Deliver a Trados or memoQ job without the licence
A client sends an SDLXLIFF or MQXLIFF. Open it here, translate and confirm, and export. Statuses change only on the segments you confirmed; comments and match rates are left as they came.
Free translation file editor · runs in your browser
xliff.ai edits XLIFF, SDLXLIFF (Trados), MQXLIFF (memoQ), Excel and CSV translation files right in your browser. It is free, needs no account, and never uploads your file.
This is the real editor, already running on a sample file. Click a target cell, type, and press Ctrl+Enter to confirm.
A preview of the editor, with the sample file it opens. The editor is built for a computer screen and a keyboard: open this page on one to try it live.
A translation file is somebody else's property, in somebody else's format, due tomorrow. The tool that opens it should be free to reach for, safe to trust with it, and careful with every byte it does not need to touch.
Drop an XLIFF, SDLXLIFF, MQXLIFF, Excel or CSV file on the page, or open a whole project folder in Chrome or Edge. Your browser reads it; nothing is uploaded.
Work segment by segment: type, press Ctrl+Enter to confirm and jump to the next one, and let repetitions fill themselves. Pretranslate from your own memory, run the quality checks, and fix what they find.
Download the finished file in its original format, ready to send back. Add a TMX for your memory, a QA report, or an Excel review workbook for a client who does not use a CAT tool.
Your computer
Autosave keeps your session in the browser's own storage, on the same disk.
A client sends an SDLXLIFF or MQXLIFF. Open it here, translate and confirm, and export. Statuses change only on the segments you confirmed; comments and match rates are left as they came.
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.
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.
Open the Excel or CSV sheet a developer exported, with the source and target columns detected for you, and send back the same sheet 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.
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 or MQXLIFF without editing it and you get the same file back, byte for byte — automated tests check that on every build. 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. A donation link in the footer supports development, and nothing is behind it.
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. The only feature that sends text anywhere is the optional AI review, which sends the segments you select to the AI provider you chose, with your own key.
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, 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 automated tests check that on every build. It has not yet been tested inside Trados Studio and memoQ themselves, so until it has, keep your original file and open the export in the tool that will consume it before you deliver. If something is rejected, write to xliff@terratra.com.
No. There is no machine translation. You write the translation; pretranslation comes only from translation memories you load yourself. The optional AI review reads your translation and reports possible errors against the source — it does not write your targets.
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. Opening a whole project folder uses a feature only Chrome and Edge have; elsewhere you open files one at a time, and Firefox and Safari are not yet part of the automated tests. The editor opens on a phone, but it is built for a larger screen with a keyboard.
Something else? Ask, or report a problem.
Drop it below and it opens in the editor. It stays on your computer the whole time.