Skip to main content
Native workspace glossaries support interchange through Platform. Provider-linked glossaries are read-only in Platform and follow different rules.

​
Supported formats

Exports use Hyperlocalise’s interchange profile: TBX 3 (TBX-Basic, DCA style), a concepts/terms CSV layout, and a two-sheet XLSX workbook.

​
Import in Platform

  1. Open Glossaries and select a native glossary (not a provider read-only glossary).
  2. Use Import and choose a TBX, CSV, or XLSX file.
  3. The file uploads directly to object storage, then the import is queued for asynchronous processing.
  4. Review the preview report, then confirm. Imports support preview, create, update, merge, and replace modes; destructive modes create a downloadable TBX backup before applying changes.
The UI polls the import report until it reaches a terminal state. Refreshing the page is safe: the report ID identifies the durable run and does not re-upload or re-apply the import. Open Import/export history from the glossary detail page to review past and in-flight runs. The list shows imports and exports with format, status, timestamps, and error summaries. Active runs refresh automatically. Open a run to read the full report. Completed exports offer a download; completed replace imports offer a TBX backup when one was created. You can leave the page while a run is queued—the history entry remains after the dialog closes. Provider-backed glossaries cannot be imported through this UI. Manage terms in the connected TMS or use a native glossary you control.

​
Export in Platform

  1. Open a native glossary, or a mirrored provider glossary stored in Hyperlocalise (a synced copy stored in Platform).
  2. Open the actions menu (⋯) → Export.
  3. Pick TBX, CSV, or XLSX for the full glossary, or use Export filtered glossary when the concept list is filtered by search or locale.
Exports are queued asynchronously. When the report is complete, use the signed download link from the report to retrieve the generated file. Live Crowdin glossaries are read-only in Platform and cannot be exported from the UI.

​
Provider glossaries

Use your TMS or the Hyperlocalise CLI for provider-native glossary downloads where supported. CLI glossary CSV is often a Hyperlocalise-shaped export and may not round-trip into every TMS upload endpoint.

​
Tips

  • TBX is the best interchange with other terminology tools.
  • XLSX is easiest for manual review and bulk edits in a spreadsheet.
  • CSV works well for scripts and narrow column-based tooling.
  • Crowdin TBX often uses short language IDs such as de while your glossary configures region-qualified locales such as de-DE. Platform maps those IDs to a matching configured locale when the mapping is unambiguous; terms are stored under your configured locale code.

​
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.