Download target files
- Open the project’s files view and select Download translations.
- Select one or more Source files.
- Choose a Target locale.
- Select Download and check each file’s result.
.strings and properties download in their own format, with ready translations filled in and other strings left as the source has them. A CSV or TSV file gets the translations in the column its source text was read from; other columns stay as they are. If a file cannot be written in its own format, its translations download as a .json file instead.
You need source files and at least one target locale. Check the generated files in the destination application, including placeholders and formatting, before publishing them. A downloadable file is not a guarantee that every segment has been reviewed.
Export a filtered queue
- Open the Content Editor.
- Set Filter queue and search to select the intended segments.
- Open the queue toolbar’s Download and choose a format.
- Verify the locale, keys, and row count in the exported file.
Re-import a bilingual file
On a native project, open More actions → Import bilingual file… in the Content Editor and upload the CSV, TMX, XLF, XLIFF, or XLSX file you exported. Matching keys in the current locale are updated. Empty targets are skipped. The import is scoped to the open file, or to every file on the all-files queue, and it uses the same 5,000-string cap. Use this after you repair inline tags or placeholders in an external tool. Verify the saved strings in the editor before you approve. Provider-backed projects cannot re-import bilingual files. XLF and XLIFF exports mark machine text no one has changed withstate-qualifier="mt-suggestion", so CAT tools show it as a machine suggestion. A re-import counts as a person’s edit: changed machine text becomes Machine, post-edited, and unchanged text keeps its label. See Machine or human.

