You often already have a document and its finished translation, but no translation memory linking them. TM Alignment turns that pair into memory: it matches the source to its translation, segment by segment, and writes the result as a TMX file you can reuse. This guide explains the purpose and the options — above all, the three ways it can align.
A translation memory is only valuable if it is full. Every document you have already translated is potential memory — if you can pair the two sides up. TM Alignment does exactly that, taking a source file and its translation and producing reusable translation-memory pairs. You can then load the result as a memory in any project and benefit from the matches, as in guide 1.
Open TM Alignment and choose Create New Alignment Run. Like extraction, each run is saved so you can resume it later.
After naming the run, you pick how it will align. This is the most important choice, because the three methods suit different files and have different trade-offs.
| Type | How it works | Best for |
|---|---|---|
| Lightweight (LLM Alignment) | Uses a model to match the two sides. Quick to set up, and includes the privacy controls. Does not handle PDFs. | Most everyday documents, especially confidential ones. |
| External App (Advanced Alignment) | Uses a dedicated external server. More powerful, and it does handle PDFs. | Large or difficult alignments, and PDF sources. |
| Structural Alignment | Matches the two files by their structure, with no model at all. | Already-structured files such as XLIFF or XML. |
Now you set the languages, the output, the files, and — for the Lightweight type — the model and privacy.
| Option | What it does |
|---|---|
| Source / Target Language | The two languages. Detected automatically for XLIFF and similar; set by hand for other files. |
| Output Mode | Pool everything into one TMX file, or write a separate TMX for each pair of files. |
| Extraction LLM | For Lightweight alignment, the model that does the matching. Choose it with Change…. |
| Anonymizer / Obfuscation / Boilerplate | The privacy profiles, applied before text reaches the model and restored afterwards. |
| Alignment Prompt | The prompt that guides the model. Required for Lightweight alignment. |
| HTML/XML Filter (Optional) | An XPath or CSS selector to align only part of a web page or XML file. |
| Minimum words/characters per batch | How much text is matched at a time. |
| Source Files / Target Files | The documents to align. Add them from disk or by URL. |
The Lightweight type sends text to a model, so it carries the full privacy toolkit. Attach an Anonymizer or Numerical Obfuscation profile and your confidential content is masked before alignment and restored after — the same protection as everywhere else.
If you added several files on each side, you tell the wizard which source goes with which target. Auto-pair by Name matches them by filename, or you select a source and a target and Pair Selected. A status line warns you if any file is still unpaired.
Start the alignment and watch its progress — elapsed time, pairs processed, and segments aligned. When it finishes, a summary shows how many pairs and segments were produced.
Use View Results to read the aligned pairs side by side and check the match is sound. Then Finish & Save TMX writes the memory to disk — one pooled file, or a set of files, depending on the output mode you chose.
The results viewer is for checking, not editing. If a pair needs correcting, save the TMX and open it in the TM editor, where you can adjust entries directly.