Actively maintained
The version receives regular bug and security fixes, for everyone and at no extra cost. Normal operation.
Lifecycle
TYPO3 Versions and Support Periods
How long a TYPO3 version keeps receiving security fixes decides when an update falls due. The dates come from the official source unchanged; the status is recalculated at every site build.
Once active maintenance ends, security fixes only reach paying ELTS customers. When that period runs out too, holes that have become known stay open. What the individual terms mean is set out in the glossary under LTS. What the latest major version brings and who the jump is worth it for is summarised in the guide on TYPO3 14.
Remaining support time
Actively maintained ELTS only (paid) As of the site build, data from get.typo3.org
| Version | LTS release | PHP | Actively maintained until | ELTS until | Status |
|---|---|---|---|---|---|
| TYPO3 14 | 14.3 | PHP 8.2–8.5 | 30 June 2029 | 30 June 2032 | Actively maintained |
| TYPO3 13 | 13.4 | PHP 8.2–8.5 | 31 December 2027 | 31 December 2030 | Actively maintained |
| TYPO3 12 | 12.4 | PHP 8.1–8.4 | 30 April 2026 | 30 April 2030 | ELTS only |
| TYPO3 11 | 11.5 | PHP 7.4–8.3 | 31 October 2024 | 31 October 2028 | ELTS only |
| TYPO3 10 | 10.4 | PHP 7.2–7.4 | 30 April 2023 | 30 April 2027 | ELTS only |
| TYPO3 9 | 9.5 | PHP 7.2–7.4 | 30 September 2021 | 30 September 2025 | Support ended |
| TYPO3 8 | 8.7 | PHP 7.0–7.4 | 31 March 2020 | 31 March 2024 | Support ended |
ELTS only
Regular maintenance has ended. Security fixes still appear, but only through the paid Extended Long Term Support. Meant as a bridge, not as a permanent arrangement.
Support ended
No more fixes are published. Every newly discovered hole stays open in the installation. At this point an update is no longer a question of priorities.
Common questions
Where does this data come from?
Straight from the official API at get.typo3.org. We take it over unchanged and give the retrieval date in the table caption.
One field available there we deliberately left out: the release date. Its meaning is not consistent across versions. A column that shows one date here and another there would be worse than no column at all.
Which version should we pick for a new project?
As a rule the most recent LTS version. It has the longest remaining support and therefore the largest gap before the next mandatory update.
An exception can arise when an indispensable extension does not support the newest version yet. That is then a deliberate decision with a known price, not a side note. What TYPO3 14 added is covered in the guide.
How long does the jump to the current version take?
That depends less on the number of versions skipped than on your own code and the set of extensions in use. A well-kept installation with a few current extensions is manageable; one that has grown with many adaptations is a project.
A dependable answer is only possible after an inventory. What gets checked is described under TYPO3 update.
Running a version that is out of support?
We will tell you whether an update is enough or a relaunch is the more honest route, and what either one involves.