Localization lets an entry store different field values for different languages or regions. The default locale is en-US; additional locales can be added from an entry form when content needs translations.
How Locales Work
Each entry has a list of enabled locales. Every enabled locale can have its own values for text, rich text, slug, and other translatable fields. Non-translatable structure, such as the entry status and content type, stays shared across locales.
Use localization when the same content item should appear in multiple languages. Use separate entries when the content is structurally different or should follow a different publishing workflow.
Adding A Locale
Open an entry, choose the locale control, and add the locale you need. You can start with empty fields, copy values from another locale, or translate selected fields when translation is available.
Required fields must be completed for the locale you are saving.
Copying Content Between Locales
Copying from an existing locale is useful when most fields stay similar across languages. After copying, edit the copied values before publishing.
When rich text is copied, formatting and embedded content are preserved. Attachment and relation fields continue to reference the same files and entries.
Translating Fields
The entry editor can translate selected text fields from one locale into another. Translation is intended as a starting point, not a replacement for review. Always check names, slugs, technical terms, and formatted text before publishing.
Fields without text content are skipped. Fields that already match the target language may be left unchanged.
Manual localization is free. Auto translation uses AI Credits at EUR 0.25 per 1,000 processed words.
Publishing Localized Entries
An entry has one status shared across all locales. If an entry is published, each enabled locale can be requested through the API, but the quality of each locale depends on the values saved for that locale.
Before publishing, review every enabled locale that should be visible to API consumers.
Removing Locales
Removing a locale deletes that locale's saved field values from the entry. This cannot be undone from the manager. If the locale may be needed later, keep it enabled and leave the content as draft or incomplete until it is ready.
API Usage
The API supports reading and writing localized entry values with the locale parameter. See Entry Localization for endpoint examples.
Related Pages
- Entries - Entry lifecycle and management.
- API Entries - Entry CRUD via the API.
- Entry Localization - Locale parameter reference for API endpoints.