Upload a gettext PO/POT 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 PO.
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."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 PO 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 PO 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.