Study guide · TYPO3, Community and Project
Getting to know TYPO3: the project, versions and where to find help
Before Mara writes her first line of TypoScript, she has to answer some basic questions. What is TYPO3, who is behind it, which version should you pick, and is the server good enough? This page follows her through exactly these questions. Afterwards you know the license, the organizations, the versions, the system requirements and the main places to get help.
The Lindenau music school project
Mara is an integrator. She is building the new website of the Lindenau music school. She works in a Composer project with TYPO3 14.3. She puts the look and the configuration of the website into her own sitepackage with the extension key lindenau_site. As a Composer package it is called lindenau/site.
In the first meeting, the school's management asks four questions:
- Does TYPO3 cost license fees?
- Who keeps developing TYPO3, and will the system still exist in a few years?
- Which version should we use, and how long will it be maintained?
- Will TYPO3 run on our current server?
Mara answers them one by one. After that she needs help herself, extensions, and a basic understanding of MVC and template engines.
What TYPO3 is
TYPO3 is an open source enterprise content management system. It ships with many features out of the box and can be extended with extensions. “Enterprise” means large and multilingual websites, many editors, fine-grained permissions and several websites in one installation. TYPO3 is not a website builder with a subscription, not a JavaScript framework and not a database system.
The license is the GNU General Public License, GPL for short, version 2 or later. It lets everyone read, copy, distribute and modify the source code. There are no license fees. So the management's first question is answered quickly: costs come from implementation, hosting and maintenance, not from the software.
Mara needs two terms all the time. The backend is the protected administration interface where editors and administrators work. By default you reach it under the path typo3 after the domain. The frontend is the public website. The page tree is only one part of the backend. The Install Tool is a separate area for system administration.
The official documentation lives at docs.typo3.org. For every version you find TYPO3 Explained, the TypoScript Reference, the ViewHelper Reference, the Getting Started tutorial and the documentation of the system extensions, among others.
What the server needs
The music school runs its own server so far. Mara checks whether it is good enough. TYPO3 is written in PHP. So it needs a web server with a supported PHP version and certain PHP extensions. You can use Node.js in a project for the frontend build, but TYPO3 itself does not need it.
The exact version numbers are listed on get.typo3.org. The documentation explicitly points there. For TYPO3 14:
- PHP: version 8.2 to 8.5. PHP 8.1 is no longer enough.
- Database: MySQL from 8.0.17, MariaDB from 10.4.3, PostgreSQL from 10 or SQLite from 3.8.3. MongoDB or Microsoft Access are not supported.
- Composer: from version 2.1, if you install TYPO3 with Composer. There is no Composer version 3.
- Web server: Apache, NGINX, Microsoft IIS or Caddy.
With MySQL and MariaDB, the storage engine InnoDB must be available. It supports transactions and is the default anyway.
Each database needs its own PHP extension. For MySQL and MariaDB that is pdo_mysql, which is recommended, or mysqli. For PostgreSQL you need pdo_pgsql and pgsql. For SQLite you need sqlite3.
On top of that, TYPO3 strictly requires a set of PHP extensions, including intl, mbstring and sodium, as well as pdo, session, xml, dom and tokenizer. Without them, Composer refuses to install TYPO3. The Install Tool is even stricter: it also reports missing extensions such as filter, gd, zip and zlib as errors. The xdebug extension, by contrast, is a debugging tool. For image processing TYPO3 does not use the PHP extension imagick. It calls GraphicsMagick or ImageMagick on the command line. GraphicsMagick is recommended. You need one of them for automatic image processing, but not for the installation.
For the php.ini, the documentation lists these values: memory_limit 256M, max_execution_time 240 and max_input_vars 1500. If max_input_vars is too small, fields get lost when large backend forms are saved. The Install Tool checks these values. For memory it treats 256 megabytes as the lower limit and recommends 512.
Setting up the database and web server
The TYPO3 database user needs more than read and write privileges. These are required:
- SELECT, INSERT, UPDATE and DELETE for reading and writing.
- CREATE, DROP, INDEX and ALTER for changes to the database schema.
- CREATE TEMPORARY TABLES and LOCK TABLES.
Without the schema privileges, the database analysis and schema changes fail. This happens after an update or with a new extension, for example. TYPO3 does not need administrative privileges like SUPER, SHUTDOWN or GRANT OPTION. For security reasons they should be missing.
For the SQL mode, TYPO3 expects the default settings of the supported databases. The strict modes STRICT_ALL_TABLES, STRICT_TRANS_TABLES and ONLY_FULL_GROUP_BY are explicitly tested and supported. So you do not have to switch them off.
For Apache, TYPO3 ships a file called .htaccess with rewrite rules and access protection. NGINX is supported too, but it does not read .htaccess files. There, these rules belong in the server configuration. For IIS, TYPO3 ships its own file called web.config.
History and products
The management's second question is: who is behind TYPO3? Mara goes back a bit.
The Dane Kasper Skårhøj started developing TYPO3 in 1997, as an individual and not as a corporation. The project grew into a large community. When Kasper stepped back in 2004, the TYPO3 Association was created. It took over leadership of the project on behalf of the community. The Association later founded the TYPO3 GmbH as its company for commercial services.
Besides the CMS, the TYPO3 project produced further products:
- TYPO3 Surf is a tool for automated deployment. It rolls out applications to servers from the command line. It has nothing to do with search or image editing.
- Fluid is the template engine that TYPO3 uses today to render templates in the frontend and the backend.
- Neos also started in the TYPO3 project and is independent today.
WordPress, Drupal or Magento, by contrast, are independent projects. PHP itself was created by Rasmus Lerdorf, Drupal by Dries Buytaert and WordPress by Matt Mullenweg.
License and trademark
The GPL allows a lot, but it sets one condition. If you pass a derived work on to others, you must license it under the GPL again and include the source code or make it available. Extensions build on the GPL code of TYPO3, so they are also covered by the GPL. You need no approval from the Association for changes, and there is no fee.
The TYPO3 trademark, on the other hand, is protected. It belongs to the TYPO3 Association, not to the GmbH and not to the inventor. The Association also provides the style guide. Name, logo and fonts are governed by its trademark usage policy. The GPL covers the code, not the trademark. Agencies and the community may use the logo, but only within this policy.
The Association and the community
With that, Mara has nearly answered the question about the future. Three levels stand behind TYPO3: the Association, its subsidiary the GmbH, and the community.
The TYPO3 Association is based in Switzerland. Its main task is to fund the development of TYPO3 and to support the community. It provides infrastructure and guidance and promotes TYPO3 worldwide. It does not sell licenses, and it neither builds websites nor offers hosting.
Its money comes from membership fees, donations and events. Around 650,000 euros a year go into Core development and community projects. There are no license fees, no advertising in the backend and no charges on downloads.
The membership levels are called Community, Bronze, Silver, Gold and Platinum. On top of that there are memberships for sectors, such as Academic for universities, NGO for non-profit organizations and Public Sector for public administration. Levels like Diamond or Premium Plus do not exist. Members get discounts on events and on services of the GmbH, for example. A membership supports the project, but it does not promise any support.
Together with the TYPO3 GmbH, the Association runs the big events: the TYPO3 Developer Days for professionals and T3CON for clients, freelancers and agencies.
The community includes everyone who uses or develops TYPO3. That ranges from editors through integrators and developers to agencies. You need neither a membership nor a certificate. Locally, the community itself organizes TYPO3Camps and the meetings of regional user groups.
The work is spread across teams and committees. For example, there are the Documentation Team, the Marketing Team, the Security Team, the Strategic Initiatives and teams for server and education. There is no team for pricing or legal enforcement. Everyone is invited to take part, with code, documentation, translations or in a team. Contributions to the Core go through the open review system, not through the GmbH.
The TYPO3 Code of Conduct applies to working together. It describes respectful, open interaction without harassment, at events as well as in chat. For code formatting, by contrast, there are the coding guidelines.
Versions and support
The third question: which version, and for how long? TYPO3 uses Semantic Versioning. A number like 14.3.7 consists of the major version, the minor version and the patch level.
- A higher patch number, for example from 14.3.6 to 14.3.7, brings bug fixes without breaking anything. Database and backend usually stay the same. Most of the time the new source code is all you need.
- A new minor version brings new features.
- A new major version may contain breaking changes. When moving from 14.3 to 15.0, system requirements like the PHP version can change. Database, backend and rendering can change too, and templates or TypoScript may need adjustments.
Every major branch starts with sprint releases. For TYPO3 14 these were 14.0, 14.1 and 14.2. They bring new features. But their support ends with the next sprint release. Only the last version of the branch is the LTS version. LTS stands for Long Term Support. TYPO3 14 LTS is internally 14.3, just as 13 LTS was internally 13.4. The official name leaves out the minor version. An LTS version gets bug fixes and security updates for at least three years.
According to get.typo3.org, TYPO3 14 was released on 21 April 2026. It is regularly maintained until 30 June 2029. With ELTS, support lasts until 30 June 2032. Such dates can change. So check the roadmap before you promise anything to a client.
Free security updates are available for the current and the previous LTS. In autumn 2026 these are TYPO3 14 and TYPO3 13. Regular support for TYPO3 12 ended on 30 April 2026.
After regular support ends, the TYPO3 GmbH offers Extended Long Term Support, ELTS for short. For a fee, it brings up to three more years of security and compatibility updates. The GmbH also sells service level agreements, SLAs for short. Only an SLA guarantees binding response times. Slack and mailing lists are community channels without any commitments.
Documentation and help
Mara gets stuck on a setting. Where can she find help?
- docs.typo3.org holds the manuals, each per version.
- In the TYPO3 Slack at typo3.slack.com the community talks to each other. There are channels on topics like TYPO3 CMS, extensions or documentation. Slack is the official meeting place of the community.
- The Core changelog lists all changes to the Core, sorted by the version in which they came.
The changelog has four kinds of entries: Breaking, Feature, Deprecation and Important. Breaking describes features that were removed or changed in an incompatible way. Feature describes something new. Deprecation announces what will go away later. Important holds significant notes that do not break anything.
If Mara finds a mistake in the documentation, she does not wait for the next LTS. The documentation lives in public repositories. Using the link “Edit on GitHub”, she suggests a correction. The Documentation Team reviews the suggestion.
Finding and checking extensions
The music school needs a feature that the Core does not provide. Almost all public TYPO3 extensions are listed in the TYPO3 Extension Repository, TER for short, at extensions.typo3.org. There you can search for extensions and download them. For each extension, the TER shows, among other things:
- The versions and the supported TYPO3 versions.
- Links to the documentation and to the code repository.
- The Composer package name, if there is one.
Because Mara works with Composer, she does not install extensions from the TER. By default Composer fetches packages from Packagist, and most TYPO3 extensions are published there too. She finds the matching package name on the extension's page in the TER.
Unlike the Core, nobody reviews the code of every extension. Most known security vulnerabilities affected extensions, not the Core. So before using an extension, Mara checks whether it is maintained, whether it fits TYPO3 14 and whether there are security advisories about it.
MVC and template engines
Finally, two concepts that Mara meets everywhere in TYPO3.
MVC stands for Model View Controller. This design pattern splits an application into three parts. The model holds the data. The view presents it. The controller decides what happens on a user action. In TYPO3, Extbase follows this pattern:
- The model consists of domain objects from the database, such as a course at the music school.
- The controller handles requests in action methods and passes data to the view.
- The view renders the data with a Fluid template.
A template engine combines two things: a template with placeholders and the data. From these, the engine produces the output, usually HTML. In TYPO3, Fluid is that engine.
A template engine has three advantages:
- Presentation and program logic are separate. Whoever changes the template does not have to touch the logic.
- The same data can be output with different templates, for example as a list and as a detail page.
- Fluid escapes variables automatically. This protects against cross-site scripting, XSS for short.
PHP code inside the template is precisely what is not intended. And the data still comes from the database, the template engine does not replace it.
Key points
- TYPO3 is an open source enterprise CMS written in PHP under the GPL, version 2 or later. There are no license fees.
- The system requirements with version numbers are on get.typo3.org. TYPO3 14 needs PHP 8.2 to 8.5, Composer from 2.1 and MySQL, MariaDB, PostgreSQL or SQLite.
- MySQL and MariaDB need InnoDB. Required extensions include intl, mbstring and sodium. The recommended max_input_vars is 1500.
- Besides read and write privileges, the database user needs CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES and LOCK TABLES.
- NGINX does not read .htaccess. The rules belong in the server configuration.
- Kasper Skårhøj started in 1997. The Association was founded in 2004, is based in Switzerland and holds the trademark. It founded the TYPO3 GmbH.
- If you pass on GPL code, you must include the source code. The Association's trademark policy governs name and logo.
- The community includes everyone. It organizes TYPO3Camps and user groups and works in teams under the Code of Conduct.
- Sprint releases are only maintained until the next one. 14 LTS is internally 14.3 and is regularly maintained until 30 June 2029, with ELTS until 30 June 2032.
- ELTS and SLAs come from the TYPO3 GmbH.
- The changelog distinguishes Breaking, Feature, Deprecation and Important.
- Extensions are in the TER and, for Composer, on Packagist. Check them before you use them.
- A template engine combines template and data. In TYPO3 that is Fluid.
Terms
- CMS
- Software that lets several people create and maintain content together.
- Backend
- Protected administration interface of TYPO3 for editors and administrators.
- Frontend
- The public website.
- GPL
- GNU General Public License, the free license of TYPO3.
- TYPO3 Association
- Association based in Switzerland that carries the project and owns the trademark.
- TYPO3 GmbH
- Company founded by the Association that offers ELTS and SLAs, among other services.
- Semantic Versioning
- Version scheme made of major version, minor version and patch level.
- Sprint release
- Early version of a major branch that is only maintained until the next sprint release.
- LTS
- Long Term Support, the last version of a major branch with at least three years of maintenance.
- ELTS
- Extended Long Term Support, a paid extension after regular support ends.
- SLA
- Service level agreement, a contract with guaranteed response times.
- TER
- TYPO3 Extension Repository at extensions.typo3.org.
- Packagist
- Directory of Composer packages that Composer installs from by default.
- MVC
- Design pattern that splits an application into model, view and controller.
- Template engine
- Software that creates output from a template and data, in TYPO3 that is Fluid.