Markup is never translated
Tags, attributes, namespaces, and entity references are treated as structure, not as content.
Translate XML into 75+ languages without touching the markup. Tags, attributes, CDATA, and placeholders are protected; only translatable text is replaced, and it returns to exactly the right node.
Free to start · 75+ languages · No credit card required
Capabilities
Tags, attributes, namespaces, and entity references are treated as structure, not as content.
Variables and interpolation tokens are protected, so a translated string still renders correctly at runtime.
Output parses. You get a well-formed document per language, not a text file you have to reassemble.
Terminology is enforced and previously approved strings are reused across every file in the set.
How it works
Every stage runs on the same platform, so nothing is exported, re-uploaded, or handed between tools.
Drop in one XML file or a whole batch.
Pick languages and the glossary to apply.
Translatable nodes are extracted, translated, and written back in place.
Get a valid XML file per target language.
Who it is for
DocBook, DITA, and custom documentation schemas.
Feed files that drive storefronts and marketplaces.
Android strings and other XML-backed resource sets.
System-to-system payloads that must stay parseable.
FAQ
Yes. Files are parsed structurally rather than as text. Tags, attributes, namespaces, and entities are preserved and the output is a well-formed document per language.
They are protected during translation, so interpolation tokens survive intact and translated strings still render correctly at runtime.
Yes. Batch upload is supported, and translation memory is shared across the batch so repeated strings translate once and reuse everywhere.
Everything in Vitra Universe shares one translation memory, one brand kit, and one quality bar — so the work you do here makes everything you do next faster.