TYPO3 v13 vs TYPO3 v12: What’s New in Version 13?

Quick Decision Summary - Should You Upgrade to TYPO3 v13?

Here's who should think about going to TYPO3 v13

Go for it if:

• You're on TYPO3 v12 LTS and want things to stay solid for a while.
• Your add-ons are kept up-to-date.
• Your setup is composer-based and in good shape.
• You handle many sites or big company setups.
• You're after better backend speed and an updated core.

TYPO3 v13 works well if your team is keeping up with TYPO3's plans and getting ready for future LTS versions.

Maybe hold off if:

• You depend on add-ons that aren't supported anymore or are old.
• Your project has a lot of custom code using old methods.
• Your hosting doesn't support PHP 8.2 or newer.
• You're thinking of jumping straight to TYPO3 v14 soon.

If any of those are true, it's a good idea to check things out technically before deciding.

How risky is the upgrade?

• Low Risk: For small to mid-sized sites with standard add-ons and not too much custom work.
• Medium Risk: For projects using a bunch of third-party add-ons or some custom code.
• High Risk: For big company setups with old integrations, outdated add-ons, or complicated backend changes.

How hard the upgrade is mostly depends on your add-ons, not TYPO3 itself.

How much work will it take?

• Small site: Should be doable with good testing.
• Mid-sized company setup: Needs a careful check for compatibility.
• Big/multi-site setup: Best to do a thorough check, roll it out bit by bit, and test a lot.

If your TYPO3 v12 setup is in good shape, moving over should be pretty smooth.

What to do?

If your TYPO3 v12 is working well and getting updates, going to TYPO3 v13 is a smart move for stability and security in the long run.

If you're planning a major overhaul or jumping to TYPO3 v14 soon, think about the timing to avoid doing the same work twice.

Always do a compatibility check and test things out before upgrading.

TYPO3 v13 vs TYPO3 v12 - Side-by-Side Comparison

Major Changes in TYPO3 v13 to Note

TYPO3 v13 removes outdated features from prior versions while implementing new technical prerequisites. Projects with custom code should review the following areas: 

• Deprecated APIs removed 
  Functions and methods marked as deprecated in earlier versions are no longer available. Custom extensions relying on them must be updated. 
• PHP 8.2 strict typing impact 
  Stricter type handling may expose previously unnoticed type mismatches in custom code. 
• Updated Symfony base 
  Dependency updates may affect custom integrations built on Symfony components. 
• Backend module JavaScript adjustments 
  Changes in backend module architecture can require updates in custom backend modules.

What’s New in TYPO3 v13?

Updated System Needs (PHP 8.2+)

You’ll need PHP 8.2 or newer to run TYPO3 v13. This means:

• Things run faster.
• Fewer type errors.
• Better security.

Make sure your hosting and command-line interface (CLI) are running PHP 8.2 before you upgrade.

Better Backend and Dark Mode

The backend is now smoother and looks better.

• Interface tweaks.
• Full dark mode.
• Faster navigation.
• Handles big setups better.

If you're an editor who uses TYPO3 daily, you’ll notice it’s easier to use.

New Page Tree

The page tree is reworked to respond faster when you click.

• Dragging and dropping is quicker.
• Works better with large sites.
• Fewer delays.

This is really helpful for big websites.

Content Blocks

Content blocks are now fully supported and work well.

• Clearer setup.
• Less complex.
• Easier to make reusable things.
• Content is more consistent.

For agencies, this makes things easier to maintain and grow.

Site Settings

Managing settings is easier.

• Settings are all in one place.
• Better for multiple sites.
• Deployment is cleaner.
• Less duplication.

This makes managing big and multi-domain sites simpler.

Multilingual Support

TYPO3 v13 is better with multiple languages, including right-to-left (RTL) languages.

• RTL rendering is stable.
• The backend is easier for international teams to use.

Better Image Handling

Working with images is better.

• WebP is integrated.
• SVG processing is improved.
• Workflows are quicker.

Core Improvements

v13 keeps cleaning up old code and updating things.

• The codebase is cleaner.
• Better typing.
• Easier to maintain over time.

What Stays the Same

The upgrade doesn’t need a rebuild.

• The core is still stable.
• Extbase still works.
• TypoScript is mostly the same.

If your TYPO3 v12 is well-maintained, moving to v13 should be easy.

TYPO3 v13 Upgrade - What You Must Check Before Migrating

Upgrading from TYPO3 v12 to v13 is structured, but only when preparation is done properly. Review the following checkpoints before starting.

Server and Hosting Stuff to Check

Before you jump to TYPO3 v13, make sure your server is ready:

• PHP: Needs to be 8.2 or higher (and the command line, too).
• Database: MySQL, MariaDB, or PostgreSQL – just make sure they're a supported version.
• Command Line: The right PHP version is needed for scheduled tasks and upkeep.
• Composer: Keep those dependencies up-to-date and playing nice.

Ensure staging access, reliable backups, and sufficient server resources before proceeding.

Extension Compatibility Review

Extensions usually make upgrades hard, not TYPO3 itself.

• See if your extensions are okay in the TYPO3 Extension Repository (TER).
• Check any extensions you've made yourself.
• Find spots where old, outdated code is being used.
• Make sure the extension dependencies are all good.

If an extension isn't maintained anymore, that's usually where things get stuck.

Breaking Change Impact Assessment

TYPO3 v13 gets rid of old code and updates how things work internally. So, take a look at:

• Your code that uses those old methods.
• If the database needs to be updated.
• Any tweaks needed for the backend module JavaScript.
• If scheduled tasks and command-line still works.

Old code might need to be rewritten.

Upgrade Effort by Project Size

• Small Website: Should be pretty easy, but test!
• Medium-Sized Business: You'll need to check those extensions carefully.
• Big Company/Lots of Sites: Do a full check and roll it out slowly.
• Lots of Custom Code: Depends on how much old code you're using.

Hidden Upgrade Risks Most Teams Overlook

Things that often go wrong during testing:

• Scheduled tasks failing.
• Problems with Fluid templates.
• Extensions that aren't being maintained.
• Strict PHP 8.2 typing errors.

These usually don't show up until you test on a staging server.

Backup & Rollback Strategy

Before you upgrade:

• Back up everything – files and the database.
• Know how to go back to the old version if needed.
• Test that you can actually restore from the backup.
• Never upgrade the live site directly!

Staging & Testing Process

Do the upgrade on a staging server first. Check:

• How the website looks.
• The backend modules.
• Forms and other integrations.
• Scheduled tasks.
• If the extensions work.

Only go to the live site when you're completely sure everything is working.

Editor Training & Change Management

TYPO3 v13 has some tweaks to the backend. Let the editors know about:

• The updated look.
• The new page tree.
• Any config changes.

Even small changes to the interface can mess with their daily work.

TYPO3 v13 Upgrade Checklist

Before upgrading, confirm the following:

• PHP 8.2+ is installed (including CLI version)
• Database version meets TYPO3 v13 requirements
• All extensions verified for v13 compatibility
• Custom extensions reviewed for deprecated API usage
• Composer dependencies updated and conflict-free
• Full file and database backup created
• Staging environment tested successfully
• Scheduler tasks validated
• Frontend and backend functionality fully reviewed
• Rollback procedure defined and tested

Upgrade Readiness Overview