Trados files, without Trados
An agency sends you a Trados translation memory, a MultiTerm termbase, a package or a bilingual file, and you work in memoQ, OmegaT, Phrase or Wordfast. This page reads those files directly — no Trados Studio, no MultiTerm, no trial install, no Windows needed — and gives you standard formats back. You can upload several files at once; the type of each file is detected automatically.
| You upload | You get |
|---|---|
| .sdltm translation memory | TMX 1.4b with languages, creation/change dates and users, usage counts and all custom fields; the same data as Excel and CSV |
| .sdltb MultiTerm termbase | TBX-Basic (all languages, synonyms, fields, dates, users), an Excel glossary (one row per entry and one row per term), a CSV glossary and the termbase's images |
| .sdlxliff bilingual file | A bilingual review spreadsheet (segment IDs, status, match %, comments, tags as numbered placeholders) and the translated segments as TMX; the edited spreadsheet can be turned back into an updated .sdlxliff |
| .sdlppx / .sdlrpx package | An overview (languages, files, memories, termbases), every file inside converted as above, and all files unpacked in a ZIP |
Before downloading you see what is inside: number of units, languages, fields, entries, terms, segments and words, and the first rows of every file.
Importing the results
memoQ – Translation memory: Resource console → Translation memories → Import from TMX (or
import into a project TM). Custom Trados fields arrive as TMX properties named x-FieldName, which
memoQ offers to map to its own fields. Termbase: Resource console → Term bases → Import terms and
pick the .tbx file (or the .csv with one column per language).
OmegaT – Copy the .tmx into the tm/ folder of your project (or tm/auto/ for automatic
insertion). Copy the .tbx into the glossary/ folder; OmegaT reads TBX glossaries directly.
Phrase (Memsource) – Translation memories → Import and choose the TMX. Term bases → Import accepts the TBX or the Excel/CSV glossary.
Wordfast Pro – TM → Import the TMX; import the TBX or the CSV glossary as a glossary.
Back into Trados – The TMX and TBX also import into Trados Studio and MultiTerm, e.g. to move a memory to another Studio version or to merge memories.
Editing an SDLXLIFF in Excel and sending it back
- Upload the
.sdlxliff(or the whole.sdlppxpackage) and download the review spreadsheet. - Edit only the Target column. Formatting and placeholders appear as numbered tags —
<1>bold text</1>for pairs and<2/>for single tags such as line breaks or fields; the Tags column says what each number stands for. You may move tags, but keep them. - Upload the original
.sdlxliff(or package) again, put the edited spreadsheet into Edited review spreadsheet, and convert. - You get the updated
.sdlxliffwith the same file name. Only the changed translations and their status are touched; every other byte of the file stays as it was, so Trados opens it like the original. Tags are checked first: a segment with a missing closing tag or a tag used twice is not changed and is listed so you can fix it. Locked segments are never changed.
Supported versions
File-based translation memories (.sdltm) from Trados Studio 2009 onwards (tested with memories
from Studio 2009, 2017 and 2019+), MultiTerm 2009 and later termbases (.sdltb), SDLXLIFF files
and Studio project and return packages (tested with Studio 2015 and 2022 packages). Translation memories with hundreds of thousands of units are streamed and converted in
seconds.
What is not converted
- Server memories (GroupShare, Trados Enterprise/Language Cloud) are not files and cannot be
uploaded; export them to
.sdltmor TMX first. - Trados does not store the original formatting codes in a memory, so tags in the TMX are empty
bpt/ept/phmarkers (which is what CAT tools expect); context-match information and Trados' internal fuzzy-index data are not exported. - MultiTerm fields without a TBX-Basic equivalent are written as TBX notes (
Field: value) rather than dropped; picklist definitions and entry-level layouts are not part of TBX-Basic. - The review spreadsheet is Excel only (no Word version yet). Tracked changes are shown accepted; if you edit a segment that has tracked changes, the new text replaces them. Comments stay attached to edited segments but now cover the whole segment. New comments cannot be added from Excel.
- An updated package is returned as updated
.sdlxlifffiles, not as a new.sdlrpxreturn package. - Encrypted (password-protected) termbase databases are not supported.
Privacy
Your files are processed on our server only to produce your downloads and are deleted automatically afterwards. They are not shared, not reused and not used for training anything. Converted files contain whatever the original contained — including the user names Trados stores with each unit — so check them before passing them on.