Convert SDLTM to TMX without Trados (Beta)

Turn a Trados Studio translation memory (.sdltm) into TMX 1.4b, Excel and CSV, with fields, dates and users kept. Ready for memoQ, OmegaT, Phrase and Wordfast.

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.

      An .sdltm file is a Trados Studio translation memory. Other CAT tools can't read it, but almost all of them import TMX, the standard exchange format for translation memories. This page converts the .sdltm to TMX 1.4b without Trados Studio, for example when an agency sends its memory to a translator who uses memoQ, OmegaT, Phrase or Wordfast.

      How to convert SDLTM to TMX

      1. Find the file. File-based memories are single .sdltm files; Studio keeps them in a Translation Memories folder under Documents\Studio 20xx unless someone chose another place. Memories that live on GroupShare or in Trados Cloud aren't files, so export those to .sdltm or TMX from Trados first.
      2. Upload it. Several memories in one go are fine.
      3. Leave Inline tags on Keep tags unless you need plain sentences, for instance for a corpus or machine-translation training data.
      4. Download Name.tmx and import it into your CAT tool's translation memory. The same units also come as an Excel file and a CSV.

      What the TMX keeps

      • Source and target language codes exactly as Trados stored them (such as en-US, de-DE).
      • For every unit: creation and change dates, the users who created and changed it, the last-used date and user, and the usage count.
      • Custom fields, each value as a property named x-FieldName. The header lists the field types and picklist values the same way Trados writes them in its own TMX exports, so memoQ or another Trados installation can map them back to fields.
      • Formatting and placeholders as TMX tags (bpt, ept, ph).

      What is lost

      A Trados memory never contains the original formatting codes, only markers, so the tags in the TMX are empty markers; CAT tools handle this fine. Context information used for context matches and Trados' internal index data are not exported.

      Checking the memory in Excel

      The Excel file has one row per unit: ID, source, target, dates, users, usage count and a column for each custom field. It is handy for spotting junk before you import. Paired tags show up as <1>…</1>. A sheet that would exceed Excel's row limit continues on the next sheet, while the TMX and CSV are never split.

      The same upload page also converts termbases to TBX and packages.

      More about what this tool reads and writes: Trados File Converter (SDLTM, SDLTB, SDLXLIFF, SDLPPX).