Skip to main navigation Skip to main content Skip to page footer
TYPO3 v14: Three strategic innovations for integrators

TYPO3 v14: Three strategic innovations for integrators

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.

While many are still learning v13, it's worth taking a look at v14. Three features show where the journey is heading - and what you should bear in mind when planning your next project.

While some integrators are only just familiarizing themselves with TYPO3 v13 LTS, it's worth taking a look at version 14 now - not because you have to migrate tomorrow, but because it's becoming clear where the journey is heading. And if you understand what's coming early on, you can plan better.

I took a look at the change log for the current development version and picked out three new features that I think are strategically relevant. Not the most spectacular features, but those with an impact on day-to-day work.

1st integration module: Central administration at last

TYPO3 is getting a new module under "System": Integrations. This sounds unspectacular at first, but it is an important step. Until now, webhooks and reactions were scattered across various modules. Now there is a central hub.

The module uses a three-level hierarchy:

  • System (main module)
  • Integrations (overview with card layout)
  • Webhooks / Reactions (as sub-modules)

The interesting thing is that the module is designed from the outset as an expandable hub. Translation services, AI platforms, external tools - everything should be able to dock here. TYPO3 is preparing for external integrations to become more important.

What this means: The old module structure will continue to work via aliases, but anyone planning new integrations should be familiar with the new concept. The backend will become clearer, especially for projects with many interfaces.

2. image formats: Finally configurable instead of hard-coded

Until now, the standard output format for processed images in TYPO3 was hardcoded - usually PNG. Use WebP or AVIF? Only possible with code changes.

This changes with the new configuration option $GLOBALS['TYPO3_CONF_VARS']['GFX']['imageFileConversionFormats']. You can use this to specify

  • Which format is used as default
  • Which output format should be used for each input format
  • Whether modern formats such as WebP or AVIF become the new standard

By default, TYPO3 retains the original format (JPG remains JPG, PNG remains PNG), everything else is converted to PNG. However, you can, for example, set all images to be output as AVIF by default - without touching a single line of Fluid code.

What this means: TYPO3 becomes more future-proof. If a new image format comes along and your graphics engine (ImageMagick or GraphicsMagick) supports it, you can activate it via configuration. No extension necessary, no code intervention.

3 HeaderData and FooterData ViewHelpers: Flexibility for edge cases

The new Fluid ViewHelpers <f:page.headerData> and <f:page.footerData> fill a gap. Until now, you had <f:asset.css> and <f:asset.script> - but what if you want to integrate dns-prefetch, preconnect or tracking scripts?

The new ViewHelpers give you direct access to <head> and the area before </body>. You can inject any HTML code that is then output via the PageRenderer API.

What this means: More control for special requirements. But be careful: The ViewHelpers do not escape automatically. If you process user input, you have to pay attention to XSS security yourself.

What the overall picture shows

These three features are just a tiny excerpt from the ChangeLog. But they show a direction:

  • TYPO3 is preparing for more external integrations
  • Modern web standards can be used without code changes
  • Flexibility is being expanded without sacrificing simplicity

Version 14 is still in development. But anyone planning projects that will go live in 2026 should have these developments on their radar.

How to stay tuned

The ChangeLog is extensive, and not every innovation is relevant for every integrator. I will continue to filter and present the strategically interesting features here in the blog.

If you don't want to miss such updates, it's worth taking a look at my TYPO3 newsletter. There you will get the most important developments in a compact format - without any noise, only what is really relevant.

And if you want to learn TYPO3 14 from scratch: I'm working on the TYPO3 Complete Course, which is updated with every new version. Integration module, modern image formats, new ViewHelper and everything else that v14 brings. Join the waiting list to secure the discounted introductory price.


Sources & Links

Feature #107795 - Introduce Integrations module

Feature #93981 - Specify default image conversion processing

Feature #107056 - Introduce headerData and footerData ViewHelpers

Back

Comments under articles are disabled. If you have a question or addition, please send me an e-mail.

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.

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