{"section":"tutorials","requestedLocale":"en","requestedSlug":"understanding-locale-fallback-rules","locale":"en","slug":"understanding-locale-fallback-rules","path":"docs/en/tutorials/cms/configuring-locales/understanding-locale-fallback-rules.md","branch":"main","content":"When [configuring locales](/en/docs/tutorials/configuring-locales), some types of content don't need localization. For example, you may have a banner image without text or a brand name that remains the same across all languages. Fallback strategies help you avoid duplicating this kind of content unnecessarily. Below are two common approaches:\r\n\r\n| Use case | Description |\r\n| :---- | :---- |\r\n| [Default locale as fallback for other locales](#default-locale-as-fallback-for-other-locales) | Use when most content is shared, and other locales only override specific differences. |\r\n| [Core language fallback with regional variations](#core-language-fallback-with-regional-variations) | Use when managing regional variations that inherit from a core language locale. |\r\n\r\n## Default locale as fallback for other locales\r\n\r\nIn this strategy, all core content is stored in the default locale (for example, `English - US`). Other locales inherit content from the default locale and only override fields when localization is required. This means you only translate or modify content when it differs from the default. This approach works well when:\r\n\r\n* Most content is shared across languages.\r\n* Localization differences are minimal.\r\n\r\nIn the example below, we have two locales:\r\n\r\n* `English-US` (default)\r\n* `Portuguese-BR`\r\n  * Fallback: `English-US`\r\n\r\nIf a description isn't translated into Portuguese, the system automatically displays the `English-US` content instead. You only localize fields in `Portuguese-BR` when the content needs to differ (for example, promotional text or region-specific messaging).\r\n\r\n## Core language fallback with regional variations\r\n\r\nThis strategy is useful when managing multiple languages and regional variations. You create a hierarchy where regional locales fall back to a core language locale. This approach is ideal when:\r\n\r\n* The store supports multiple regions with the same language.\r\n* Some languages share a base language structure.\r\n* You need layered fallback logic.\r\n\r\nIn the example below, we have set up the following locales:\r\n\r\n* `English-US` (default)\r\n* `English-UK`\r\n  * Fallback: `English-US`\r\n* `Spanish-ES`\r\n  * Fallback: `English-US`\r\n* `Catalan-ES`\r\n  * Fallback: `Spanish-ES`\r\n\r\n`English-UK` inherits content from `English-US` and only overrides specific regional differences (for example, \"pants\" to \"trousers\"). `Catalan-ES` inherits from `Spanish-ES` and only replaces content where Catalan is required."}