Upload a XLIFF 1.2 file and download it as Multi-language JSON. Translation keys, plurals and placeholders are preserved. Free, no account needed.
Pick the source format or let the converter detect it from the file.
Used when the source format holds one language per file. Also used as the source language for XLIFF output.
Choose the format you want to download.
A single JSON file where every translation key holds an object with one entry per language. Handy for small projects, static sites and CDN delivery because all languages travel together.
Need it the other way round? Convert Multi-language JSON to XLIFF 1.2.
XLIFF 1.2 is the XML-based industry standard for exchanging translations with agencies and CAT tools. Each trans-unit carries the source text, the target translation and optional notes.
Used by: Xcode, Angular, CAT tools, translation agencies. One language per file. Read the XLIFF 1.2 format guide.
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2">
<file source-language="en" target-language="pl" datatype="plaintext" original="messages">
<body>
<trans-unit id="hello_world">
<source>Hello World</source>
<target>Witaj Świecie</target>
<note>My comment</note>
</trans-unit>
</body>
</file>
</xliff>A single JSON file where every translation key holds an object with one entry per language. Handy for small projects, static sites and CDN delivery because all languages travel together.
Used by: custom i18n setups, static site generators, CDN delivery. All languages in one file. Read the Multi-language JSON format guide.
{
"en_US": {
"hello.world": "Hello World!",
"my_address": "My address"
},
"pl_PL": {
"hello.world": "Witaj Świecie!",
"my_address": "Mój adres"
}
}de.json or messages_pt-BR.properties.If you need the Multi-language JSON file in more languages, the fastest route is a free SimpleLocalize project: import the XLIFF 1.2 file, add languages, run auto-translation with DeepL, Google Translate, OpenAI, Claude or Gemini, and download the result as Multi-language JSON. The CLI does the same from CI with upload and download commands, so the conversion becomes part of your build. See also translating XLIFF 1.2 files.
Yes. There is no signup and no limit on the number of conversions beyond a few requests per second.
No. The file is parsed in memory, converted and returned in the same request. Nothing is written to disk or a database.
Plural forms are normalized to ICU message syntax and written back in the native form of Multi-language JSON. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.