Upload a XLIFF 2.0 file and download it as XLIFF 1.2. 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.
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.
Need it the other way round? Convert XLIFF 1.2 to XLIFF 2.0.
XLIFF 2.0 is the newer OASIS standard with a simpler structure: files, units and segments. It is the preferred exchange format for modern CAT tools and localization vendors.
Used by: CAT tools, Angular, translation agencies. One language per file. Read the XLIFF 2.0 format guide.
<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="fr">
<file id="app_strings" original="messages.json">
<unit id="hello_world">
<segment>
<source>Hello World</source>
<target>Bonjour le monde</target>
</segment>
<note>My comment</note>
</unit>
</file>
</xliff>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>de.json or messages_pt-BR.properties.If you need the XLIFF 1.2 file in more languages, the fastest route is a free SimpleLocalize project: import the XLIFF 2.0 file, add languages, run auto-translation with DeepL, Google Translate, OpenAI, Claude or Gemini, and download the result as XLIFF 1.2. The CLI does the same from CI with upload and download commands, so the conversion becomes part of your build. See also translating XLIFF 2.0 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 XLIFF 1.2. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.