Skip to main content
Native workspace translation memories support interchange through Platform. External TMS memories follow different rules when they are not mirrored locally.

Supported formats

TMX is TMX 1.4 with inline codes, tuid upsert, and locale-pair variants. CSV uses a Hyperlocalise row layout (header row with source_locale, target_locale, source_text, target_text, match_score). The importer also accepts Crowdin-style locale-matrix CSV (locale codes as column headers).

Import in Platform

You can upload a TMX or CSV file when you create a workspace memory, or import into an existing memory you can edit.
  1. Open Translation Memories.
  2. Choose Import TMX or CSV (or Create memory and attach a file), or open a memory and choose Import.
  3. The import runs a background preview and opens a report with counts, sample entries, and diagnostics.
  4. Review the report, then choose Import entries to write the segments into the memory. Until you confirm, nothing is applied.
  5. If the report shows a size or entry limit, split the file into smaller batches and import each batch separately.

Export in Platform

  1. Open the memory and choose Export.
  2. Select TMX or CSV.
  3. Either download all locales or pick a source and target locale pair to filter the file.

External TMS memories

Use your TMS or the Hyperlocalise CLI for provider-native TM download shapes where supported (csv or tmx depending on provider). CLI CSV is often Hyperlocalise-shaped and may not match every TMS upload format.

Tips

  • Prefer TMX when moving segments with inline tags or stable tuid values between memories.
  • Prefer CSV for spreadsheets, quick edits, or scripts.
  • Re-importing an exported TMX from Hyperlocalise is supported; treat CSV as the canonical flat row format for native memories.

Check the result

Inspect the reported counts, locales, and representative entries after import. Keep an export before a bulk replacement. If terms or suggestions are missing, confirm that the resource is linked to the intended project and uses the expected locales. See Translation quality.