ID & State Preservation
Every trans-unit ID, segment state (new, translated, reviewed), and metadata attribute stays exactly as in the original XLIFF file.
Translate XLIFF Files Online - Segments, States & IDs Preserved
Upload your XLIFF file and get accurate translation in 100+ languages. IDs, segments, states, notes, and placeholders - all preserved. XLIFF 1.2 and 2.0 supported.
XLIFF workflow
Translation example
An XLIFF 1.2 file, English to Spanish
A four-unit XLIFF written for this page, with an inline <x/> placeholder and two <g> links. The <source> text is left alone, each <target> is filled in, and the inline tags come back in the same places.
Source
Result
-
Every <source> unchanged
-
Inline tags in each target match its source
Same <x id="1"/> and <g id="2"> elements, same ids.
-
Unit ids and notes unchanged
-
target-language attribute
target-language="es"
2026-10-08 verified — Amanda Lee
XLIFF features
Placeholder Protection
Inline elements (bpt, ept, ph, x, mrk), variables, and markup references are detected and preserved. Your app logic works in every language.
Results in Minutes
Cloud-based AI processes complex localization files with thousands of segments.
100+ Languages Supported
Translate XLIFF files between 100+ languages including Spanish, French, German, Arabic, Chinese, Japanese, and Korean.
Why ForgeFile Is the Best XLIFF Translator Online
Need to translate an XLIFF file without losing segment IDs, translation states, or developer notes? ForgeFile is an AI-powered XLIFF translator that converts your localization files into 100+ languages while preserving every trans-unit ID, segment state, context note, and placeholder. Whether it's a web app, a mobile project, or an enterprise platform, your translated XLIFF is CI/CD ready and imports directly into your build pipeline.
How ForgeFile Translates XLIFF Files
Our translation engine understands the XLIFF standard natively. When you translate an XLIFF file, ForgeFile:
- Parses trans-units, segments, and groups - preserving IDs, states, and metadata
- Reads context notes and source text to deliver accurate, context-aware translations
- Writes translations into target elements while maintaining the original XLIFF schema
The result is a valid XLIFF file you can import directly into your TMS, CAT tool, or CI/CD pipeline - no manual segment editing needed.
Full XLIFF 1.2 & 2.0 Support
ForgeFile handles both XLIFF versions with their specific semantics:
- Trans-unit IDs and segment IDs are preserved exactly
- Translation states (new, translated, reviewed, final) are maintained
- Context notes, developer comments, and match quality attributes stay intact
- Inline elements (bpt, ept, ph, x, mrk) and placeholders are protected
- Source and target language attributes are updated in the file header
Built for Dev Teams, LSPs & Continuous Localization
ForgeFile handles the XLIFF workflows localization professionals rely on:
- Software Development Teams - pre-translate XLIFF exports from Xcode, Android Studio, or i18n frameworks
- Localization Service Providers - process client XLIFF files at scale with consistent quality
- Product & Localization Managers - accelerate global launches by pre-translating string files
- Open-Source Projects - make your project multilingual by translating contributor-submitted XLIFF files
Batch upload and API access are available for continuous localization pipelines. All files are encrypted in transit and at rest - fully GDPR-compliant.
Why Localization Teams Choose ForgeFile for XLIFF
- ID & State Preservation - trans-unit IDs, segment states, and metadata never modified
- Placeholder Protection - inline elements, variables, and markup references stay intact
- 100+ Languages - including right-to-left scripts (Arabic, Hebrew) and CJK characters
- Both Versions Supported - XLIFF 1.2 and 2.0 handled natively
- No Software to Install - works entirely in your browser
Upload your XLIFF file now for accurate, standards-compliant XLIFF translation.
XLIFF is standardized by OASIS - see the XLIFF 2.1 specification.
How to Translate an XLIFF File in 4 Steps
- 1
Upload Your XLIFF File
Drag and drop your .xliff or .xlf file. We support both XLIFF 1.2 and 2.0 versions for all localization projects.
- 2
Select Source & Target Language
Choose from 100+ languages. ForgeFile reads context notes and source text for accurate, context-aware translations.
- 3
Configure Translation Settings
Choose whether to update translation states and language attributes. Select which segments to translate (all, untranslated only, or specific states).
- 4
Download Your Translated XLIFF
Your translated XLIFF is ready in minutes. All IDs, states, and segments are preserved - import directly into your TMS or build pipeline.
XLIFF Translation FAQ - Common Questions Answered
How do I translate an XLIFF file online?
Upload your .xliff or .xlf file to ForgeFile, select your target language, and click Translate. Our AI fills in target segments while preserving all IDs, states, and metadata.
Are trans-unit IDs and segment states preserved?
Absolutely. ForgeFile preserves every trans-unit ID, segment state (new, translated, reviewed, final), and metadata attribute exactly as in the original.
Are placeholders and inline elements preserved?
Yes. ForgeFile detects and protects all XLIFF inline elements including bpt, ept, ph, x, and mrk tags, as well as variable references and markup.
Does ForgeFile support both XLIFF 1.2 and 2.0?
Yes. Both XLIFF versions are handled natively with their specific semantics - trans-units for 1.2 and segments/units for 2.0.
Can I translate only untranslated segments?
Yes. ForgeFile can selectively translate only segments with empty targets or specific states, leaving already-translated segments untouched.
Does it work with Xcode, Android Studio, or i18n frameworks?
Yes. ForgeFile handles XLIFF files exported from Xcode, Android Studio, and popular i18n frameworks like react-intl, Angular i18n, and Symfony Translation.
Is my XLIFF file secure during translation?
Files are encrypted in transit and at rest. How long they are kept depends on your plan.
What is the difference between XLIFF and JSON for localization?
XLIFF is the industry standard for professional translation workflows with support for states, notes, and bilingual segments. JSON is simpler and common in web apps. ForgeFile handles both natively.
Ready to Translate Your Localization Files?
Upload your XLIFF file and get CI/CD-ready translated output in minutes. IDs, states, and segments preserved, every time.