TYPO3 Update 13: What Does This Mean for Agencies?
If you think TYPO3 v13 is just another routine update, think twice! This upgrade modifies how agencies deliver/manage and futureise client projects with a faster editing experience built on a cleaner and modern technical foundation.
As the latest Long Term Support (LTS) version, TYPO3 v13 is about providing agencies with a more solid, safe, and scalable CMS. The choices you make now, whether you are running multiple client sites or one large client platform, will determine whether your experience in the next few years is smooth or a hassle.
In this guide, we’ll cover what’s new, what’s changing, and how agencies can prepare!
What’s New in TYPO3 13
TYPO3 13 introduces several helpful updates and system enhancements that agencies will notice immediately. The focus is on speed, usability, and cleaner coding, which ultimately improves project readiness and maintainability.
1. A smoother backend for editors
The TYPO3 backend has been redesigned to be faster and easier to navigate. The work of editors has been made significantly more efficient through mass editing features, a modernized page tree, and the choice between dark mode and light mode.
2. Modern technology under the hood
TYPO3 v13 updates the core to modern frameworks and removes outdated code that previously slowed down the system. It has been switched to PHP 8.2 or higher, which provides TYPO3 performance improvements and ensures long-term security.
3. Improved localization and media handling
The tools around localization and translation offer optimized workflows for global projects. TYPO3 improves the handling of modern image formats like WebP to increase user-friendliness and offers intelligent image cropping, allowing editors to work more flexibly without additional plugins.
4. Stronger security and reliability
Security throughout the system and in the extensions has been improved. The innovations in TYPO3 13 make it easier for developers to meet modern security requirements and best practices. Thanks to new coding standards and updated libraries, the system is now more stable and secure than ever before.
Why TYPO3 Update 13 Matters for Agencies
For agencies, TYPO3 13 presents a major opportunity. All major TYPO3 version releases shift how projects are developed and supported. Understanding those shifts can help TYPO3 agencies stay ahead of competitors and ease any last-minute panic over having to migrate TYPO3 versions.
1. It influences project timelines and budgets
As old APIs are removed and new system requirements are introduced, updates may require more time for testing and implementation. TYPO3 agencies that start planning early can better schedule and implement updates, rather than reacting only when a client deadline is pressing.
2. It improves how teams work
The faster backend, optimized code, and modernized tools reduce friction points in the daily workflow for both developers and editors. TYPO3 projects can be launched faster, maintenance becomes easier and more efficient, and teams work more productively and contentedly.
3. It protects client relationships
The use of unsupported TYPO3 versions increases security risks and maintenance efforts. Agencies that systematically migrate their clients to TYPO3 13 gain trust and demonstrate a willingness for long-term partnership, an important advantage in a competitive market.
4. It opens new revenue opportunities
Each upgrade offers the opportunity to create additional value. Agencies can offer migration projects, extended maintenance packages, or training on new workflows. Performance audits are also worthwhile. The upgrade to TYPO3 13 provides the chance to deepen customer relationships and open new avenues for digital growth.
Key Technical Changes to Know in TYPO3 v13
TYPO3 13 introduces some technical details for agencies to know prior to upgrading. These changes improve performance, security and maintainability but might impact older projects.
1. PHP and Database Requirements
- TYPO3 13 requires PHP 8.2 or higher, otherwise an error will occur.
- TYPO3 13 supports the following databases: MySQL 8.0.17+, MariaDB 10.4.3+, PostgreSQL 10+, and SQLite 3.8.3+.
2. Removal of Deprecated and Legacy APIs
- All classes and methods marked as deprecated in version 12 have been removed. Code based on these may therefore fail.
- The methods within GraphicalFunctions have been removed in version 13. Image generation is now done via GifBuilder.
- In the TypoScript context, some elements have been removed without direct replacement options.
3. Extension Compatibility
- Some third-party extensions may not work immediately. Agencies should therefore check compatibility with tools like the TYPO3 Extension Upgrade Checker Tool.
- Extensions may need to be updated or replaced before migration.
4. Configuration and Setup Changes
- TYPO3 13 has added new configuration guidelines and removed deprecated ones.
- Server environments must meet the new system requirements to ensure stability.
5. Backend and User Interface Enhancements
- The backend now features more intuitive operation, faster loading times in the page tree, mass editing, and support for right-to-left languages to improve localization.
6. Testing and Migration Tools
- The official documentation contains steps for dealing with breaking changes and extension updates.
- Agencies should first use the compatibility tool to check installed extensions before upgrading.
These changes make TYPO3 13 faster, cleaner, and more secure, but careful planning and testing are essential for a smooth migration.
How Agencies Should Prepare for TYPO3 13
Preparing for TYPO3 v13 will make sure that your agency is able to successfully upgrade sites for your clients without unnecessary downtime and errors.
Here is a working TYPO3 Roadmap to prepare:
1. Audit existing installations and extensions
- Create a list of all client websites, individual modules, and third-party extensions.
- Analyze which of them are compatible with TYPO3 13 and decide whether updates or replacement solutions are necessary.
2. Set up a staging environment
- Perform all upgrades in a staging environment first before making changes to live websites.
- Use this environment for regression tests, content checks, and performance analyses.
3. Plan budgets and timelines
- Create initial effort estimates for each website, including necessary extension updates and testing times.
- Plan buffers for unexpected tasks so that your projects do not stall.
4. Communicate with clients
- Proactively inform your clients about upcoming changes, planned maintenance times, and the benefits of the upgrade.
- Offer upgrade packages, maintenance options, or staggered migration plans to make costs transparent for clients.
5. Train developers and editors
- Developers need to familiarize themselves with the removed APIs and new features.
- Editors need guidance on new backend tools, such as mass editing or handling images.
6. Implement monitoring and fallback strategies
- Create backups before performing the upgrade.
- Plan fallback strategies in case issues arise during the migration to TYPO3 v13.
- Monitor performance metrics and error logs after the upgrade to ensure stability.
TYPO3 13 vs TYPO3 12 – Key Differences
Category | TYPO3 12 | TYPO3 13 | Key Change / Benefit |
Backend Performance & Usability | Standard page tree and content editing | Faster page tree, mass editing, smoother workflows | Editors can work more efficiently with fewer clicks |
Code Structure & Deprecated Features | Some deprecated APIs and classes are still present | Deprecated APIs and classes removed | Cleaner, more maintainable code; easier future upgrades |
Technology Stack | Supports PHP 7.4–8.1, older JS libraries | Requires PHP 8.2+, updated database drivers, and removed old JS libraries | Improved performance, security, and modern development standards |
Localization & Media Handling | Basic RTL support, older image handling | Full RTL support for selected languages, better WebP support, and improved cropping | More flexible for international projects and modern media formats |
Security & Compliance | Standard security measures | Stricter coding standards, updated libraries, stronger security | Reduced vulnerabilities and better long-term compliance |
Conclusion
For a TYPO3 Agency, planned upgrades will support smoother workflows, speedier project delivery and allow you to add value for clients through training, performance audits and maintenance packages.
By starting the planning early, you can avoid accidental downtime and convert TYPO3 v13 into a competitive advantage, which is not a problem!
FAQs
The support for TYPO3 12 LTS is provided up to April 30, 2025, for bugs and until October 31, 2025, for security issues. Sites should be upgraded before the support period lapses to maintain their security.
Costs vary for different sites based on their size, complexity, and the installed extensions. Each project will need to be reviewed in order for us to generate a realistic cost estimate.
Not all extensions may be compatible from the start. It's important to check for compatibility when upgrading and find replacements for extensions you are using that rely on deprecated APIs.
The time can vary depending on the number of sites, extensions, and the amount of customizations. A simple and small website might take a few hours to a day, while larger or complicated sites may take several days.
Yes, PHP 8.2 is required for TYPO3 13. If the server doesn't run PHP 8.2 or higher, it will need to be upgraded prior to migration.
Yes, but you need to ensure you have proper backup and staging procedures in place. Before performing a migration, be sure to take full deployments and full database backups.
Contact for project management and team coordination
Mihaela Angelova
Project Manager - Germany
Mihaela Angelova
Project ManagerMihaela keeps technology projects on track and ensures to meet business goals. She specializes in coordinating teams, optimizing workflows, and delivering projects. At NITSAN, she works closely with clients to transform ideas into actionable solutions. Outside of work, she enjoys exploring new hiking trails.
Be the First to Comment