TYPO3

Last reviewed Sep 13, 2026 · 775 words

TYPO3 is the right CMS for a 40-site, 12-language corporate estate with a team of editors and an agency on retainer, and the wrong one for nearly everyone reading a self-hosting directory. It needs 1 GB of RAM as a floor, a PHP developer who has learned TypoScript and Fluid, and a willingness to treat the CMS as a platform rather than a product. Those are the terms. In exchange you get the most disciplined editorial permissions model in open-source PHP, page trees that scale to tens of thousands of pages, and a long-term support cycle that organisations can plan budgets around.

The estate it was built for

TYPO3 dates from 1998 and grew up in German-speaking Europe serving universities, ministries and industrial companies. Its core abstractions reflect that. One installation hosts many sites in a single page tree; every page and content element can exist in every configured language with fallback rules; editors get backend groups with permissions down to individual fields; content can be staged in workspaces and published on a schedule. If your requirement list includes "the Munich office edits their pages but cannot touch the header" and "the Polish site falls back to English for untranslated pages", TYPO3 answers it out of the box, where WordPress answers it with 3 plugins and some hope.

Expect a developer project, not an install wizard

Installation is Composer-based: composer create-project typo3/cms-base-distribution pulls the core and a starter site package, then the install tool sets up the database (MySQL or MariaDB are the usual choices; PostgreSQL works). After that comes the part no wizard covers. Templates are Fluid, configuration is TypoScript, content element definitions live in PHP arrays called the TCA, and a site package extension is the expected place to hold all of it. There is no theme marketplace where you click "activate". Reckon on a developer week to get a site package to a state you would show a client, longer if you are learning the stack from zero. The "Hard" difficulty in the listing is accurate, not conservative.

Hosting requirements are enterprise-shaped

Run it on PHP 8 with opcache, a real database server, and enough RAM for the backend, which is a heavy single-page application: 1 GB is the floor for a small instance, and busy editorial teams sit closer to 4 GB once image processing (ImageMagick or GraphicsMagick) and the caching framework are working. Put a page cache in front for anonymous traffic; TYPO3's own caching is capable, but Redis or a Varnish layer is normal in production. Docker works, but there is no single official image the way WordPress has one; teams build their own from the php-fpm base or use community images, which is fine for a team and a burden for a hobbyist.

The LTS cycle is the quiet selling point

TYPO3 ships a long-term support release roughly every 18 months, each supported with free updates for 3 years and a paid extended support programme after that. Upgrades between LTS versions are documented and tooled, with an upgrade wizard in the install tool that handles most database migrations. For an organisation, that means a predictable line in the budget rather than the patch-whenever cadence of most open-source CMSs. For a solo operator, it means one major upgrade project every year and a half, with extension compatibility to check each time.

How it compares

Drupal is the closest rival: similar audience, similar learning curve, larger English-speaking community and more third-party modules. Picking between them usually comes down to which one your agency knows. WordPress is the safer pick when the requirement is "a good website" rather than "a governed publishing platform", and the CMS category is where I would send anyone who has not already been told they need TYPO3 by a procurement document. It is a genuine open-source answer to Adobe Experience Manager and Sitecore, and that is the shelf it belongs on.

What I'd do

If you are an agency or an in-house web team with PHP skills and a multisite, multilingual brief: run it, on a VM with 4 GB of RAM, Composer-managed, on the current LTS, with the site package in git and separate staging and production environments from day one. If you are one person with one site, do not: WordPress or a static generator will get you there in an afternoon, and the TYPO3 backend will sit there reminding you it was built for a bigger organisation than yours.