Trados File Converter (SDLTM, SDLTB, SDLXLIFF, SDLPPX) (Beta)

Open Trados files without Trados: SDLTM to TMX, SDLTB to TBX and Excel, SDLXLIFF to a bilingual Excel review file and back, SDLPPX packages unpacked.

Opens: SDLTM, SDLTB, SDLXLIFF, SDLPPX, SDLRPX
Saves: TMX 1.4b, TBX-Basic, XLSX, CSV, SDLXLIFF

Convert

Trados files
Choose files… or drop them here
.sdltm, .sdltb, .sdlxliff, .sdlppx, .sdlrpx, .zip · up to 200 MB each, 20 files max
    Add more files

    Translation memories (.sdltm), MultiTerm termbases (.sdltb), bilingual files (.sdlxliff) and project or return packages (.sdlppx, .sdlrpx). Several files at once are fine.

    More inputs
    Edited review spreadsheet (optional)
    Choose files… or drop them here
    .xlsx · up to 200 MB each, 20 files max
      Add more files

      Only to update a bilingual file: upload the original .sdlxliff (or its package) above and the review spreadsheet you edited here. You get the updated .sdlxliff back.

      Options

      Formatting and placeholders become TMX tags and <1>…</1> placeholders in spreadsheets. The SDLXLIFF review spreadsheet always keeps tags so it can be imported back.

      More options

      Only used when updating an SDLXLIFF from an edited spreadsheet: the confirmation status given to segments whose translation changed.

      Your files are deleted after processing.

      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 uploadYou get
      .sdltm translation memoryTMX 1.4b with languages, creation/change dates and users, usage counts and all custom fields; the same data as Excel and CSV
      .sdltb MultiTerm termbaseTBX-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 fileA 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 packageAn 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

      1. Upload the .sdlxliff (or the whole .sdlppx package) and download the review spreadsheet.
      2. 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.
      3. Upload the original .sdlxliff (or package) again, put the edited spreadsheet into Edited review spreadsheet, and convert.
      4. You get the updated .sdlxliff with 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 .sdltm or TMX first.
      • Trados does not store the original formatting codes in a memory, so tags in the TMX are empty bpt/ept/ph markers (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 .sdlxliff files, not as a new .sdlrpx return 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.

      Frequently asked questions

      Do I need Trados Studio or MultiTerm installed?

      No. The files are read directly: .sdltm translation memories are SQLite databases, .sdltb termbases are Access (Jet) databases with the entries stored as XML, .sdlxliff files are XLIFF 1.2 and packages are ZIP archives. Everything is converted on our server; nothing needs to be installed.

      How do I get a Trados translation memory into memoQ, OmegaT, Phrase or Wordfast?

      Upload the .sdltm file and download the TMX. memoQ: Resource console → Translation memories → create or open a TM → Import from TMX. OmegaT: copy the TMX into the tm/ folder of your project. Phrase: Translation memories → Import. Wordfast Pro: TM → Import TMX. Custom fields become TMX properties (x-FieldName) that memoQ and Trados can map on import.

      Which TBX flavour do you produce?

      TBX-Basic in the TBX 2008 (ISO 30042:2008) martif syntax, validated against the TBX-Basic schema. This is the TBX that memoQ, OmegaT, Phrase and Wordfast import. Subject, definition, context, status, gender, part of speech and term type are mapped to TBX-Basic categories; other MultiTerm fields are kept as notes, so nothing is dropped.

      Can I edit an SDLXLIFF in Excel and get an SDLXLIFF back?

      Yes. Convert the .sdlxliff to the review spreadsheet, edit the Target column (keep the numbered tags such as <1>…</1>), then upload the original .sdlxliff together with the edited spreadsheet. Changed targets are written back, tags are validated, locked segments are left alone and every other byte of the file stays unchanged, so Trados opens the result normally.

      Is there a size limit?

      Files up to 2 GB are accepted and translation memories are streamed, so memories with hundreds of thousands of units work. Excel sheets are split at Excel's row limit of 1,048,576 rows; the TMX and CSV files are never split.

      What happens to my files?

      They are processed on our server only to create your downloads and are deleted automatically afterwards. They are not used for anything else, not shared and not used to train anything.