Convert XLIFF 1.2 to PO online
Upload a XLIFF 1.2 file and download it as gettext PO/POT. 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.
gettext PO files pair every msgid with a msgstr and support plural forms, contexts and translator comments. They are the standard in Python, PHP, WordPress, Django and desktop Linux software.
Need it the other way round? Convert PO 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>To: gettext PO/POT
gettext PO files pair every msgid with a msgstr and support plural forms, contexts and translator comments. They are the standard in Python, PHP, WordPress, Django and desktop Linux software.
Used by: Django, WordPress, PHP, Python, GNU tools. One language per file. Read the PO format guide.
# Single line
msgctxt "My translation context"
msgid "My translation key"
msgstr "My translation message"
# Multiple lines
msgid ""
"The input text "
"split to several "
"lines"
msgstr ""
"Translation "
"can also be splitted."How to convert XLIFF 1.2 to PO
- Drop your .xliff file into the converter above, or paste its content.
- Confirm the language of the file. It is guessed from the file name, for example
de.jsonormessages_pt-BR.properties. - Click Convert. You get one .po file per language.
- Preview the result, copy it or download the files.
What changes between XLIFF 1.2 and PO
- Target texts from the XLIFF trans-units are used as translations; units without a target are exported with empty values.
- Translation keys become msgid entries; ICU plural messages are written as msgid_plural with one msgstr per plural form.
Convert and translate in one place
If you need the PO 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 PO. 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 PO. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.
Convert XLIFF 1.2 to other formats
Convert other formats to PO
Translate your PO files
- Import XLIFF 1.2 or PO 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