Import & Export

Round-trip locale files across web, mobile, and backend stacks.

LingPie Import & Export supports round-tripping localization files across web, mobile, and backend stacks. Teams import locale files into a project and export in formats such as i18next JSON, next-intl JSON, Flutter ARB, Android XML, Apple strings and String Catalogs, Java properties, and XLIFF ICU.

Broad localization format support covering mainstream platforms—web, mobile, and backend. VS Code · CLI · MCP · Figma

Apple .strings & .stringsdict

Apple .strings (ICU)

Apple .xcstrings

Apple .xcstrings (ICU)

Android .xml

Android .xml (ICU)

Flutter .arb

i18next Key Flat .json

i18next Key Flat .json (ICU)

i18next Key Nested .json

i18next Key Nested .json (ICU)

Next-intl Key Flat .json (ICU)

Next-intl Key Nested .json (ICU)

Java .properties (ICU)

Java .properties (printf)

.NET .resx (native {n})

.NET .resx (ICU)

Gettext .po (ICU)

Gettext .po (printf)

.xliff (ICU)

Nested .yaml (ICU)

Flat .yaml (ICU)

Nested .yaml (ICU, language root)

Flat .yaml (ICU, language root)

Nested .yaml (printf)

Flat .yaml (printf)

Nested .yaml (printf, language root)

Flat .yaml (printf, language root)

Ruby/Rails Nested .yaml (%{name})

Ruby/Rails Flat .yaml (%{name})

Nested .php (ICU)

Flat .php (ICU)

.ini (ICU)

Qt Linguist .ts (native %1 / %n)

Qt Linguist .ts (ICU)

.csv (ICU)

.xlsx (ICU)

Import localization files

Upload locale files from your web, mobile, or backend stack. LingPie maps keys into the project so translators can work without fighting format differences.

Export in your target format

Download translated strings back as i18next JSON, Flutter ARB, Android XML, Apple String Catalogs, and more—ready to drop into your repo or CI pipeline.

Related product