.JSON #️⃣

Localazy supports various JSON flavors, including i18Next, Mozilla i18n, Multilingual JSON, JSON5, HJSON, and RequireJS.

Learn more about the JSON file format in the CLI docs

Android .XML #️⃣

Android XML format is fully supported including array-lists and plurals. No extra configuration is necessary.

For Android app localization, we recommend using the Localazy Gradle plugin that automatically handles uploads, downloads and adds code for OTA (over-the-air) updates.

Learn more about the Android XML file format in the CLI docs

iOS and macOS formats #️⃣

For iOS and macOS apps, Localazy supports .xcstrings, .strings, .stringsdict, .plist and XLIFF files.

Learn more about iOS and macOS formats in the CLI docs

.xcstrings #️⃣

All the features of XCode Strings Catalogs are supported, including simple values, variants, substitutions and plurals.

No extra configuration is necessary as all the features are supported out of the box.

Learn more about the Xcode String Catalog format in the CLI docs

XLIFF #️⃣

XLIFF 1.2 #️⃣

Selected elements of XLIFF 1.2 are supported, and the format is fully compliant with Apple’s XLIFF files generated by XCode including Apple’s plural extension.

Learn more about the XLIFF 1.2 format in the CLI docs

XLIFF 2.0 #️⃣

Selected elements of XLIFF 2.0 are supported, and we added extra support for Apple’s plural extension, arrays, and other forms of plurals.

Learn more about the XLIFF 2.0 format in the CLI docs

iSpring Suite .XLIFF #️⃣

iSpring Suite XLIFF format is supported out of the box.

.PO/.POT file #️⃣

Gettext PO/POT format is fully supported including plurals and context information.

See the full specification for more details.

Learn more about .PO & .POT formats in the CLI docs

.YAML #️⃣

Localazy supports various YAML flavors, including plain, structured, Rails i18n, Multilingual YAML, object-based, and array-based YAMLs.

Learn more about the YAML file format in the CLI docs

Flutter .ARB #️⃣

Flutter’s ARB format is fully supported including arrays, plurals, and selected context information. No extra configuration is necessary, but you can enable certain features if you want to.

Learn more about the Flutter ARB file format in the CLI docs

Adobe Captivate .XML #️⃣

Adobe Captivate Export format is supported out of the box.

.CSV/.TSV #️⃣

With Localazy, you can parse CSV/TSV files and configure the parser to handle almost any of the widely used formats.

If you follow one of the pre-defined structures, you can select how to read the file - which column is the key, which one is the comment for the translator, and where to look for translations.

You can also upload multilingual CSV/TSV files.

Learn more about CSV & TSV formats in the CLI docs

Excel (.xls/.xlsx) #️⃣

With Localazy, you easily use Microsoft Excel files (both XLS and XLSX) to localize your mobile, web, or desktop apps as well as marketing materials, tags, social posts, documentation, etc.

The expected format is as shown below:

Key	Translation	Comment

By default, Localazy expects the first row to be a header.

Only the first sheet is used. Other sheets are ignored.

You can also upload multilingual files.

Learn more about Excel support in the CLI docs

OpenOffice (.ods) #️⃣

OpenOffice format follows the same rules as the XLS format above, including multilingual files.

Learn more about OpenOffice support in the CLI docs

.INI file #️⃣

INI files are supported and with Localazy, it’s possible to use also plurals and arrays for more comfortable and accurate translations. You can also use multilingual INI files.

Learn more about the INI file format in the CLI docs

Java .properties #️⃣

Java Properties files are supported and with Localazy, it’s possible to use also plurals and arrays for more comfortable and accurate translations.

Learn more about the Java Properties file format in the CLI docs

Javascript .JS & Typescript .TS #️⃣

Our parser can adapt to many formats of JS files that follow the rule PREFIX { localizable content } SUFFIX.

Please note that functions, imports, lambdas, explicit types (for TypeScript), string concatenation, etc. are not supported in the localizable content part. Also, there can be only one localizable part in the file.

For multiline strings, you can use backticks.

Learn more about Javascript & Typescript formats in the CLI docs

Nette .NEON #️⃣

NEON (Nette Object Notation) is a popular format for Nette framework and with Localazy, you can use it out-of-the-box with plain, structured, multilingual, object-based, and array-based NEONs.

Learn more about the NEON file format in the CLI docs

.TOML #️⃣

Localazy supports various TOML flavors, including plain, structured, multilingual, and object-based TOML.

Learn more about the TOML file format in the CLI docs

.PHP/Laravel #️⃣

Localazy allows using PHP files based on associative arrays such as those commonly used with Laravel framework. You can also upload multilingual PHP. As an addition, we support for many different features - plurals, ICU, etc.

Learn more about the PHP file format in the CLI docs

.TXT & .MD texts #️⃣

Localize text & markdown files, app store description, marketing materials, and more with Localazy. In Localazy, the file is stored as a file with a single key content.

Learn more about the Plain Texts file format in the CLI docs

QT Linguist .TS #️⃣

Qt’s Linguist .TS files are fully supported by Localazy. You can use id-based or source-based files.

Learn more about the QT-TS file format in the CLI docs

.RESX #️⃣

RESX format is supported and with Localazy, it’s possible to use also plurals and arrays for more comfortable and accurate translations.

Learn more about RESX file format in the CLI docs

.SRT Subtitles #️⃣

Upload SRT (SubRip Text) files with subtitles to Localazy and manage your translations easily.

By default, Localazy tries to autodetect the character encoding.

Learn more about SRT file format in the CLI docs

.TMX (Translation Memory) #️⃣

TMX (Translation Memory eXchange) files are supported in the same way as all other localizable formats. There’s also a custom implementation for pluralized items.

TMX files up to version 1.4b are supported.

Learn more about the TMX file format in the CLI docs