◆ File conversionFREE

Your CAT tool speaks XLIFF.
Your vendor wants Excel.

XLIFF⇄XLSXInline tags, states, file header — all preserved · send the .xlf as a sheet, load it straight back.
Converter· Local processing
Drop your .xlf here
or pick from your device · your file never leaves your browser
01 · what this tool actually does for you

Turn an XLIFF 1.2 file into an Excel sheet a translator or vendor can edit, then load it straight back to XLIFF — inline tags, translation states, the file header, placeholders and whitespace all preserved, every trans-unit keyed by its id. Not generic XML-to-table — the one step a CAT/TMS handoff actually needs.

Files never leave your deviceIn-browser · zero upload · NDA-friendly
Deterministic conversionThe same input always yields the same output
Lossless round-tripXLIFF→Excel→XLIFF keeps every unit
02 · two formats, one round-trip

XLIFF and Excel are each good at different things

This conversion exists so CAT/TMS tools and translators each use the format they're comfortable with — without losing anything in between.

XLIFF 1.2.xlf

The bilingual interchange format CAT tools and TMS platforms (memoQ, Trados, Phrase, Crowdin…) export: one trans-unit per string with a source and target, a translation state, and inline tags (ph, g, bpt/ept) standing in for formatting and variables. Precise — not something to hand-edit by eye.

Excel.xlsx

The interface translators, reviewers and vendors find most natural: one row per string, source and translation side by side, easy to filter, bulk-edit and annotate. The catch: open an .xlf in raw Excel and the inline tags get mangled, the state is lost, and it won’t load back into the CAT tool.

What this tool guards is exactly that “won’t load back”: on export it carries every inline tag character-exact, keeps each target’s state in the Type column, and stores the file header in reserved @@file.* rows — so the sheet rebuilds into valid XLIFF 1.2 on the way back. A few XLIFF constructs can’t survive a spreadsheet and are reported, never silently dropped: notes, alternative translations (alt-trans), group nesting, the approved flag and resname — and XLIFF 2.0 is not yet supported (1.2 only).

03 · common questions

You're probably wondering

Will my file be uploaded?+
No. Parsing and conversion run entirely in your browser (a Web Worker handles large files); the file never leaves your machine and never touches a server. That's a hard requirement for NDA-bound localization work, so the tool is built fully client-side.
How do I send an XLIFF to a translator who only uses Excel?+
Convert the .xlf to an Excel sheet here, hand the sheet to the translator or vendor, then load the edited sheet back to XLIFF — one <trans-unit> per row, source and translation side by side. Inline tags, states and the <file> header are all carried, so the rebuilt XLIFF loads straight back into your CAT tool.
Does converting XLIFF to Excel lose the inline tags or states?+
No. Inline tags (<ph>, <g>, <bpt>/<ept>) are kept character-exact, each <target> state goes into a Type column, and the <file> header is stored in reserved rows. A few constructs that can’t map — notes, <alt-trans> candidates, group nesting, the approved flag and resname — are reported at export, never silently dropped. Every conversion comes with a fidelity report.
How is this different from my CAT tool's built-in Excel export?+
Built-in exports often flatten inline tags to plain text or drop the state, so the sheet can’t be loaded back cleanly. This tool treats round-trip fidelity as the whole point: tags stay character-exact, states are preserved in a column, and the XLIFF rebuilds into valid 1.2. It’s also fully local — nothing is uploaded.
Which XLIFF version is supported, and is it free?+
This tool handles XLIFF 1.2, the version most CAT/TMS tools export. XLIFF 2.0 has a different structure and isn't supported yet — you'll get a clear message, never a silent mis-parse. This tier is completely free, no account, no usage limits.
04 · who made this / why

Built by someone who's done this work

This isn’t a thin wrapper over a large model, and it isn’t an open-source library reskinned. It comes from years of game-localization frontline work and the pile of "nobody notices until it breaks" details that come with it.

The CAT tool hands over an XLIFF; the vendor only wants to edit in Excel — the format loss in between shouldn’t be a human’s job to absorb.

Hand an .xlf to a vendor and nine times out of ten it comes back with inline tags "cleaned up" into plain text, the target state wiped, group structure mangled — and it won’t load back into the CAT tool. We hit every one of those, so the tool guards them by default: character-exact inline tags, state-preserving columns, the file header stored and restored.

Free, fully local, instant. It’s one step in a workflow, not a platform — but it comes from a place that genuinely understands localization.