Skip to converter

TMX 1.4b translation memory (restricted) to CSV Converter.

Convert supported bilingual segments from TMX 1.4b translation memory (restricted) into CSV locally, without uploading translations.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTTMX 1.4b translation memory (restricted)
OUTPUTCSV
Files stay on your device

Up to 2 MiB · 1–1,000 plain-text bilingual segments · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert TMX 1.4b translation memory (restricted) to CSV

  1. Choose a source file. Select a real TMX 1.4b translation memory (restricted) file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated CSV file. Your original file is unchanged.

FORMAT GUIDE

Why convert TMX 1.4b translation memory (restricted) to CSV?

Transfer curated translation pairs between basic TMX, XLIFF and spreadsheet review workflows.

  • Reviewing English and Bengali translation pairs in a spreadsheet.
  • Preparing a restricted TMX memory from an approved bilingual CSV.
  • Exchanging supported plain-text translation units with an XLIFF-oriented workflow.

UNDERSTAND YOUR FILES

TMX 1.4b translation memory (restricted) vs. CSV: what changes?

Input · TMX 1.4b translation memory (restricted)

Output · CSV

Comma-separated tabular text; quotation marks may enclose commas and line breaks within fields.

Transfer curated translation pairs between basic TMX, XLIFF and spreadsheet review workflows. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Only the strict NGInfinite plain-text profile of TMX 1.4b or XLIFF 1.2 is accepted. The five spreadsheet columns must be exactly id, source_lang, target_lang, source_text, target_text, in that order. Each file holds 1–1,000 unique segments for one language pair, with short BCP-47-style tags and single-line Unicode text. File size is limited to 2 MiB. XML language variants, translation IDs and segment text are preserved. Existing rich TMX/XLIFF exports with additional attributes, alternate translations, inline elements, notes, workflow approvals, skeletons, contexts, placeholders or other metadata are rejected instead of being silently simplified. These tools convert existing translations; they do not translate text or verify translation quality. Preserve your originals and check compatibility with your translation software.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

TMX 1.4b translation memory (restricted) to CSV questions

Does this machine-translate my content?

No. It only changes the format of translations already provided in the source file.

Which columns must tables contain?

Exactly: id, source_lang, target_lang, source_text, target_text.

Will any TMX or XLIFF file work?

No. Unsupported rich metadata and inline markup are deliberately rejected.