XLIFF
XLIFF 1.2 · interchange · 46 languages · Free

Translate XLIFF, with the inline tags kept in place

XLIFF is the format every TMS exports. Drop in your .xliff and KAERIS translates each <trans-unit> into 46 languages, keeps inline <g>/<x/> tags in place, and reads every unit back so meaning drift is caught before you re-import.

Translate your file → $ pip install kaeris
Inline tags preserved trans-unit structure intact Round-trips to your TMS Placeholders kept No account needed
What breaks in XLIFF — and how KAERIS handles it

Inline tags that survive

<g id="1">bold</g> and self-closing <x/> placeholders stay exactly where they belong — drop one and read-back flags it, so your re-import doesn't fail validation.

Structure you re-import cleanly

Unit ids, order and the surrounding XML are preserved, so the file drops straight back into Crowdin, Phrase, memoQ or whatever exported it.

Meaning you can trust

Beyond structure, each translated <target> is read back into your language and checked for drift — the one thing a raw machine-translate step skips.

Real XLIFF, round-tripped

Before → after

messages.xliff (source)
<trans-unit id="greeting">
  <source>Welcome, <g id="1">{name}</g>!</source>
</trans-unit>
messages.xliff (fr target)
<trans-unit id="greeting">
  <target>Bienvenue, <g id="1">{name}</g> !</target>
</trans-unit>
From file to shipped in 3 steps
1

Drop your .xliff file

Upload it as-is, or run pip install kaeris and translate from your terminal or CI.

2

Pick languages & verify

Choose from 46 languages. Leave read-back on to catch meaning drift, lost placeholders and overflow.

3

Ship the .xliff back

Download one .xliff per language, structure intact — or let the GitHub Action open a PR when new keys land.

Translate your .xliff now

Free, no account. Read every line back in your own language.

Drop your .xliff file →

See the read-back benchmark · CLI & GitHub Action