Convert XLIFF 1.2 to XLIFF 2.0 online

Upload a XLIFF 1.2 file and download it as XLIFF 2.0. 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 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.

One file per language. Format documentation

Need it the other way round? Convert XLIFF 2.0 to XLIFF 1.2.

From: 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>
<?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>

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>
<?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>

How to convert XLIFF 1.2 to XLIFF 2.0

  1. Drop your .xliff file into the converter above, or paste its content.
  2. Confirm the language of the file. It is guessed from the file name, for example de.json or messages_pt-BR.properties.
  3. Click Convert. You get one .xliff file per language.
  4. Preview the result, copy it or download the files.

What changes between XLIFF 1.2 and XLIFF 2.0

  • Target texts from the XLIFF trans-units are used as translations; units without a target are exported with empty values.
  • The language you enter in the converter becomes the XLIFF source-language, and the same texts fill both source and target elements.

Convert and translate in one place

If you need the XLIFF 2.0 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 XLIFF 2.0. 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.

Frequently asked questions

Is the converter free?

Yes. There is no signup and no limit on the number of conversions beyond a few requests per second.

Are my files stored?

No. The file is parsed in memory, converted and returned in the same request. Nothing is written to disk or a database.

What about plurals and placeholders?

Plural forms are normalized to ICU message syntax and written back in the native form of XLIFF 2.0. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.

Translate your XLIFF 2.0 files

  • Import XLIFF 1.2 or XLIFF 2.0 files into a free project
  • Auto-translate with DeepL, Google, OpenAI, Claude or Gemini
  • Download in any of the supported formats or publish to the CDN
Start for free
No credit card required5-minute setup
"The product
and support
are fantastic."
Laars Buur|CTO
"The support is
blazing fast,
thank you Jakub!"
Stefan|Developer
"Interface that
makes any dev
feel at home!"
Dario De Cianni|CTO
"Excellent app,
saves my time
and money"
Dmitry Melnik|Developer