165 revolutionary new features *
TYPO3 v13 not only brings numerous new functions, but also far-reaching improvements for Backend users, developers and administrators. The most important new features for the areas Backend (BE), System (SYS), Development (DEV), Project Management (PM) and Search Engine Optimization (SEO) are presented here.
* marked as FEATURE in the release notes
TYPO3 v13 benefits - PM
TYPO3 13 also serves as the basis for GSB 11 (Government Site Builder), a solution developed specifically for the requirements of public institutions. By using TYPO3 as the basis, users benefit from the flexibility and scalability of the system, while at the same time the specific needs of government websites are taken into account.
GSB 11 enables public authorities to quickly and efficiently create customizable websites that comply with current standards. This integration strengthens the position of TYPO3 in the public sector and shows how powerful CMS is for creating professional and user-friendly websites. Another step towards a modern digital administration!
TYPO3 now supports Irish Gaelic, Scottish Gaelic and Maltese. Irish Gaelic is spoken in Ireland, Scottish Gaelic in Scotland and Maltese in Malta.
It is now possible to automatically retrieve translated labels from translations.typo3.org and CrowdIn in TYPO3-Backend. The user interface of Backendcan be switched to these languages. Developers can add new languages in the site configuration and create translation files with the prefix (e.g. `*.locallang.xlf`) to define their own labels.
This extension of language support improves accessibility and promotes the versatility of TYPO3 for a wider audience.
In TYPO3 13, support for SEO is optimized through various improvements. These include the improved handling of SVG crops, which provides high-quality graphics in various sizes without affecting loading times.
In addition, the site sets now offer an integrated SEO sitemap function that makes it easier to structure and optimize website content for search engines. Meta tag management has also been enhanced to provide more precise control over SEO-relevant information.
These advances make TYPO3 a powerful tool for companies looking to maximize their search engine visibility and provide a first-class user experience.
- SVG / WebP see DEV: "Improved image processing in TYPO3: WebP and SVG support"
- See also: DEV & SYS
TYPO3 13 offers extended LTS (Long Term Support) and ELTS (Extended Long Term Support) to guarantee users even more stability and security. With the extended LTS, users can benefit from longer support periods that include regular updates and security patches.
Updates until 30.04.2026 | security updates until 31.12.2027 | optional until 31.12.2030 (possibly 2031)
The ELTS service is aimed at companies that require additional support to secure and adapt their TYPO3 installations in the long term. This support enables organizations to work securely even in critical environments while benefiting from the latest developments. With these offers, TYPO3 becomes an even more reliable choice for long-term projects and demanding applications!
TYPO3 v13 benefits - BE
The new redirect check tools enable administrators to monitor redirects efficiently. This function helps to identify potential problems at an early stage and ensure the integrity of the website. This avoids dead links and incorrect redirects, which not only improves the user experience but also has a positive impact on SEO rankings.
The ability to define individual entry points for the Backend provides administrators with more security. Instead of using the standard access via `/typo3`, user-defined URLs or domain names can be configured. This reduces the risk of attacks on the administrator interface and enables a more individual configuration.
With the introduction of the module `@typo3/backend/hotkeys.js` in TYPO3, developers can now register custom hotkeys in TYPO3 Backend . To avoid conflicts with other hotkeys, possibly from other extensions, it is recommended to register hotkeys in a special scope.
The module provides an enum with common modifier keys (Ctrl, Meta, Alt and Shift) as well as a public property describing the common hotkey modifier based on the user's operating system: Cmd (Meta) for macOS and Ctrl for other systems. The use of modifiers is optional, but highly recommended.
A practical new feature is that scheduler tasks can now also be saved using a key combination. The hotkeys Ctrl/Cmd + S can be used to save a scheduler task, while Ctrl/Cmd + Shift + S is used to save and close the task.
"Save and close" has also been implemented in the FormEngine area via Ctrl/Cmd + Shift + S.
These new functions significantly improve user-friendliness and efficiency in TYPO3 Backend and make day-to-day work easier for editors and developers.
In large installations, finding specific forms can be a challenge. TYPO3 13 therefore introduces a new search function in the Form Manager that allows users to search for specific forms. A search field enables a case-independent search by name or `persistenceIdentifier`.
This function makes administration much easier and is particularly useful for editors who regularly have to work with a large number of forms. With this improvement, editors can quickly and efficiently find and edit the desired forms.
The page tree in TYPO3 has been improved to allow users to search not only for individual page IDs, but also for comma-separated lists of page IDs. This enhancement makes it easier to filter and find multiple pages at once and improves the usability of TYPO3 Backend s.
TYPO3 has introduced dashboard widgets for each type of internal note (EXT:sys_note) to make it easier for users to view all the notes in their system. These notes can be private or shared and are particularly useful for teams. Users can record thoughts and notes directly in the system, improving collaboration.
In order to use the widgets, the Backend user must have access to the `sys_note` table and authorization to view the page on which the record is located. Notes can be linked to specific pages or content, which facilitates contextualization. This function not only promotes communication within the team, but also enables new members to familiarize themselves with projects more quickly.
This new feature improves clarity in TYPO3 Backend and optimizes teamwork.
The Backend-Pagetree component of TYPO3 has been updated to add labels and status information to Pagetree, greatly improving functionality and usability.
Prior to the introduction of labels, developers and integrators had to rely on `pageTree.backgroundColor.<pageid>` to provide visual cues, which is considered deprecated in TYPO3 v13. However, these background colors were not accessible and did not provide meaningful context, excluding users with limited vision or those who rely on screen readers.
The new labels will improve accessibility for all editors. These labels enable customizable color markers for Pagetree and require an associated label to improve accessibility. Each node can support multiple labels sorted by priority, with the highest priority label taking precedence. Users can assign a label via the TSconfig user, although only one label can be set in this way.
In addition, status information has been added to the page tree. These details show the status of the nodes and provide additional information. For example, if a page in a workspace undergoes changes, this is now indicated by an indicator in the corresponding page tree. The status is also displayed in the title of the node, which increases the visual clarity and accessibility of the information.
Each node can hold multiple status information, prioritized by severity and urgency. Critical messages have priority over other status notifications. These innovations help to significantly improve the user experience at TYPO3 Backend .
The Pagetree function in TYPO3, a central element for the visual representation of page structures, is receiving a comprehensive update. With the new Modern Reactive Tree, which is based on modern web standards, we are saying goodbye to the limitations of the previous SVG tree.
The update brings a consistent user experience in which all functions are seamlessly integrated. The new solution dynamically adapts to user preferences and supports both dark mode and right-to-left (RTL) writing. Native drag-and-drop makes interaction more intuitive, and the improved virtual scroll function ensures that only the currently visible nodes are rendered.
Another plus point is the storage of the tree status in the browser's local memory, which makes it easier to switch between devices. With these innovations, TYPO3 is ready for a user-friendly future and offers exciting prospects for future features.
With TYPO3 version 13, editing metadata for multiple files and pages is considerably simplified. Previously, it was necessary to edit each page individually to access its specific properties. Now, the new bulk edit columns feature allows users to select multiple pages at once and view the specific information they want.
The user interface features a new "Edit Columns" button that retains the functionality of the previous "Edit" button, but only displays the currently active columns. This means, for example, that several pages can be edited at once without being distracted by irrelevant fields. This significantly improves editing efficiency.
This function is not only available in the page module, but also in the file module "Filelist". There, users can adjust specific metadata of files directly. These new features make working with TYPO3 more intuitive and targeted by focusing on the essentials while increasing user-friendliness.
With the latest TYPO3 version, the clarity of the formBackend module has been significantly improved. The list of existing forms can now be sorted, making it easier for users to quickly find and manage their forms. This new feature allows for more efficient navigation and organization, so you can arrange your forms according to your needs. A simple but effective update that further optimizes the user experience at TYPO3 Backend
In the current TYPO3 version, the user-friendliness of content management has been significantly improved. Backend-Users can now drag and drop Inhaltselements in the Web > Page module into the page tree.
After dropping, a modal window opens in which the user can select the desired position for the Inhaltselement and change the target page if necessary. This function makes it easier to manage content across multiple pages and ensures a more efficient way of working in the TYPO3 Backend .
In the latest TYPO3 version, the management of authorizations for Backend user groups has been significantly improved. The tables_select (read) and tables_modify (write) fields of the be_groups table have been combined into a single, user-friendly UI element. This makes it easier for integrators to manage access rights to database tables.
The new UI provides separate radio buttons that can be used to define whether a user group has "No Access", "Read" or "Read & Write" permissions. In addition, options such as "Check All", "Uncheck All" and "Toggle Selection" have been introduced to further optimize operation.
Behind the scenes, permissions are still stored separately in the tables_select and tables_modify columns of the be_groups table. A new render type, tablePermission, has been introduced to display this new view and control its behavior. The associated JavaScript code is provided by a new web component.
These changes make it easier to manage table permissions for Backend user groups and improve the overall user experience. However, integrators should ensure that their existing customizations to the tables_select and tables_modify fields continue to work and are adjusted if necessary.
TYPO3 v13 benefits - SYS
Especially with the fetch logic of the Common Table Expressions (CTEs) in the root line, optimized database queries shorten the loading time and increase the response speed. This ensures a smoother user experience, even with complex page structures. A significant improvement for anyone who relies on fast and efficient content!
In TYPO3 13, the option to define individual entry points for Backend was introduced! Until version 13, access was always possible via the path `/typo3`. Now, however, this path can be customized to use user-defined URLs or domain names.
This flexibility increases security, as the default access point no longer has to be used. This innovation enables a more individual configuration of the TYPO3 instance and improves the protective measures against potential attacks on the administrator interface.
- See also: BE
- Feature: #87889 - Configurable TYPO3 backend URL
In TYPO3 13 there is now support for SVG crops and WebP formats! These functions enable improved handling of graphics and images. SVGs can now be cropped more efficiently and used in different sizes, while WebP as a modern image format reduces loading times and improves image quality.
The integration of these formats ensures an optimized user experience and faster loading times, which is especially beneficial for modern websites. A great extension for anyone who values image quality and performance!
TYPO3 introduces a simple log rotation to prevent the growth of log files, which can lead to full hard disks. Without regular cleanup, log entries quickly become cluttered.
The new approach follows the "copytruncate" method: The currently open log file is copied (e.g. to `typo3_[hash].log.20230616094812`), while the original file is emptied. This makes it easier to deal with open file handles.
A new file writer, `\TYPO3\CMS\Core\Log\Writer\RotatingFileWriter`, extends the existing `FileWriter` class and enables efficient log management, even in hosting environments without logrotate.
This new feature improves the handling of log files and ensures that they always remain clear.
In TYPO3 13, cache busting for file resources is optimized through the introduction of file version numbers. This feature allows developers to ensure that the latest versions of files such as CSS, JavaScript and images are always loaded without users having to manually clear the cache.
By assigning versioning numbers to files, changes can be reflected immediately, making it easier to update content while optimizing load times. This innovation improves the user experience and ensures that web pages are always displayed with the most up-to-date resources, without the complications of outdated files. An important step for efficiency in TYPO3 development!
- Feature: #99203 - Streamline FE/versionNumberInFilename to 'EXT:' resources
- https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Data.html#asset
- https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Configuration/Typo3ConfVars/FE.html#confval-typo3-conf-vars-fe-versionnumberinfilename
- https://docs.typo3.org/other/typo3/view-helper-reference/main/en-us/Global/Uri/Resource.html#viewhelper-argument-typo3-cms-fluid-viewhelpers-uri-resourceviewhelper-usecachebusting
TYPO3 v13 benefits - DEV
In TYPO3 version 13, the new Frontend attribute `frontend.page.information` was introduced, replacing various page-related properties of the `TyposcriptFrontendController`.
Although the class is currently marked as experimental, extension authors are encouraged to already access this attribute instead of using the TSFE properties. The TYPO3 core will try not to break the getters and properties that are not marked `@internal`.
The `frontend.page.information` attribute provides commonly used page information and is appended to the PSR-7-Frontend request by the middleware `TypoScriptFrontendInitialization`. Other middleware components can rely on the existence of this attribute, which simplifies development and integration in TYPO3 applications.
In TYPO3 v13, the function for automatically creating database columns from TCA column definitions has been further developed. Developers no longer have to declare these explicitly in `ext_tables.sql`.
The automatic creation of "management" fields such as `uid` and `pid`, which are derived from the TCA `ctrl` settings, was already supported in earlier versions. Now this is extended to individual TCA columns. The aim is that extension authors no longer need to maintain `ext_tables.sql` definitions for common table fields. This file can be omitted in many cases, while the core creates the fields with meaningful default values.
The following types are supported: select, datetime, number, inline, link, radio, color, password, text, flex, group, language, imageManipulation, folder, check, email, file, input. A "country" type is still being worked on.
Of course, it is still possible for developers to overwrite specific definitions in `ext_tables.sql` if the core definitions do not meet the desired requirements. Explicit definitions in `ext_tables.sql` always have priority.
Support for the modern image format WebP is now activated in TYPO3, provided that the ImageMagick or GraphicsMagick library used supports WebP. WebP offers several advantages over PNG and JPEG, including:
- Smaller file sizes: WebP images are about 30% smaller than JPEG or PNG files.
- Transparency: WebP supports an alpha channel, which JPEG does not.
- Compatibility: All modern browsers support WebP.
In addition, the GIFBUILDER library, which is responsible for image editing in TypoScript, can now also generate WebP files.
Another new feature is native support for cropping SVG images in Backend. When editing or using Fluid ViewHelpers such as `<f:image>` or `<f:uri.image>`, the image is saved as SVG by default instead of rasterized formats such as PNG or JPG.
These improvements provide TYPO3 users with more flexibility and efficiency in image processing and help to optimize web page load times.
The introduction of the null coalescence operator (??) in TypoScript constants greatly simplifies the handling of variables. Developers can now specify default values that will be used if a variable is not set. This allows a seamless transition from deprecated constant names to new names, while maintaining full backwards compatibility to the old name if it is still defined.
This innovation can not only reduce code, but also improves the readability and maintainability of TypoScript implementations.
The PAGEVIEW cObject was introduced in TYPO3 to simplify the rendering of complete pages in Frontend. It offers fewer configuration options than the FLUIDTEMPLATE cObject.
A simple example of use:
```typo3_typoscript
page = PAGE
page.10 = PAGEVIEW
page.10.paths.100 = EXT:mysite/Resources/Private/Templates/
```
The PAGEVIEW cObject automatically resolves the name of the page layout. For a layout named "with_sidebar", the template file becomes `EXT:mysite/Resources/Private/Templates/Pages/With_sidebar.html`.
Fluid functions for layouts and partials are also automatically linked and can be stored in the corresponding directories.
Standard variables such as settings, site, language and page are available in the Fluid template.
This new feature makes page rendering in TYPO3 more efficient and user-friendly.
The site-specific TSconfig is loaded from the file `page.tsconfig`, which is stored alongside the configuration file `config.yaml` in the storage directory of the respective site (config/sites/<identifier>/).
This function allows page TSconfig to be defined at the level of individual pages without requiring database entries or burdening the global scope. Extensions and site packages can also provide TSconfig in site sets by placing a `page.tsconfig` file in the appropriate set directory.
This structure allows sites and sets to provide page TSconfig efficiently, while dependencies can be expressed via site sets. This enables automatic ordering and deduplication, which greatly simplifies the handling of configurations.
TYPO3 has been extended to allow sites to act as TypoScript template providers. This function is similar to sys_template records with activated "clear" and "root" flags. A site TypoScript provider always defines a new scope (corresponds to the "root" flag) and does not inherit from parent sites. This means that it behaves as if the "clear" flag were set in a sys_template data set. This functionality is not configurable, as TypoScript sharing is provided via sharable sets.
It is important to note that sys_template records are still loaded, but are optional and are applied according to the TypoScript provided by the site.
TypoScript dependencies can be included via set dependencies. This mechanism is much more effective than previous `static_file_include` or manual `@import` statements, as sets are automatically sorted and deduplicated. This innovation improves the handling of TypoScript and enables a more flexible and efficient configuration in TYPO3.
With the new functionality of site sets, it is possible to provide parts of the site configuration as combinable modules. These sets are intended to provide settings, TypoScript, TSconfig and referenced, activated inhaltsblocks for the scope of a site.
Extensions can provide multiple sets to provide presets for different sites or subsets (think of frameworks) where selected functions are presented as a subset (e.g. /seo-xml-sitemap). E.g. typo3/seo-xml-sitemap).
A set is defined in a subfolder of the extension in `Configuration/Sets/`, for example in `EXT:my_extension/Configuration/Sets/MySet/config.yaml`.
The folder name in `Configuration/Sets/` is arbitrary, but the name defined in `config.yaml` is decisive. This name conventionally follows the vendor/name scheme and should use the same vendor as the extension it contains. If necessary, it can differ for compatibility reasons (e.g. if sets are moved to other extensions). If an extension provides exactly one set, its name should match the name defined in `composer.json`.
Advantages:
- Modularity: Site sets enable modular handling of site configurations, which increases reusability and customizability.
- Flexibility: By providing multiple sets, developers can offer specific configurations for different scenarios and requirements.
- Easy integration: The clear structuring and naming facilitates the integration and management of configurations in TYPO3 projects.
This innovation represents a significant advance in the handling of site configurations in TYPO3 and promotes more efficient and customizable development.
The latest TYPO3 version introduces a new TypoScript data processor for FLUIDTEMPLATE and PAGEVIEW: the record-based Transformation Data Processor. This processor can be used in conjunction with the DatabaseQuery Data Processor to retrieve database records and transform them into record objects.
The record-transformation Data Processor is particularly useful for TCA tables that contain "types" such as pages or tt_content. It ensures that only relevant fields are included in the record object. It also extracts important information from "enableColumns", deleted fields as well as language and version data to enable consistent editing.
One outstanding feature is the "type" property, which specifies the name of the database table and the specific type of entry, such as "tt_content.textmedia" for contentltselements. This new feature significantly improves the handling of database entries and optimizes the development of TYPO3 applications.
In the latest TYPO3 version, the Site Settings Editor has been introduced as a Backend module under Site Management > Settings. This module provides a clear view of all sites in the current installation and allows you to edit the site settings for all relevant pages.
The Settings Editor displays the settings of all configurations contained in the current site set, including their dependencies. Site sets can define categories and subcategories to better organize the settings.
The settings to be displayed must be defined in a definition file within an extension or site package, for example in `EXT:my_sitepackage/Configuration/Sets/MySitepackage/settings.definitions.yaml`. Settings made directly in `settings.yaml` without corresponding entries in `settings.definitions.yaml` are not displayed in the editor as they have no type or label. However, these values are retained when the editor writes to `settings.yaml`.
This new feature makes managing site settings in TYPO3 much simpler and more structured.
In the latest TYPO3 version, support for the UNION clause was introduced in the QueryBuilder. This clause makes it possible to combine the result sets of two or more SELECT statements, a feature supported by all major database vendors, but with different variations.
With version 4.1.0 of Doctrine DBAL, generic support for the UNION clause has been added. TYPO3 extends the Doctrine DBAL QueryBuilder to ensure automatic quoting of identifiers and values as well as the application of database restrictions for SELECT queries.
Now developers can use the new API methods of the TYPO3 \QueryBuilder to create UNION clauses more easily. The API allows the use of dedicated QueryBuilder instances or the insertion of direct queries as strings.
Note: It is important to note that using the QueryBuilder to create UNION clauses is not compatible with all database providers, especially if LIMIT/OFFSET is used in the individual subqueries.
Impact: Extension authors can use the new QueryBuilder methods to create more complex queries and significantly increase the flexibility of their database queries.
In the current TYPO3 version, static route variables can now be declared directly in the configuration of the route enhancer. This simplifies the handling of URLs, as user-defined route aspect mappers are no longer required.
Important: Static variables only apply if:
- No aspect mappers are configured: These take precedence over static variables.
- A request definition is present: This should be restrictive to avoid cache problems.
This new feature improves the flexibility and user-friendliness of route management in TYPO3.
In the latest TYPO3 version, static routes can now also be configured for assets. This makes it possible to create links to resources located in directories such as EXT:my_extension/Resources/Public/. These asset URLs can be customized on a site-by-site basis, making it possible to provide site-specific custom favicons or manifest files.
This new feature makes it easier to manage and customize resources in TYPO3 installations, as static routes to extension files can now be defined directly in the site configuration.
The content relating to the features has been AI-generated, checked for content and relevance anderpadjusted. However, if we have made a mistake, please let us know so that we can keep our information up to date for ourselves and everyone else.
We all benefit from the enthusiasm of the TYPO3 community, and the shared expertise will also deliver exciting new features for version 14.
We actively shape the TYPO3 CMS
With Fluid Components and the Fluid Styleguide, for example, we have created a native component ecosystem for the TYPO3 fluid stack. This and other extensions developed by us are available to the entire community as open source software and are used intensively. At the same time, we and our customers also benefit from the community's solutions.
