Game Localization · All Services
XLIFF Translation — Game Localization from .xliff Files
Native translators. Translation Memory. LocQA in your build. Get a free quote →
XLIFF (XML Localization Interchange File Format) is the closest thing game localization has to a universal file standard — supported by Unity, convertible from Unreal Engine’s PO exports, and accepted by every major CAT tool. If your game uses .xliff files, sending them to SandVox is straightforward: we translate using Translation Memory and terminology glossaries, and return translated files in the same XLIFF format ready for direct engine import.
What Is XLIFF?
XLIFF is an XML-based open standard for exchanging localization data between tools. It pairs each source-language segment with its target-language translation, metadata, and status flags — making it readable by any standards-compliant CAT tool or localization platform. XLIFF files contain your source strings and receive translated content in return, leaving your game engine integration intact.
XLIFF 1.2 vs XLIFF 2.0
XLIFF 1.2 is the legacy version — widely supported but with a complex and inconsistently implemented schema. XLIFF 2.0 is the current standard — cleaner schema, modular extensions for metadata and annotations, and better tool support in recent versions of memoQ, Trados, and Phrase. Unity’s Localization Package exports XLIFF 2.0 by default in recent versions. Unreal Engine typically uses .po format natively, but its exports can be converted to XLIFF via Okapi Framework. SandVox works with both XLIFF 1.2 and 2.0 — specify your version when sending files.
Which Game Engines Use XLIFF?
Unity’s Localization Package (com.unity.localization) exports and imports XLIFF 2.0 natively for string table content. Custom game engines using industry-standard pipelines often adopt XLIFF for its broad tool compatibility. Unreal Engine uses .po as its native export format, but Okapi Framework converts Unreal .po files to XLIFF with full segment metadata preserved. Web-based games and cross-platform frameworks with localization requirements frequently adopt XLIFF as the interchange format between developer tools and translation vendors.
How to Send XLIFF Files to SandVox
Export your XLIFF files from your engine or localization tool — include source language text and, if available, any translator notes or context metadata you have added. Send the files along with your target languages and a brief description of the game genre and tone. SandVox processes XLIFF files through a memoQ-based workflow with per-project Translation Memory and terminology glossary, then returns translated XLIFF files in the same version (1.2 or 2.0) ready for direct import into your engine. We also deliver the project TM and glossary for use on future patches or DLC.
Frequently Asked Questions
Can SandVox handle both XLIFF 1.2 and XLIFF 2.0?
Yes. Specify the version when you send files. If you are unsure, include the file and we will identify the version during scoping.
Do you return files in the same XLIFF format I send?
Yes. We return translated XLIFF files in the same version and structure you send, with all metadata and status flags preserved. Files are ready for direct import into Unity, your custom engine, or your localization platform.
What if my XLIFF files have missing context or translator notes?
We flag strings that appear ambiguous during scoping and request context before translation begins. Context provided before translation starts costs nothing; context clarified during translation (causing re-translation) adds to cost and timeline.
Can you translate XLIFF files for mobile games?
Yes. XLIFF translation is format-agnostic from our workflow perspective. Whether your XLIFF comes from a Unity mobile build, a web game, or a custom engine, the process is the same: export, translate, QA, return.
Send Your XLIFF Translation Files to SandVox
Tell us your word count, target languages, and timeline. We return translated files in the same format — ready for direct import. Free quote in one business day.