The Additional settings page tunes how import & export behave.

Source language synchronization #️⃣

Choose whether to import source-language content from Localazy to Directus. When enabled, your Directus source-language values are replaced by the content in Localazy.

This is recommended when you wish to modify the source language directly from Localazy to make use of assistive localization features.

However, we generally recommend against importing the source language from Localazy, to keep Directus as the single Source of Truth. Instead, choose a source language you won’t use in production and only use languages translated in Localazy as user-facing languages. For example, users frequently choose Developer English as the source language in Localazy and then translate (i.e., proofread) into production-ready English. This way you benefit from a single Source of Truth while reviewing content with the translation-assistive tools Localazy offers.

Export translations from Directus #️⃣

When enabled, all translations of your Directus content — not just the source language — are uploaded to Localazy.

We recommend turning this option on for the initial synchronization of your existing translated content. Afterward, turn it off to speed up the export process and manage translations from Localazy.

Empty values #️⃣

Select whether to export fields with empty values to Localazy. By default, entries with empty fields are not exported since there is nothing to translate. Uploading empty values is useful when Source language synchronization is on and you want to finalize source content in Localazy.

Synchronize Localazy languages #️⃣

Choose whether to create languages in Directus that exist only in Localazy. There are multiple options.

Create non-hidden missing languages in Directus — create only languages that are not hidden in Localazy.

Create all missing languages in Directus — create all missing languages, including hidden ones.

Don’t create missing languages in Directus — missing languages are not synchronized. To support such languages, add them manually to the languages collection.

Language mappings #️⃣

When a Directus language code doesn’t match the code Localazy expects (or vice versa), add a language mapping so the two are linked explicitly. Each mapping pairs a Directus language code with a Localazy language code; the plugin uses these when deciding which Localazy language a Directus language corresponds to during import and export. This resolves the Unknown Localazy language state on the Overview page when you can’t change the underlying code.