Free XLIFF editor · runs in your browser
Open the SDLXLIFF a client made in Trados Studio, the MQXLIFF from memoQ, or any XLIFF, PO, SRT, WebVTT, Excel or CSV file. Translate and check it, and export it untouched outside your translations. xliff.ai is a translation editor, not a translation service, and nothing is uploaded.
No account · no install · works offline No file to hand? Try it on a sample ↓
0
uploads
Your browser opens, edits and saves the file. There is no server that could receive it. Where your file goes
€0
for everything
Every feature and every export, with no trial and no paid tier. Your computer does the work, so there is no server to pay for.
9
file formats
XLIFF 1.2 and 2.0, SDLXLIFF from Trados, MQXLIFF from memoQ, PO, SRT and WebVTT subtitles, Excel and CSV.
Live · sample.xlf · English → German
It is already running on a sample file, in this tab. Click a target cell, type, and press Ctrl+Enter to confirm. On a touch screen, tap the cell, type, and tap its status.
Confidential by design
Not because a privacy policy says so: there is no server that receives files, so there is nowhere for yours to go. Your browser does all the work.
Your computer
Autosave keeps your session in the browser's own storage, on the same disk.
In desktop Chrome and Edge, AI translation happens here as well: the translator built into the browser, with nothing sent.
Outside · optional
The AI provider you chose
Only when you press an AI button with a provider chosen: the segments in your current view, two neighbours on each side and matching glossary terms, sent with your own key. Never the file.
The editor
Built for the daily loop — type, confirm, move on — with your memory, your glossary and the checks a client expects.
Ctrl+Enter confirms and moves on. Switch to the Trados Studio or memoQ preset and your hands already know the rest.
Load a TMX, a two-column Excel or CSV, or a file you translated before, and pretranslate with exact and fuzzy matches.
Import a TBX, CSV or Excel termbase. Terms are marked in the source, and the checks flag missing and forbidden ones.
Tags, placeholders, numbers, punctuation, no-break spaces, terms and consistency, each at the severity you choose.
Confirm a segment and its empty repetitions are filled as Draft, waiting for you to confirm them in turn.
How was this translated before? Search the file and your memories at once, and replace across the whole file.
Every edit is saved in this browser as you type, with 200 steps of undo. Close the tab and the session is offered back.
The file in its own format, plus TMX, bilingual Excel, a review workbook, a QA report and a pseudo-translation.
Use it for
A client sends an SDLXLIFF or MQXLIFF. Open it here, translate and confirm, and export. Statuses change only on the segments you confirmed and on empty repetitions, which are filled as draft; comments and match rates are left as they came.
Load a TMX or a file you translated before and pretranslate new segments from it. Export what you finish as TMX to feed the memory in your main tool.
Run the quality checks over a file you did not translate — a vendor's delivery, a post-edited machine translation — filter to the problems, and export a QA report.
Export a review workbook with a decision drop-down on every segment. Your client reviews it in Excel, and you import their decisions back into the file.
Open the Excel or CSV sheet exported from your code, with the source and target columns detected for you, and get the same sheet back with the translations filled in.
Pseudo-translate a resource file to find hard-coded strings, text that gets cut off and broken placeholders before a single word goes to a translator.
Compared
Upload converters keep your file on their server. Browser CAT platforms need an account and the file on theirs. Desktop CAT tools keep it on your computer, for the price of a licence.
| Question | xliff.ai | Upload converters | Browser CAT platforms | Desktop CAT tools |
|---|---|---|---|---|
| Where the file goes | Stays on your computer | Uploaded; kept for hours | Uploaded to the platform | Stays on your computer |
| Account | None | Usually none | Required | Licence |
| Edit, confirm, export | Yes | Mostly view or convert | Yes | Yes |
| Trados and memoQ files | SDLXLIFF and MQXLIFF, written back byte for byte outside your edits | View or convert | Often imported, sometimes exported in another flavour | Native to their own tool |
| Cost | Free | Free | Free tier or subscription | Paid licence |
The export
The usual way to save a translation file is to read it into memory and write a new one out. The new file means the same thing, but the details a CAT tool cares about can shift on the way: attribute order, line endings, entities, the byte order mark.
xliff.ai keeps your original file and replaces only the targets you changed. Export an XLIFF, SDLXLIFF, MQXLIFF, PO or subtitle file without editing it and you get the same file back, byte for byte — an automated test suite checks exactly that. Excel and CSV files are rewritten by their own format's rules, keeping sheets, columns and formatting.
Read into memory, write a new file
every byte rewritten
xliff.ai, after you edit two segments
two ranges rewritten, the rest copied
Yes. The editor, the quality checks, the translation memory and every export are free, with no account, no trial and no paid tier. It can be free because there is no server: your own computer does the work, so there is nothing to pay for per user. xliff.ai is made by Terratra, a translation and localization company in Estonia.
No. Your browser reads the file, edits it and writes the export on your own computer. You can check this yourself: open your browser's network tab, open a file, and look for a request that carries it — there is none. Or turn on the network lock, the padlock in the editor's top bar: the editor then refuses every request, and its count lists each one since you opened the file. In desktop Chrome and Edge, AI translation runs on your computer too, with the translator built into the browser, and sends nothing. The only feature that sends text anywhere is AI review and translation with your own provider key, and only when you press its button: it sends the source text of the segments in your current view (with their translations, for a review), two neighbouring segments on each side for context, and any matching glossary terms, straight to the AI provider you chose. The file itself is never sent.
In Chrome and Edge on a computer, Save (Ctrl+S) writes your translation back into the file you opened, in its folder, after your browser asks you to allow it once for that file. It never writes over a file that another program changed after you opened it without asking you first, and Restore the original file, in the menu beside Save, puts the file as you opened it back while the tab is open. A file opened from a project folder also gets a backup copy beside it at the first save, ending in .orig. Save as copy, in the same menu, downloads a separate copy instead, and Always download a copy, under ⋯, makes every save a download. In Firefox, Safari and on phones and tablets, Save downloads the translated file, as it always has.
No. xliff.ai opens SDLXLIFF files from Trados Studio and MQXLIFF files from memoQ on its own, as well as XLIFF 1.2 and 2.0, gettext PO, SRT and WebVTT subtitles, Excel and CSV. There is nothing to install.
It is built to. Everything outside the segments you edit is written back byte for byte as it arrived, and an automated test suite checks exactly that. It has not yet been tested inside Trados Studio and memoQ themselves, so until it has, keep a copy of your original file (in Chrome and Edge, Save writes into the file you opened) and open the export in the tool that will consume it before you deliver. If something is rejected, write to xliff@terratra.com.
Only if you ask it to. By default you write the translation, and pretranslation comes from translation memories you load yourself. AI translation can fill the empty segments in your current view, or retranslate one segment: in desktop Chrome and Edge with the translator built into the browser, on your computer, with no key and nothing sent; in any browser with your own AI provider key. Either way it writes the result as Draft: nothing is confirmed until you confirm it, and one undo reverses a whole run. A result that loses an inline tag is not written at all.
Every edit is saved in your browser's own storage as you type, together with two hundred steps of undo. Open xliff.ai again and it offers the session back. That storage is on your computer, so your work does not follow you to another machine, and opening a second file replaces the stored session — the editor asks before it does.
Yes. Load a TMX file, a two-column Excel, CSV or TSV file, or a bilingual file you translated before, and pretranslate from it with exact and fuzzy matches. You can export your finished work as TMX too. Trados .sdltm files and server-based memories are not supported; export them to TMX first.
It is tested in current Chrome and Edge on a desktop or laptop; Firefox and Safari are not yet part of the automated tests. Opening a whole project folder works only in Chrome and Edge on a computer; elsewhere you open files one at a time. On a phone, or a small tablet held upright, each segment is a card with the source above the target, and you confirm a segment by tapping its status. Keyboard shortcuts such as Ctrl+Enter need a physical keyboard. The phone layout has been checked in a desktop browser's phone emulation, not yet on a real iPhone or iPad, or in Safari.
Something else? Ask, or report a problem.