Supported File Formats
Import your existing translations and export to any format your stack requires. Locize supports various import/export formats and different i18n framework formats.
Import & Export Formats
Many file formats for importing existing translations and exporting to your deployment target. All formats support both import and export unless noted otherwise.
description
JSON
.json
The default format for i18next and most JavaScript frameworks. Supports nested and flat structures.
description
XLIFF 1.2 / 2.0
.xliff, .xlf
XML-based standard used by professional CAT tools such as SDL Trados, memoQ, and Memsource.
description
YAML
.yml, .yaml
Human-readable format commonly used with Ruby on Rails, Hugo, and static site generators.
description
Android Strings
.xml
Android resource string files used by native Android applications.
description
iOS Strings
.strings
Apple string resource files used by iOS and macOS applications.
description
Xcode String Catalogs
.xcstrings
Apple's modern string catalog format introduced in Xcode 15 for iOS, macOS, watchOS, and tvOS apps.
description
RESX
.resx
.NET resource file format used by ASP.NET, WPF, Xamarin, and .NET MAUI applications.
description
Gettext
.po, .pot
GNU Gettext format widely used in PHP, Python (Django), C/C++, and WordPress projects.
description
Fluent
.ftl
Mozilla's localization system designed for natural-sounding translations with built-in pluralization and gender support.
description
Laravel PHP
.php
PHP array-based translation files used by the Laravel framework.
description
CSV
.csv
Comma-separated values for simple tabular translation data. Easy to edit in spreadsheet applications.
description
XLSX
.xlsx
Excel spreadsheet format for bulk translation management and handoff to non-technical translators.
description
TBX / UTX
.tbx, .utx
Terminology exchange formats used for importing and exporting glossary and lexicon data between localization tools.
description
TMX
.tmx
Translation Memory eXchange format for migrating translation memories between TMS platforms.
description
Java Properties
.properties
Key-value format used by Java applications, Spring Boot, and other JVM-based frameworks.
i18n Framework Formats
A lot of framework-specific formats so your translations match the syntax your code expects.
i18next v4
The current i18next format with flat or nested keys, pluralization, and interpolation and optional context-based variants for gender, formality, or other contextual distinctions.
i18next v3
Legacy i18next format for projects that have not yet migrated to v4 and optional context-based variants for gender, formality, or other contextual distinctions.
ICU MessageFormat
Industry-standard message syntax used by react-intl (FormatJS), Angular, and many other frameworks.
Fluent
Mozilla's Fluent syntax for natural-sounding translations with advanced grammar support.
Vue i18n
Format used by vue-i18n for Vue.js applications with linked messages and pluralization.
Polyglot
Airbnb's Polyglot.js format with simple interpolation and pluralization.
i18n-js (Rails)
JavaScript counterpart of Ruby on Rails i18n, commonly used in Rails-backed frontends.
Android
Android-specific i18n format with plural quantity strings and string arrays.
Other
For i18n frameworks not listed above. Locize stores your keys and values as-is, but format-specific features like intelligent plural handling or context variants are not available.
Migrating existing translations?
Locize can import your existing translation files directly — XLIFF, Gettext, Android strings, RESX, and 13 other formats. No conversion scripts needed.
Upload via UI
Drag and drop your translation files directly into the Locize editor.
Import via CLI
Use the locize-cli to bulk-import files from your repository.
API import
Push translations programmatically via the REST API.