--- title: Improved Language and Locale Support in TYPO3 v12 url: "https://b13.com/knowledge/multilanguage-use-any-locale-now-in-typo3-v12" description: TYPO3 v12 introduces better support for languages and locales, including BCP 47 format, automatic fallbacks, and reduced configuration overhead for setting up new languages. image: "https://b13.com/fileadmin/_processed_/5/1/csm_Multilangual_Sharing_44638c6c64.png" date: 2024-04-30 modified: 2026-08-19 lastUpdated: 2026-08-19 --- # Improved Language and Locale Support in TYPO3 v12 [ TYPO3 v12 ](https://b13.com/knowledge/typo3-v12) [ TYPO3 ](https://b13.com/knowledge/typo3) [ Localization ](https://b13.com/knowledge/localization) Multilanguage—Use any Locale now in TYPO3 v12 =============================================== ![](https://b13.com/fileadmin/_processed_/c/6/csm_benni_5e519221c4.jpg)Benni Mack 02 May 2024 [ RSS Feed ](https://b13.com/rss.xml) ![A globe with four yellow location markers is surrounded by dotted lines and paper airplanes, symbolizing global communication and connectivity.](https://b13.com/fileadmin/_processed_/7/8/csm_Multilangual_Headerbild_b6e34b835b.webp) **Languages have infinite possibilities—so should your multilingual website** By default, TYPO3 uses English as the base language, and ships with a mechanism to translate text strings into other languages. Strings include all text in the backend user interface (UI) as well as the frontend or output of your website. Common text strings might be the words on a button such as “Log In” - these words are not handled as content but rather are stored in external translation files. One of TYPO3’s strengths is its long-lasting migration path from previous versions—so any changes to the handling of translation files is done with maximum backwards-compatibility in mind. This article explains the basic idea of language and locales related to translation files in a CMS context—from choosing the language, their variations, and their format—and how TYPO3 has slowly shifted to the concept of using locales as a better identifier of the used language and its variation. The Rigid Past—TYPO3 and Language Challenges ---------------------------------------------- The admin interface and all TYPO3 plugins are English by default, and all labels reside in files of the XLIFF standard. But before v12, the way TYPO3 approached language had some quirks. The TYPO3 “supported languages” is a [fixed list of “language codes](https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/core/Classes/Localization/Locales.php#L31-L122)“ (such as ”de“ for German) which Kasper Skarhooj originally introduced over 20 years ago. Over time, the list has expanded to over 57 supported languages. The TYPO3 [Localization Team](https://typo3.org/community/teams/localization) works hard to translate the English strings and labels into these languages. In mid-2023, the [translation for TYPO3 in Arabic](https://typo3.org/article/typo3-fully-translated-to-arabic) was completed. This is a great community effort and an amazing system that works well. Every TYPO3 installation can download additional “language packs” for their extensions—even third-party extensions—in any of the 57 supported languages. When using German for a site language or an editor in the TYPO3 backend, the Localization system automatically checks for available language packs in the local setup. It references a “de.mylabels.xlf” file, checks for the label, and returns it. If the label doesn’t exist in the XLF file, it falls back to the English version. However, the challenge comes when a project needs to use a different “language” for a different version of a language, for example, German for Switzerland. This is where “locales” come into play. The format usually is bound to a [Locale system](https://en.wikipedia.org/wiki/Locale_(computer_software)) where “de” is the ISO 639 language code (2 letters in lowercase), and an optional 2-letter country code (ISO 3166–1 alpha 2) separated by an underscore—resulting in “de\_CH”. Previously, you could “add” an additional language with any format, such as “de\_CH” (or any other kind of way), but you also needed to define the system to fall back to “de” and then to English, to override any necessary words or sentences. Once manually registered and defined as a “dependency” in TYPO3 (until v11), the language system then checked for “de\_CH.mylabels.xlf” — then, for a “de.mylabels.xlf” and then for the fallback to “mylabels.xlf”, when referenced. For the website output, language setup is handled in the Site Configuration. One example for a setting would be to define if a language or locale for your website should be rendered “right to left” or “left to right”. For editors, there are a lot of different language settings in Site Config that make it complicated to use. ![Language settings interface with options for selecting language, entry point, and localization details. Features fields for website title, navigation title, and a grid of flags representing various countries.](https://b13.com/fileadmin/_processed_/4/2/csm_Bildschirmfoto_2024-04-30_um_11.07.16_7d64130632.webp) BCP 47 — A standardized format for the Web -------------------------------------------- Although TYPO3 lets you construct a format to specify additional languages, there is actually a web standard format. The HTML standard for locales is built on a standardized code called [IETF BCP 47 language tag](https://en.wikipedia.org/wiki/IETF_language_tag). Rather than an underscore, each language tag is composed of one or more “subtags” separated by hyphens (-). For example, Swiss German looks like “de-CH”, but the format can also contain additional regions such as “nan-Hant-TW” (that’s Min Nan Chinese using traditional Han characters as spoken in Taiwan). TYPO3 v12 Improvements ------------------------ TYPO3 v12 ships with a list of all ISO 639 language codes, which can literally be combined with any other Country or Region code, *and* handles the fallback automatically. The fixed list of ISO 639 letter codes as defined in TYPO3 Core is still valid—but the changes introduced in version 12 should result in a reduction in the direct usages of the two-letter “language” format. In addition, a Locale class has been introduced, which can handle both BCP 47-like formats as well as previous syntax formats. When referencing a translation file then, the Locale is used and the fallback logic for multiple languages applies automatically. `$languageService = $languageServiceFactory->create(new Locale('de-CH));` `$myTranslatedString = $languageService->sL('LLL:EXT:my_extension/Resources/Private/Language/myfile.xlf:my-label');` In addition, the necessary options for setting up a new Language in TYPO3 v12 have been drastically reduced, so it’s now easier than ever to configure a new language: ![A user interface displaying fields for entering details such as title, location, alternative attributes, entry point, and navigation title, with options for language settings and website-related information.](https://b13.com/fileadmin/_processed_/5/3/csm_Bildschirmfoto_2024-04-30_um_11.07.59_d7a835bcae.webp) Most values such as right-to-left handling, and even the hreflang tags are now derived from the locale. For all extension authors, TYPO3 now includes a list of all ISO 639–1 and ISO 639–2 codes (two- and three-letter language codes), including official language names, in a common available PHP class `\\TYPO3\\CMS\\Core\\Localization\\OfficialLanguages` — in all available translations for TYPO3 supported languages. Locales all the way --------------------- TYPO3 v12 can make life easier if your requirements need it with languages and Locales. From setting up new languages, reducing configuration overhead, and adding custom language-country-region combinations, everything is possible now with TYPO3 v12. We are really happy that TYPO3 as a leading open-source content management system can solve all the needs of our clients, and we haven’t seen any comparable system with similar capabilities yet. Do you have a special case regarding languages or translations for your website? Reach out to us! [ Get in touch. ](https://b13.com/lets-connect) ### Written by: ![Bild von Benni Mack](https://b13.com/fileadmin/_processed_/c/6/csm_benni_66cce9a81f.webp) b13 co-founder and TYPO3 CMS Core Development Lead, Benni Mack, heads our technical practices, setup and maintenance of our technical infrastructure, and coordinates our open-source contribution. His essential tool: TYPO3 Benni Mack CTO [ more from Benni Mack ](https://b13.com/team/benni-mack) Related Articles ------------------ - ![Cartoon trophy character surrounded by hands giving thumbs up and a heart gesture, set against a gear-patterned background.](https://b13.com/fileadmin/_processed_/f/7/csm_T3ppy_Design_Kit_Headerbild_b51eb9dc31.webp) ### T3ppy Gives TYPO3 a Friendly Face 06 August 2026 | Florian “Flix” Keitgen TYPO3 is powerful—but it doesn’t have to feel impersonal. Meet T3ppy, our friendly companion for the backend. [ Read more: T3ppy Gives TYPO3 a Friendly Face ](https://b13.com/knowledge/t3ppy-design-kit) - ![Gavel labeled "AI" on a circuit-patterned background with yellow stars, symbolizing regulation or legislation related to artificial intelligence in the EU.](https://b13.com/fileadmin/_processed_/1/0/csm_EUAIAct_Headerbild_510724b3de.webp) ### AI Content in TYPO3: Labelling Needs Accountability 02 August 2026 | Benni Mack The EU AI Act brings the origins of AI-generated content into focus. AI Label marks AI-generated and AI-edited content in TYPO3 and records who signed off the published version—for… [ Read more: AI Content in TYPO3: Labelling Needs Accountability ](https://b13.com/knowledge/ai-content-in-typo3-labelling-needs-accountability) - ![A series of stylized figures in various poses, each with a distinctive orange hat, depict a progression from walking to standing still while looking at a phone, set against a purple grid background.](https://b13.com/fileadmin/_processed_/d/7/csm_QueuesDDEV_Headerbild_f640931350.webp) ### Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 10 April 2024 | Jochen Roth When built-in message transports hit their limits, RabbitMQ can provide TYPO3 with a scalable, robust message queue. [ Read more: Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 ](https://b13.com/knowledge/better-scalability-with-decoupled-queues-how-to-set-up-rabbitmq-with-typo3) - ![A cartoon character resembling a shield gives a thumbs up in front of a computer interface with various menu options.](https://b13.com/fileadmin/_processed_/e/6/csm_Header_cda1f80173.webp) ### Meet T3ppy: A New Era for Editorial Work in TYPO3 01 April 2026 | Florian “Flix” Keitgen T3ppy and the AiM extension bring AI directly into the TYPO3 backend—enhancing SEO, content quality, and workflows with centralized control. [ Read more: Meet T3ppy: A New Era for Editorial Work in TYPO3 ](https://b13.com/knowledge/meet-t3ppy-a-new-era-for-editorial-work-in-typo3) - ![Retro microphone illustration with a shopping cart icon in the background, symbolizing e-commerce or online shopping.](https://b13.com/fileadmin/_processed_/f/8/csm_Marketplace_Headerbild_ee1575614c.webp) ### Why TYPO3 Needs a Marketplace for Products 25 March 2026 | Florian “Flix” Keitgen A marketplace would make TYPO3 products more discoverable, easier to compare, and benefit both agencies and clients alike. [ Read more: Why TYPO3 Needs a Marketplace for Products ](https://b13.com/knowledge/why-typo3-needs-a-marketplace-for-products) - ![A hand holding a magnifying glass over a laptop screen displaying a webpage with an image and text elements.](https://b13.com/fileadmin/_processed_/e/5/csm_BackendUserSection_Headerbild_6093c842fd.webp) ### Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6) 05 March 2026 | David Steeb Discover TYPO3’s underrated doktype 6 (Backend User Section) for secure internal previews, editor training, and prototyping. Learn real use cases, common pitfalls like 403 errors… [ Read more: Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6) ](https://b13.com/knowledge/backend-user-section-in-typo3-uses-pitfalls-helper) - ![Two stylized web page designs featuring a user profile, image placeholders, and text sections, set against a light blue background.](https://b13.com/fileadmin/_processed_/2/0/csm_BackendPreview_Headerbild_b4c5799cfa.webp) ### Backend Previews With a System—Why We Built EXT:backendpreviews 09 February 2026 | David Steeb EXT:backendpreviews brings structure and consistency to content previews in the TYPO3 backend using Fluid templates, layouts, and partials. [ Read more: Backend Previews With a System—Why We Built EXT:backendpreviews ](https://b13.com/knowledge/backend-previews-with-a-system-why-we-built-extbackendpreviews) - ![A human hand shakes a robotic hand against a purple background with heart patterns, symbolizing collaboration between humans and technology.](https://b13.com/fileadmin/_processed_/6/2/csm_AIbotsLoveMarkdown_Headerbild_72fe5820d6.webp) ### The Internet Is No Longer Just for Humans—AI Bots Love Markdown 28 January 2026 | Benni Mack Discover why most web traffic is now automated and how TYPO3’s structured content model prepares websites for humans, editors, and AI systems. [ Read more: The Internet Is No Longer Just for Humans—AI Bots Love Markdown ](https://b13.com/knowledge/the-internet-is-no-longer-just-for-humans-ai-bots-love-markdown) - ![Several colorful web page mockups stacked together, showcasing different layouts and design elements against a purple background.](https://b13.com/fileadmin/_processed_/e/3/csm_CaminoTheme_Headerbild_d082598009.webp) ### Camino—The Need for a Default Theme in TYPO3 Is Real 27 January 2026 | Benni Mack With TYPO3 v14, Camino introduces a default theme that removes friction from first installs. Why this matters—and how TYPO3 laid the groundwork. [ Read more: Camino—The Need for a Default Theme in TYPO3 Is Real ](https://b13.com/core-insights/blog/camino-the-need-for-a-default-theme-in-typo3-is-real) - ![Graphic featuring stylized representations of a tower with the text "T3CON25 Düsseldorf" prominently displayed in the center.](https://b13.com/fileadmin/_processed_/7/b/csm_T3CON2025_Headerbild_fc9c5cc53e.webp) ### T3CON25—One Step Closer to the Future of Content Management 10 December 2025 | Franzi Töpler T3CON25 showcased the future of TYPO3 with insights on TYPO3 v14, AI, digital sovereignty, and open-source solutions driving secure, modern web experiences. [ Read more: T3CON25—One Step Closer to the Future of Content Management ](https://b13.com/knowledge/shaping-the-future-of-content-management-t3con25)