---
title: "TYPO3 Translation Handling: How to start off right"
url: "https://b13.com/knowledge/localization-part-2-a-guide-to-setting-up-your-typo3-translation-workflow"
description: "The #TYPO3 CMS makes it easy to launch a truly multilingual website. But sometimes figuring out how to update your website’s multiple translations can take a few tries. Here’s how we at b13 help our clients set up their translation workflows."
image: "https://b13.com/fileadmin/_processed_/7/6/csm_lcalization-pt2_191-1_4f4296232a.png"
date: 2022-11-02
modified: 2026-08-19
lastUpdated: 2026-08-19
---

# TYPO3 Translation Handling: How to start off right

[ Core-Development ](https://b13.com/knowledge/core-development) [ TYPO3 ](https://b13.com/knowledge/typo3) [ Project Management ](https://b13.com/knowledge/project-management)

 Localization, Part 2: A Guide to Setting Up your TYPO3 Translation Workflow
=============================================================================

![](https://b13.com/fileadmin/_processed_/c/6/csm_benni_5e519221c4.jpg)Benni Mack

  02 November 2022

 [ RSS Feed ](https://b13.com/rss.xml)

  ![localization workflow](https://b13.com/fileadmin/_processed_/0/e/csm_lcalization-pt2_4e4299cab5.webp)

**Some initial planning can make localization much simpler. Here’s how we help our clients set up their workflows for smooth, efficient translations in TYPO3.**

  In the [first post](https://b13.com/knowledge/localization-part-1-how-localization-works-in-typo3) of our localization series, we described how TYPO3 manages localization and makes it easy to run a truly multilingual website. Whether you’re a one-person operation or part of a large global company, you’ll want translations to appear effortless to your website’s visitors. So while you’re getting into the weeds of setting up your translation workflow, read on for some tips on how to configure your TYPO3 backend.

   Need help localizing your website? Get in touch!
--------------------------------------------------

 [ Let’s connect ](https://b13.com/lets-connect)

   Choose your Page Tree structure first
---------------------------------------

Before translating any single piece of content, you’ll want to decide on a Single Tree vs. Multi Tree approach. This decision should be based on your project’s needs. If every locale needs to manage their own websites independently (for example, if countries launch most products on different timelines), we recommend the Multi Tree approach. In that case, each local website will have its own Page Tree—which means local independence, but higher maintenance.

If you need a more unified website across translations, regions, or countries, we recommend using the Single Tree approach, which puts all locales under the same Page Tree. We use a Single Tree structure for most of our clients‘ projects because it allows for connected translations—so, within the TYPO3 backend, there is a clear view of which content has been translated and which has not. If you want to translate a page heading, for example, you can view all the translations in a single frame in the TYPO3 backend.

  ![Two sections displaying content management options for a blog, one in English and one in German. Each section includes a header and a brief description about using TYPO3's language features for multilingual setups.](https://b13.com/fileadmin/_processed_/6/a/csm_Localization_Part1_Conneted_mode_482cb7a6ea.webp)

   Configure your website’s localization settings
------------------------------------------------

Once you’ve decided on a Page Tree structure, it’s time to select your website’s main language. In TYPO3, this is called the “default language.” For a Multi Tree approach, each Page Tree will have its own language, and translation workflows will have to be managed by your organization’s internal operations, rather than from within TYPO3. The rest of this post concerns the Single Tree approach, which offers more configuration options at each level of content.

If you opt for a Single Tree approach, you’ll need to configure the following settings at the root level:

- **A Source Language**, or the default language for your entire website; each element will be connected to that source language
- **Entry points,** (i.e. domains) on a language level—we use b13.com for our English site and b13.com/de/ for our German-language site
- **Fallback languages**, that tell your website which language(s) to use if a piece of content is not translated

   Tip:
------

While you might be tempted to choose a default language based on, say, the location of the company headquarters, we recommend thinking more broadly about your organization’s needs. So if you work for a company based in Paris, but a lot of your business is conducted in English, it would probably make sense to use English as your Source Language.

   Use a localization manager to set up your workflow
----------------------------------------------------

While you don’t have to use an extension to localize your website, the more content you add or change, the harder it can be to keep up with translations. Many larger organizations use third-party translation services or have field offices that manage translations—and professional translators shouldn’t have to be TYPO3 users. A localization manager allows you to export content for translation and import translated content back into your TYPO3 backend.

If you have more than a few page’s worth of content to translate, we recommend installing a well-tested, third-party extension like the L10N Manager to manage your translations. Any piece of content containing text can be handled through the L10N Manager (co-developed by b13). Other solutions for TYPO3 include adapters, like [LanguageWire.com](https://www.languagewire.com).

  Through the L10N Manager extension, you can configure settings for your website’s content requiring translation, including:

- **Depth of translation** (entire website, a subset of pages, or a single page)
- **Target languages**
- **Type of content to translate** (i.e. metadata, content types, page headings, etc.)
- **Content excluded from translation**

  This configuration will create a settings file, so when your content is passed on to translators, they have a guide as to how the website is structured and how translations should be managed.

  Once you’re ready to translate your website’s content, you can export the file through the L10N manager. Through this UI, you can select:

- Target languages
- Whether to limit the file to recently updated or added content
- Format for translation file (available options include XML, CSVs, and inline editing)

  Click the Export button, and your file will be prepared. By exporting your file through the L10N manager, you can let field offices or third-party translation services perform translations outside of the TYPO3 backend, using clearly labeled Excel spreadsheets, XML file formats, or any other preferred format.

  ![L10N Manager interface displaying options for XML export/import, including target language selection, content filters, and export settings. Options for checking previously exported content and alternative source languages are also visible.](https://b13.com/fileadmin/_processed_/4/2/csm_L10N_Manager_503e152fed.webp)

  If you work for a large corporation with field offices or use a translation service provider, your translators will likely use translation memory systems. These memory systems (like SDL Trados, MemoQ, and more) will read the settings file produced by your L10N Manager configuration and places where the source language has changed, or where you might commonly use a word replacement.

Regardless of the size of your organization, once your content is translated, you can import it back into your website using the same L10N manager interface that you used to export your file. Once the new content is imported, it automatically updates fields where you’d previously had outdated or missing translations.

   Tip:
------

If you need to preview a set of translations before they go live, you can toggle a language’s visibility at the page level and default to your fallback language(s).

   Look out for localization updates in future TYPO3 versions
------------------------------------------------------------

While TYPO3 already offers a lot of great features, the team members at b13 are always thinking about how to contribute and improve the TYPO3 Core. In the future, we’d like to integrate translations with Workspaces, so users can set up approval processes and previews for translations.

In the meantime, b13 has experience building approval workflows and other custom localization features for our clients.

   Get in touch, and we’ll help you develop a solution!
------------------------------------------------------

 [ Let’s connect ](https://b13.com/lets-connect)

   Want to know how localization works in TYPO3?
-----------------------------------------------

 [ Check out Localization, Part 1 ](https://b13.com/blog/localization-part-1-how-localization-works-in-typo3)

  ###  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 rocket labeled "V14" launches into the sky, surrounded by a group of people celebrating with raised arms.](https://b13.com/fileadmin/_processed_/3/d/csm_v14_Celebration_Headerbild_3d4170fdc5.webp)

    ###  Happy Release Day TYPO3 v14: Why This Release Shows the True Strength of Open Source

     21 April 2026 | Florian “Flix” Keitgen

     TYPO3 v14 improves workflows for editors, marketing teams, and developers—and shows how community-driven open source creates real impact.

     [ Read more: Happy Release Day TYPO3 v14: Why This Release Shows the True Strength of Open Source ](https://b13.com/knowledge/happy-release-day-typo3-v14-why-this-release-shows-the-true-strength-of-open-source)
- ![Hands holding puzzle pieces with QR codes surround a large QR code under a magnifying glass, suggesting a collaborative activity.](https://b13.com/fileadmin/_processed_/3/b/csm_QRcodeManagement2_Headerbild_85c3ff55b5.webp)

    ###  QR Codes in TYPO3 v14: Built-in Link Management That Just Works for Editors

     17 April 2026 | David Steeb

     TYPO3 v14 adds QR code generation to Link Management. Create codes before URLs are final, track scans via redirect stats, update targets anytime, and avoid third-party tools. Ideal…

     [ Read more: QR Codes in TYPO3 v14: Built-in Link Management That Just Works for Editors ](https://b13.com/qr-codes-in-typo3-v14-built-in-link-management-that-just-works-for-editors)
- ![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)
- ![Hands holding a pencil and a circular token with characters, working on a digital interface displaying text and images.](https://b13.com/fileadmin/_processed_/7/e/csm_VisualEditor_Headerbild_33d4a1f19b.webp)

    ###  Visual Editing in TYPO3: When Content Management Happens in Context

     16 March 2026 | Florian “Flix” Keitgen

     Discover the Visual Editor by anders und sehr that enables true in-context content editing. Learn how Camino, the new frontend theme, and improved editorial workflows transform…

     [ Read more: Visual Editing in TYPO3: When Content Management Happens in Context ](https://b13.com/knowledge/visual-editing-in-typo3-when-content-management-happens-in-context)
- ![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)
- ![Multiple hands hold QR codes while one hand uses a magnifying glass to examine a larger QR code in the center.](https://b13.com/fileadmin/_processed_/0/1/csm_QRcodeManagement_Headerbild_5d9ec54194.webp)

    ###  Why we built QR codes into TYPO3: Bringing print campaigns under CMS control

     12 February 2026 | Jochen Roth

     QR codes generated outside your CMS break when pages move. TYPO3 v14.1 brings QR code management into the backend. Create, track, and retarget from one place.

     [ Read more: Why we built QR codes into TYPO3: Bringing print campaigns under CMS control ](https://b13.com/knowledge/qr-codes-in-typo3-bringing-print-campaigns-under-cms-control)