Supported file formats

Bring your localization files in the format your platform already uses.

Localizely works with the localization file formats used across mobile, web, and backend development, whether your app is written in Dart, Kotlin, Swift, Objective-C, JavaScript, Java, PHP, Ruby, C#, or something else. You upload files in the format your platform already uses and download them in the same format, through the web app, the CLI, the REST API, or a git integration.

Available formats

Flutter ARB (.arb)
Application Resource Bundle files used for Flutter app localization.
Gettext PO (.po, .pot)
Portable Object files used with the Gettext toolchain.
Android Resources (.xml)
String resource XML files used for Android app localization.
Apple Strings (.strings)
Localizable.strings files used for iOS app localization.
Apple Stringsdict (.stringsdict)
Localizable.stringsdict files used for plural and variant strings on iOS.
Apple String Catalog (.xcstrings)
Localizable.xcstrings files for iOS and macOS, holding all languages in a single file.
XLIFF (.xlf, .xliff)
XML Localization Interchange File Format 1.2, as used for Angular localization and by translation and e-learning tools such as Articulate Rise 360. Downloaded as Angular XLIFF or as a neutral XLIFF file.
Key-Value JSON (.json)
Flat JSON files without nested objects, as used by many JavaScript libraries such as i18next.
Java Properties (.properties)
Standard resource bundle files used for Java localization.
Ruby on Rails YAML (.yml)
YAML locale files used by Ruby on Rails applications.
.NET Resources (.resx)
Resources.resx files used for .NET localization.
CSV (.csv)
Comma-separated values, handy for exchanging translations with spreadsheets.
Excel (.xls, .xlsx)
Excel workbooks, in both the legacy format and the format used since Excel 2007.
Translation Memory Exchange (.tmx)
The industry-standard format for importing Translation Memory from other tools.

Several platforms in one project

Every platform writes placeholders differently, for example %1$s on Android and %1$@ on iOS. With universal placeholders, placeholders are stored in one form and converted to the syntax of each file format on upload and download, so the same string keys can serve Android, iOS, web, and every other platform from a single project.

Missing your format?

We add new formats regularly. If the one you use is not listed, let us know and we will look into it.

Supported file formats

Documentation

Available formats

Several platforms in one project

Missing your format?

Documentation

About

Resources

Free tools

Boring stuff

Newsletter