Skip to main navigation Skip to main content Skip to page footer
Wolfgang Wagner - TYPO3 Seminare, Workshops, Tutorials, Support
TYPO3 v14.0 is here: Fresh UI, Fluid 5 and the starting signal for the most modern TYPO3 era

TYPO3 v14.0 is here: Fresh UI, Fluid 5 and the starting signal for the most modern TYPO3 era

Have the article read aloud.

Loading the Elevenlabs Text to Speech AudioNative Player...
| TYPO3 | Estimated reading time : min.
This article was automatically translated using DeepL. Therefore, inaccuracies may occur.

TYPO3 v14.0 is here and brings a breath of fresh air to the CMS. Backend UI modernization, Fluid 5 with new ViewHelpers and a modern translation workflow make you want to use the new version.

TYPO3 v14.0 was released yesterday at T3CON25 in Düsseldorf. The first sprint release of the v14 series brings over 2,000 changes and marks the start of a new era for the open source CMS. Find out what's changing, why it's important and what extension compatibility looks like here.

Backend modernization: More than just new names

The TYPO3 backend is getting a makeover. Modules have been renamed and restructured to make it easier for new users to navigate:

  • Web → Content
  • Files → Media
  • Admin Tools → Administration

The DocHeader has been completely redesigned and now features interactive breadcrumb navigation and a standardized language selector for all modules with multi-language support. The second line is reserved for action dropdowns and buttons such as Save, Close, Reload and Bookmark.

Benni Mack presented the new version at T3CON25 and gave a preview of the planned backend UI changes. It looked great and will almost certainly ensure that TYPO3 loses its reputation as an "old-fashioned system". I'm looking forward to the new version and I'm sure that we can once again talk about the "best TYPO3 ever" with full justification.

Fluid 5: The next generation

The Fluid template system has been updated to version 5. The most important new features:

Flexible file names

File names no longer have to start with a capital letter. Fluid now uses a fallback chain that first searches for the standard spelling and then falls back to capitalization. This paves the way for future Fluid file extensions such as .fluid.html or.fluid.txt.

CDATA support

Inline CSS or JavaScript in Fluid templates now work without curly bracket conflicts. Content in CDATA sections is ignored by the parser, while variables and ViewHelpers with triple curly braces {{{ }}} continue to work.

New ViewHelpers

  • PageTitle: Set page title directly in Fluid, without custom page title provider
  • PageMeta: Set meta tags via the MetaTagManager API
  • PageHeader and PageFooter: Insert custom content in <head> or before </body
  • Date: New "timezone" option for localized date and time display

Who wants to learn TYPO3 v14 from scratch: I'm working on the TYPO3 Complete Course, which is updated with every new version. Fluid 5, site sets, the new backend and everything that goes with it. Join the waiting list to secure the discounted introductory price.

Translation workflow: Guided instead of guesswork

The translation workflow has been modernized. A step-by-step wizard guides you through the entire process, automatically skipping unnecessary steps and ensuring a consistent experience in all backend modules.

The language selection in the backend has been simplified: select multiple languages at the same time, show or hide individual languages, activate or deactivate all at once. The selection is retained across the Page and List modules.

In the background, the localization architecture has been migrated to the Symfony Translation Component. TYPO3 now supports XLIFF 1.2 and XLIFF 2.x as well as custom translation loaders according to the Symfony standard. The new domain syntax makes references more logical:

  • OLD: "LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:general"
  • NEW: "core.form.tabs:general"

Backward compatibility is retained, so TCA files do not need to be updated immediately.

Under the hood: Housekeeping and new APIs

Deprecated code removed

As with every first release of a new cycle, a thorough clean-up has been carried out. PHP classes, functions, CLI calls and other legacy components have been removed. The changelog "Deprecated functionality removed" lists all changes with migration notes.

System Resource API

Resources are now resolved centrally via a new System Resource API. This includes package resources (files in extensions), FAL assets, app resources (files in the TYPO3 project folder) and URI resources. Keywords such as "PKG" or "FAL" work consistently in PHP, TypoScript and Fluid. The legacy keyword "EXT" will be retained for the time being.

Extbase: PHP Attributes and Symfony Validators

Extbase no longer uses doctrine/annotations (upstream maintenance discontinued). Since PHP 8.2 is mandatory, developers should migrate to PHP Attributes. TYPO3 supports attributes for all Extbase annotations since version 12.

Extbase Models and Controllers now support Symfony Validators. Together with the existing Extbase validators and the new PHP Attributes, input validation becomes much easier. Custom validators are less necessary.

Hosting and DevOps: More flexibility

  • Install Tool sessions can now be stored in Redis or with custom storage path for file sessions
  • Redis cache backend supports username + password authentication (Redis 6+)
  • Install Tool Password Hash can be generated via CLI (interactive or unattended)
  • HTTP response compression has been removed from TYPO3 core (servers do it more efficiently)
  • Install Tool is now fully integrated into the backend routing, "typo3/install.php" no longer necessary
  • Standard .htaccess template for Apache has been adapted to modern Composer installations

System requirements and support

TYPO3 v14 requires at least PHP 8.2 (security updates until 31.12.2026) and supports PHP 8.3, 8.4 and even 8.5. Since TYPO3 v12, v13 and v14 have similar system requirements, the platform can be updated before the TYPO3 instance.

The sprint releases v14.0 to v14.2 are supported until the next minor version. TYPO3 v14 LTS (version 14.3) will receive bug fixes until 31.12.2027 and security patches until 30.06.2029.

Extension compatibility: quick start

16 extensions are already available in the TER as v14-compatible (as of 26.11.2025, 7 a.m.). These include well-known and popular ones such as:

  • news (Georg Ringer)
  • content_blocks (Nikita Hovratov)
  • tt_address (Georg Ringer)
  • schema (Chris Müller)
  • warming (Elias Häußler)

I'm sure there will be more soon. If you want to use TYPO3 v14 productively, you should check the extension compatibility of your own setup components.

What's coming next?

TYPO3 v14.1 is planned for January 20, 2026. The backend modernization will then continue, new API endpoints will be added and a default theme based on site sets is planned.

For all those who want to get started with TYPO3 v14 in a structured and practical way: The TYPO3 complete course is continuously updated and grows with each new version. Sign up for the waiting list to be the first to be informed and to secure the introductory price.

Test now

You can find the download and all details about the release at get.typo3.org. The official press release with technical deep-dives can be found at news.typo3.com.

Have you already tested TYPO3 v14? What are your first impressions? Let us know in the comments.

Back

Do you have a question or want to discuss the topic?

In the Community Hub for TYPO3 you can exchange ideas with other TYPO3 users. And if you don't want to miss any new articles: The TYPO3 Newsletter comes once a month, without spam.

[Translate to English:] Wolfgang Wagner, TYPO3 Experte und Trainer

Hi, I'm Wolfgang.

I have been working with TYPO3 since 2006. Not in theory, but in real projects with real deadlines. I've probably had the problems you're having three times already.

At some point, I started putting my knowledge into video courses. Not because I like being in front of the camera, but because I kept hearing the same questions over and over again. There are now hundreds of videos. Every single one was the result of a specific question from a specific project.

What makes me different from a YouTube tutorial: I not only know the solution, but also the context. Why something works. When it doesn't work. And which mistakes you can avoid because I've already made them.

My participants use me as a sparring partner. Not in the sense of "call me anytime", but like this: You come to the live session with a specific problem, post your question in the community or watch the appropriate video. And get an answer that works because it comes from practical experience.

As a member of the TYPO3 Education & Certification Committee, I make sure that the certification exams are kept up to date. What is tested there flows directly into my courses.