TYPO3 v14 LTS: What's New, Release Dates and Upgrade Guide (2026)
TYPO3 v14 is the current TYPO3 version: the LTS release v14.3 was published on 21 April 2026.
By NITSAN GmbH. Updated: 28 October 2026.
TYPO3 v14.3 LTS was released on 21 April 2026. This guide covers what you need to know now: release and support dates, the main new features, system requirements and the path to upgrade. All dates come from TYPO3 and are linked to their sources. For all versions side by side, see the TYPO3 roadmap.
TYPO3 v14 at a glance (as of 28 October 2026)
- Release: 21 April 2026 (v14.3 LTS)
- Bug fixes until: 31 December 2027
- Security updates until: 30 June 2029
- ELTS until: 30 June 2032 (per get.typo3.org)
- PHP: 8.2 to 8.5
- Current patch release: v14.3.10
Sources: TYPO3 press release and get.typo3.org.
TYPO3 v14 Release Date & Roadmap Overview
TYPO3 v14 is the current major version of TYPO3. The LTS release v14.3 was published on 21 April 2026. All support dates compared with v13 and v12 are on the TYPO3 Roadmap.
In TYPO3, major versions are not just feature updates. They focus on long-term improvements to architecture, APIs, and system consistency, ensuring the platform remains stable and maintainable for enterprise use.
TYPO3 follows a structured and predictable release model, designed to balance innovation with stability. This approach allows agencies and enterprises to plan upgrades with confidence.
Key Roadmap Focus Areas
- System modernization
Removal of legacy patterns and reduction of technical debt - API harmonization
Cleaner, more consistent APIs for long-term extension stability - Backend usability
Improved editor workflows and overall user experience - Structured content
Better content modeling for scalable and multi-channel use cases - Enterprise-level stability
Focus on maintainability, predictability, and long-term support
Is TYPO3 v14 an LTS Release?
Yes, TYPO3 v14.3 is a Long-Term Support (LTS) release.
This includes:
- Long-term active support
- Extended security updates
- Suitability for long-running enterprise projects
For agencies and enterprises, LTS releases provide predictability, reduced upgrade pressure, and easier long-term planning.
Strategic Goals Behind TYPO3 v14
TYPO3 v14 focuses on modernisation rather than isolated extras. Legacy patterns are removed, APIs become more consistent and the backend gets clearer.
Focus areas
- System modernisation: removal of legacy patterns and reduced technical debt
- API stabilisation: cleaner, more consistent APIs and removal of deprecated methods
- Backend: reworked interface with a new context panel and leaner navigation
- Structured content: better content modelling for scalable multi-channel projects
TYPO3 v14 LTS: status and lifecycle
TYPO3 v14.3 is the LTS (Long Term Support) release of the v14 line and was released on 21 April 2026. The phases:
- Bug fixes until 31 December 2027
- Security updates until 30 June 2029
- ELTS afterwards, until 30 June 2032 according to get.typo3.org. The glossary entry on TYPO3 ELTS explains what that means.
LTS versions are the recommended basis for production websites because they make budgets and upgrade dates predictable. The TYPO3 roadmap shows when each version ends.
Why TYPO3 v14 Matters for Agencies and Enterprises
TYPO3 v14 mainly affects long-term planning: budget, upgrade dates and maintenance.
Long-term planning
TYPO3 v14.3 is the current LTS release. For many organisations it defines the next stable upgrade cycle. This has a direct effect on:
- Budget planning
- Upgrade roadmaps
- Ongoing maintenance strategy
Skipping an LTS release can increase the complexity and cost of future migrations.
Upgrade planning
If you run v13, you have until 31 December 2027 (end of bug fixes). If you are still on v12, free support has ended. Recommended steps:
- Check custom and third-party extensions for compatibility, for example with the TYPO3 Version Checker
- Set up a staging environment for testing
- Align the upgrade date with your business cycles
Leaving preparation until shortly before support ends often means higher costs and time pressure.
Alignment with the ecosystem
With each new LTS release, extension developers shift their maintenance to the new standard. Moving early avoids compatibility gaps. The exact dates for every version are on the TYPO3 roadmap.
TYPO3 v14 release schedule and support dates
TYPO3 v14.3 LTS has been released. This table shows the dates TYPO3 publishes (as of 28 October 2026):
Milestone | Date | Source |
TYPO3 v14.3 LTS release | 21 April 2026 | |
First maintenance release v14.3.1 | 12 May 2026 | |
Last planned maintenance release v14.3.24 | 14 December 2027 | typo3.com maintenance schedule |
Bug fixes end | 31 December 2027 | TYPO3 press release |
Security updates end | 30 June 2029 | TYPO3 press release |
ELTS ends | 30 June 2032 |
What the dates mean for you
- On v14.3, apply patch releases as they come. get.typo3.org currently lists v14.3.10.
- According to TYPO3, new projects start on v14. For existing v13 sites, plan the upgrade before support ends on 31 December 2027.
- Sites on v12 have had no free support since 30 April 2026. The way forward is an upgrade, or ELTS as a bridge.
Compare the previous version: TYPO3 v13 LTS.
What's new in TYPO3 v14 (overview of the main features)
TYPO3 names these changes in its press release for v14 LTS:
Area | What changes | Who benefits |
Backend interface | Reworked backend focused on usability, with a new context panel for editors and leaner navigation | Editors, backend administrators |
Camino theme | Default theme as an optional system extension, enabled by default on new installations | New projects, quick prototypes |
QR codes and short URLs | New backend modules for QR codes and short URLs | Marketing and editorial teams |
Form Framework | Extensive enhancements to the form framework | Integrators, editors |
Translation workflow | Guided workflow for multilingual content | Multilingual sites, editorial teams |
API cleanup | Deprecated APIs from v12 and v13 are removed, APIs more consistent | Extension developers, agencies |
The first five rows come from the TYPO3 press release. The API cleanup row follows from the rule that major versions remove deprecated functionality. Details on individual changes are in the TYPO3 release notes. What this means for your extensions is covered in the section on breaking changes.
TYPO3 v14.0 to v14.3: what each release brought
TYPO3 v14 grew in several steps: v14.0 was released on 25 November 2025, and v14.3 followed as LTS on 21 April 2026. TYPO3's official changelog shows where the changes are (as of 28 October 2026):
Release | Breaking changes | New features | Deprecations |
v14.0 | at least 61 | not listed | not listed |
v14.1 | 0 | 18 | 3 |
v14.2 | 0 | 98 | 29 |
v14.3 LTS | 0 | 0 | 11 |
Source: TYPO3 Core Changelog v14. The v14.0 figure is based on the visible list and is a lower bound.
Examples from the changelog
- v14.0 (breaking): the backend module "Database Relations" was removed, the field "url" of the table "pages" was dropped, logout handling in EXT:felogin changed and a stronger algorithm is used for HMAC.
- v14.1 (features): Fluid components integration and a QR code module.
- v14.2 (features): a new page creation wizard, a Short URL module, a rich text editor in the form editor, database storage for forms, rate limiting for Extbase actions and access gates for backend modules.
- v14.3 (LTS): no new features and no breaking changes since v14.0, but 11 deprecations. That makes the LTS release a stable base.
What this means for your upgrade
Most breaking changes are in v14.0. If you come from v13, check your extensions and customisations against that list. No further breaking changes were added from v14.1 on. How to proceed is shown in the upgrade guide section and in the article on the TYPO3 upgrade.
TYPO3 v14 vs TYPO3 v13, Technical Comparison
The table below highlights the key technical differences between TYPO3 v13 and TYPO3 v14.
Area | TYPO3 v13 | TYPO3 v14 | Practical Impact |
Architecture | Continued modernization with some legacy support | Further cleanup and removal of legacy structures | Cleaner long-term foundation; review custom code |
API Structure | Stable APIs; deprecated methods still available | Stricter APIs; deprecated methods removed | Extension updates may be required |
Developer Workflow | Established patterns with compatibility layers | More structured approach; reduced legacy handling | Short-term adjustment; improved maintainability |
Extension Ecosystem | Broad compatibility; mature ecosystem | Some extensions require compatibility review | Extension audit recommended before upgrade |
Backend User Experience | Stable and functional interface | Cleaner layout; improved consistency | Easier editor onboarding and daily use |
TYPO3 v14 for Headless & API Projects
TYPO3 v14 strengthens its position for API-driven and hybrid (headless) architectures, while maintaining its traditional CMS capabilities.
API & Headless Direction
- Improved API consistency and structure
- Removal of deprecated methods
- Better long-term integration stability
Headless Suitability
- Supports structured content models
- Suitable for API-based and hybrid setups
- Works well for multi-channel publishing
Limitations
- Not headless-first by default
- Requires custom frontend implementation
- Some extensions may need adjustments
TYPO3 v14 is best suited for headless projects where structure, governance, and long-term maintainability are priorities.
TYPO3 v14 and AI: what TYPO3 names and what it does not
The changes TYPO3 names for v14 LTS (backend context panel, Camino, QR code and short URL modules, Form Framework, translation workflow) include no built-in AI feature. If you want to use AI, you connect it through extensions or external services.
What to consider when using AI
- AI-generated content needs a review process by editors.
- External AI services can raise data protection questions, especially in the DACH region and with personal data.
- Legal and compliance checks remain the operator's responsibility.
In TYPO3, AI is therefore an addition through extensions, not part of the core.
Strategic Focus Areas in TYPO3 v14
TYPO3 v14 focuses on long-term platform improvement rather than isolated feature additions.
Backend Usability Improvements
- Improved interface
- Improved accessibility
- Improved workflows
Goal: Improve editor and administrator usability.
Standardization & Best Practices
- Improved coding standards
- Improved project structure
- Improved implementation patterns
Goal: Improve project consistency and reduce technical debt.
Improved Onboarding
- Improved documentation
- Improved setup instructions
Goal: Lower the barrier to entry without sacrificing architectural integrity.
Upgrade & Migration Improvements
- Improved deprecated code handling
- Improved migration paths
Goal: Improve long-term upgrade experiences.
AI Tooling (Carefully Introduced)
- Content editorial support tools
- Optional AI integration
Goal: Enable content teams without replacing governance workflows.
Ecosystem Strengthening
- Improved positioning
- Support for agencies and developers
Goal: Preserve a stable open source ecosystem.
TYPO3 v14 Breaking Changes
TYPO3 v14 introduces breaking changes focused on removing legacy code and enforcing modern standards. These changes primarily affect custom development and older extensions.
Key Breaking Changes
- Removal of deprecated APIs
APIs marked as deprecated in earlier versions (v12/v13) are fully removed in v14 - Stricter coding and architectural standards
Extensions must follow updated TYPO3 core patterns and conventions - Backend/UI adjustments
Changes in backend behavior and structure may impact editor workflows - Extension compatibility risks
Not all third-party extensions will be immediately compatible
Practical Examples
- Extensions using deprecated Extbase or TypoScript patterns may fail or require refactoring
- Custom integrations relying on outdated hooks or APIs may break after upgrade
- Backend modules may need UI adjustments to align with updated layouts
Key Risk Insight
The biggest upgrade risk comes from:
- Custom-built extensions
- Unmaintained or outdated third-party plugins
Early compatibility checks and code reviews are essential to avoid upgrade blockers.
TYPO3 v14 system requirements
According to get.typo3.org, TYPO3 v14 has these minimum requirements:
Component | Requirement |
PHP | 8.2 to 8.5 |
Composer | 2.1 or higher |
MySQL | 8.0.17 or higher |
MariaDB | 10.4.3 or higher |
PostgreSQL | 10 or higher |
SQLite | 3.8.3 or higher |
Memory (RAM) | at least 256 MB |
Before upgrading, check your PHP version, database and hosting. For the requirements of all versions, see TYPO3 system requirements.
TYPO3 v14 Upgrade Guide & Strategy
An upgrade to TYPO3 v14 succeeds with a structured, phased approach, especially with custom extensions or legacy code.
Step by step to the v14 upgrade
- Audit the installation: review core version, extensions and custom code.
- Remove deprecated code: clean up old APIs and legacy implementations.
- Check extensions: confirm compatibility of core, custom and third-party extensions, for example with the TYPO3 Version Checker.
- Validate infrastructure: check PHP 8.2 to 8.5, database and hosting against the system requirements.
- Set up staging: test the upgrade in an isolated environment.
- Run the upgrade: use the official upgrade wizards and database migrations. The process is described in the article on the TYPO3 upgrade.
- QA and go-live: complete testing before releasing to production.
Complexity and risks
- Low complexity: standard installations with maintained extensions
- Medium complexity: projects with some customisation
- High complexity: legacy code, outdated or unmaintained extensions
Typical risk factors are custom extensions that need refactoring, APIs removed in v14 and unsupported third-party plugins. For heavily customised projects, plan extra development and testing effort.
Timing
TYPO3 v14.3 LTS has been available since 21 April 2026, so start the audit and extension check now:
- From v13: plan the upgrade before bug fixes end on 31 December 2027.
- From v12: free support has ended, so upgrade soon or consider ELTS as a bridge.
- Apply patch releases continuously after the upgrade.
Which route fits which starting version is shown on the TYPO3 roadmap.
Migration checklist
- Audit all extensions (core, custom, third-party)
- Validate PHP version and infrastructure
- Remove deprecated code
- Set up a staging environment
- Run regression and compatibility tests
- Plan and run the production deployment
Who Should Upgrade to TYPO3 v14 and Who Shouldn’t?
TYPO3 v14 matters to every TYPO3 user, but the approach and priority differ by role.
Agencies
- Offer upgrade audits and migration services
- Structure client communication and planning
- Align services with the new LTS standard
Businesses
- Plan upgrades into budget and lifecycle management
- Ensure security and compliance
- Reduce long-term operational risk
Developers
- Adapt your own extensions to updated APIs and coding standards
- Refactor and modernise custom extensions
- Test compatibility against v14.3
In most cases TYPO3 v14 belongs in your plan for the next upgrade cycle, even if the migration does not happen immediately.
When you can postpone the upgrade
A delay can make sense in the short term if:
- your project is close to launch
- critical extensions are not yet compatible
- you lack development resources
- the upgrade conflicts with business priorities
Postpone on purpose, not by default. On v13 the deadline is 31 December 2027; on v12 it has already passed. The TYPO3 roadmap helps you decide which version fits you now.
Risks of delaying TYPO3 v14 adoption
A postponed upgrade saves effort in the short term but often increases risk, cost and complexity in the long term.
Key risks
- Security risk after end of support: without security updates and bug fixes, technical and legal risk grows. For v12, free support has already ended; what comes next is explained under TYPO3 ELTS.
- Growing technical debt: outdated code accumulates and the gap to the current version widens.
- Extension ecosystem drifting apart: developers mainly maintain current versions, so older extensions receive fewer updates.
- Higher upgrade costs later: skipped versions add refactoring effort, test complexity and project scope.
Incremental upgrades are usually faster and cheaper than big version jumps. What exactly happens after support ends is covered on the TYPO3 roadmap.
TYPO3 v14 for Agencies, Developers, and Enterprises
TYPO3 v14 affects agencies, developers and businesses differently. Planning should reflect your role and responsibility.
TYPO3 v14 for agencies
Service portfolio implications
- Growing demand for upgrade audits
- Extension refactoring services
- Infrastructure modernisation support
Agencies should formalise structured upgrade offerings. The process of a TYPO3 upgrade is the basis for that.
Client advisory strategy
- Communicate lifecycle timelines early, for example via the TYPO3 roadmap
- Recommend compatibility audits
- Align upgrades with client business cycles
Clear guidance strengthens long-term client relationships.
TYPO3 v14 for extension developers
API refactoring
- Remove deprecated APIs
- Align with updated standards
Test your extensions' compatibility against TYPO3 v14.3 LTS now.
Forward compatibility
- Avoid short-term patches
- Follow official API patterns
- Align with the LTS roadmap
Proactive alignment reduces future maintenance overhead.
TYPO3 v14 for enterprise IT and the public sector
Procurement planning
- Align upgrades with budget cycles
- Include testing and training resources
Governance alignment
- Review editorial workflows
- Reassess extension strategy
Compliance review
- Validate security configuration
- Confirm data protection alignment
- Review infrastructure policies
Early preparation supports risk reduction and operational continuity.
TYPO3 v14 in the Context of Modern CMS Trends
TYPO3 v14 aligns with long-term CMS developments while maintaining architectural discipline.
Structured Content
- Clear content modeling
- Reusable data structures
- Multi-channel readiness
API-First Direction
- Improved API consistency
- Stronger integration capability
AI-Assisted Workflows
- Editorial assistance tools
- Human oversight remains required
Governance-Centric Architecture
- Strong role management
- Controlled workflows
- Enterprise stability focus
LTS-Based Planning
- Predictable lifecycle
- Clear upgrade paths
- Suitable for multi-year digital strategies
TYPO3 v14 represents structured evolution, focused on stability, clarity, and long-term value rather than short-term trends.
Conclusion
TYPO3 v14 represents a structured evolution of the platform. The focus is on architectural cleanup, API consistency, backend usability, and long-term maintainability.
For organizations running TYPO3 v12 or v13, preparation should begin early. This does not require immediate migration, but it does require:
- Extension compatibility review
- Infrastructure validation
- Lifecycle planning
- Budget alignment
Agencies should formalize upgrade strategies.
Extension developers should align code with updated APIs.
Enterprise IT teams should integrate TYPO3 v14 into long-term roadmap planning.
TYPO3 v14 continues the platform’s stability-focused approach. It introduces modernization without compromising governance or long-term support principles.
Early, structured preparation reduces upgrade risk and protects long-term investment.
FAQs
TYPO3 names, among other things, a reworked backend with a context panel and leaner navigation, the default theme Camino, new modules for QR codes and short URLs, Form Framework enhancements and a guided translation workflow.
According to get.typo3.org, TYPO3 v14 runs on PHP 8.2 to 8.5. It also needs Composer 2.1 or higher and, depending on the database, MySQL 8.0.17+, MariaDB 10.4.3+, PostgreSQL 10+ or SQLite 3.8.3+. Details under TYPO3 system requirements.
TYPO3 v14.3 LTS was released on 21 April 2026. get.typo3.org currently lists v14.3.10. All dates at a glance are on the TYPO3 roadmap.
Yes. TYPO3 v14.3 is the Long-Term Support (LTS) release of the v14 line. Bug fixes run until 31 December 2027 and security updates until 30 June 2029.
In most cases yes, before bug fixes for v13 end on 31 December 2027. First check extension compatibility (for example with the TYPO3 Version Checker) and test on a staging environment. The process is described in the article on the TYPO3 upgrade.
Not automatically.
Well-maintained extensions are likely to be updated, but custom or outdated extensions may require changes.
The changes TYPO3 names for v14 LTS include no built-in AI feature. AI can be connected through extensions or external services. Editorial review and data protection remain the operator's responsibility.
TYPO3 can be used headless or API-based, for example for structured content and multi-channel projects. This is not a new feature of v14 but depends on your architecture and extensions.
According to TYPO3: bug fixes until 31 December 2027, security updates until 30 June 2029. After that comes ELTS, until 30 June 2032 per get.typo3.org. More under TYPO3 ELTS.
Contact for Internet agency and TYPO3 projects
Sven Thelemann
Service Partner - Germany
Sven Thelemann
Client Service LeadSven Thelemann serves as the Client Service Lead at NITSAN, focusing on delivering TYPO3 solutions that meet client goals. With a strong understanding of technology and client expectations, he ensures smooth communication and project execution. Outside of work, Sven enjoys cycling and experimenting with homemade recipes.
Be the First to Comment