Export translations

This guide applies to the branch selected in Current branch. Keys, values, languages, tags and file mappings are independent between branches. See branch navigation and branch permissions.

Every current member, including Viewer, can export. Archived workspaces, projects and branches remain exportable. Output is generated in the background from one consistent database snapshot.

Choose the output

1. Open a project and select Export.
2. Choose File format and Languages. Active languages are selected initially. Load more languages exposes further pages; Select loaded languages selects the displayed set. Enable Include inactive languages explicitly to include inactive values.
3. Select Key status: Active (default), Archived or All keys.
4. Optionally set Include tags and Exclude tags. Include matches any selected tag. Exclude always wins, even if that same key matches Include. Empty Include means no inclusion restriction.
5. Choose the Missing policy below and review any format-specific mapping requirements.
6. Select Create download. Wait for completed status, then select Download.

A single output downloads directly. Multiple files are packaged into one ZIP. CSV/Excel with Don’t export produces one table per language, excluding Missing rows in each; this avoids turning an omitted value into a blank table cell. Other table policies produce one table containing the selected language columns.

Empty translations

Choice	File behavior
Export as empty strings	Missing values become empty strings where the format can represent them. This is the default.
Don’t export	Missing entries are absent from that language’s output.
Use source language	A Missing value uses the selected branch’s direct source-language value in the file only.

If the source value is also Missing, the output is empty and the result reports source missing. No fallback-chain lookup is performed. These options never fill the editor, alter Missing status, change fallback configuration, or create translation history.

Formats can impose stronger requirements. XLIFF needs source text; native parameterized entries need a known valid structure. An unrepresentable empty entry stops the export with a diagnostic instead of producing a broken file. Choose Don’t export or correct the content and create a new export.

Native file identities and parameters

Expand File identity and format options. Use the same File group as the import to reuse saved identifiers, context and argument order.

If the key name is invalid for a platform, choose Add output mapping and enter its key name or ID and a valid File identifier. The database key is not renamed. For positional parameters, enter an explicit Parameter order, such as count, person, unless import already recorded the order. It must contain every contract parameter exactly once. Apple cardinal arguments occupy the first position. Gettext plurals also need a plural message ID; context is optional.

JSON can use Export nested objects using periods in key names. Conflicting paths such as menu and menu.save cause an error; neither value is discarded.

Tables and formula protection

CSV uses a formula-safe profile by default, escaping formula-looking prefixes with an apostrophe. To reverse that escaping, select Localisync formula-safe export during re-import. Use Raw text for a raw CSV from another source. Excel cells are written as text, including strings that start with =. No formula or macro is executed.

Result and recovery

The result reports key/value counts, empty values, source substitutions and omissions. The download belongs to the creator and requires current membership. It expires after 24 hours, including after a successful download. Create another export for a later snapshot.

If conversion fails, inspect the diagnostics and expand Correct export options. The saved options remain available for correction. Retry export retries the same options against a fresh snapshot after a transient failure. No file is reported ready until its private storage write and completion receipt finish successfully.