TYPO3

TYPO3 as an enterprise CMS for large sites

TYPO3 is an open-source enterprise CMS from the German-speaking world, built for large, multilingual sites with many editors, fine-grained permissions and a predictable version cycle.

TYPO3 was started in 1997 by Kasper Skårhøj and first released publicly in 2001; today the non-profit TYPO3 Association carries the project. It is written in PHP and licensed under the GNU General Public License (version 2 or later). Its strength is not the quick landing page but the large, long-lived portal: many languages, many editors, clear roles. This page describes what TYPO3 is suited for, how its LTS cycle works, and where its learning curve lies.

Core concept

TYPO3 cleanly separates content, configuration and presentation, and is built from the ground up for multilingualism and multiple sites in one installation. Several domains, language trees and editorial areas can run inside a single TYPO3 instance instead of one separate installation per market.

• Multilingualism and multisite. Site handling manages several sites with their own domains and languages centrally. Translations hang off the original content as language variants rather than as separate copies.
• Permissions and workspaces. A fine-grained permission model with backend user groups governs who may edit what. Workspaces let editors gather changes and approve them before publication.
• Extensibility. Features arrive as extensions via the TYPO3 Extension Repository or through Composer. The File Abstraction Layer (FAL) manages media centrally and independently of the storage source.

This points TYPO3 at the same demanding applications as Drupal, while WordPress and Grav CMS are stronger on lighter, faster sites. Where the application is less a portal than a bespoke web application, the path runs through a pure framework such as Symfony instead.

Where it fits

TYPO3 is standard software for content, not a bespoke system; the reasoning behind that trade-off is described in standard software.

• Suited for: large corporate and group sites, public administrations, universities and associations with many languages, many editors and long lifespans.
• Advantage: native multilingualism and multisite, a strong permission and approval model, and a predictable LTS cycle that gives investment security over years.
• Learning curve: TYPO3 has a markedly higher barrier to entry than WordPress or Grav. The backend, its concepts (TypoScript, site configuration, FAL) and its operation all require ramp-up; productive use assumes experienced developers and editor training.

The LTS cycle

The predictable version cycle is one of the strongest arguments for TYPO3 in long-lived projects. Each major version ships as Long Term Support (LTS) and then runs through fixed phases, so update windows can be planned years in advance:

timeline
    title TYPO3 release lifecycle
    Sprint releases : development of the major version
    LTS release : stable major version
    Active maintenance : bug fixes for about 18 months
    Security phase : security fixes until about 3 years after LTS
    Free support ends : check ELTS
    ELTS : paid support for up to 4 more years

In concrete terms for the current line: version 12.4 LTS was released in April 2023, version 13.4 LTS in October 2024, and version 14 LTS arrived in April 2026 as the major version recommended for new projects. Once free support ends, a version can be kept secure through Extended Long Term Support (ELTS). ELTS is a paid offering from TYPO3 GmbH and can extend support by up to four more years depending on the version. Following the cycle actively avoids the jump across an outdated, unmaintained installation that legacy modernisation otherwise has to untangle.

Licence and vendor lock-in

TYPO3 is released under the GPL; the source code is open and free of licence fees, and the choice of an open-source licence weakens vendor lock-in because the code is not tied to a single vendor. TYPO3 still costs money: in operation, development, hosting and, for older versions, optional ELTS. Behind the project sits an ecosystem of the TYPO3 Association as the non-profit steward and TYPO3 GmbH, which offers commercial services such as ELTS. That separation keeps the core open while funding long-term maintenance.

Where TYPO3 does not fit

• Small, fast sites. For a marketing site or landing page, TYPO3 is oversized. Here WordPress or Grav reach the goal faster.
• Without developer support. TYPO3 earns its value with clean configuration and maintenance. Without an experienced team the learning curve becomes a permanent burden.
• Missing update discipline. The LTS cycle is only an advantage if the updates are actually applied. An installation two major versions behind loses the security and planning benefit.

In the German-speaking world, TYPO3 is traditionally widely used and ranks among the most-used CMS in Germany; a comparable enterprise CMS also rooted in the DACH region is Contao, which pursues a similar ambition with a smaller feature set.

References

• TYPO3 Association Release roadmap and maintained versions. Lifecycle of the LTS versions with active, security and ELTS phases. (2026). get.typo3.org
• TYPO3 GmbH Extended Long Term Support (ELTS). Paid extension of support by up to four years after free maintenance ends. (2026). typo3.com/products-services/extended-support-elts
• TYPO3 Association Release notes TYPO3 CMS 13.0. Start of the version 13 line on the way to the LTS release in October 2024. (30.01.2024). get.typo3.org/release-notes/13.0.0
• TYPO3 Core Source code repository. Open-source enterprise CMS under the GNU GPL (version 2 or later); project history since 1997. (2026). github.com/TYPO3/typo3

---

Related topics

• Drupal, the second open-source enterprise CMS for complex portals.
• WordPress, the lighter choice for marketing sites and SMEs.
• Grav CMS, the flat-file CMS for fast, lean sites.
• PHP, the language TYPO3 is written in.
• Standard software, the make-or-buy view behind a standard CMS.
• Vendor lock-in, why the open licence weakens the binding.