Fractor 1.0: Why I Can't Do Without It Anymore When Upgrading TYPO3

Fractor 1.0 has been available since July 9, 2026. I use this tool alongside Rector for almost every TYPO3 upgrade; it really pays off, especially with older installations. A personal look back at the release and why the combination of these two tools has become an integral part of my upgrade work.

Fractor 1.0 Is Here

Fractor 1.0.0 was released on July 9, 2026. Simon Schaufelberger, who has since taken over the tool’s main development, shared the announcement in the developer Slack channel, and I checked it out right away.

Fractor has been around since May 2024. Andreas Wolf and Sebastian Schreiber launched the tool to make non-PHP files migratable as well. Simon joined later, initially contributing many new rules and then increasingly synchronizing development with Rector. But the real reason I use Fractor so extensively is something else: it saves me a tremendous amount of work when migrating old TypoScript, Fluid view helpers, and the like.

What Fractor Actually Does

You’re probably already familiar with Rector: it automatically updates and modernizes PHP code. Fractor essentially does the same thing, but for all the other files that also become obsolete during a TYPO3 upgrade. TypoScript, Fluid templates, YAML configurations, XLIFF translation files, and more.

The core package a9f/fractor provides only the infrastructure for configuration and execution. The actual rules come from individual packages for each file type. As a TYPO3 user, you’ll usually just install a9f/typo3-fractor, which includes the relevant packages for Fluid, TypoScript, YAML, and more right out of the box.

Why I use it for almost every upgrade

I now use Fractor for practically every TYPO3 upgrade, always in combination with Rector. The process is almost identical for both tools: first a test run to see what would change, then review the suggested changes, and only then actually execute them. This consistency makes day-to-day work easier. I don’t have to switch between two completely different ways of thinking just because I’m working on a TypoScript file instead of a PHP class.

What I particularly like about this is that Fractor runs entirely under my control. Nothing happens automatically in the background. I see every suggested change before it actually makes its way into the code, and I can specifically exclude individual rules, files, or entire folders if something doesn’t work.

The real added value lies in older versions

When upgrading from current or relatively new TYPO3 versions, the effort required for TypoScript, Fluid, and related components is often minimal. Fractor becomes truly valuable for projects migrated from very old TYPO3 versions—the kind I encounter time and again in my work as an integrator and trainer.

Over the course of several major versions, a lot of outdated syntax accumulates: TypoScript notations that are no longer recommended, Fluid constructs that have been replaced by new ViewHelpers, and XLIFF files with obsolete formats. Going through this manually can quickly take several hours to days on larger projects. Fractor automates a good portion of this process, freeing me up to focus on the issues that really require careful consideration—such as deciding which extensions need to be replaced.

What’s New in Version 1.0

The changelog for 1.0.0 shows one thing above all: Fractor is moving even closer to Rector. The CLI parameters are now largely identical, with a few exceptions. Simon himself cites --only, --rules-summary, and --output-format as the most important ones.

In addition, there are smaller but practical new features: a --no-diffs option, a --memory-limit option, and the old --quiet option has been removed in favor of --no-diffs. A new XLIFF file processor, contributed by Christian Sonntag, expands the supported file types to include a format that is important for multilingual TYPO3 websites.

A Word of Thanks to the Developers

Tools like Fractor don’t just appear out of thin air. Andreas Wolf and Sebastian Schreiber laid the groundwork. Simon Schaufelberger has been playing a key role in driving further development for some time now. Christian Sonntag has contributed the XLIFF processor, a feature that is particularly relevant for international TYPO3 projects. Without this work behind the scenes, a large portion of my upgrade projects would be significantly more tedious.

By the way: Simon already hinted in the announcement that he’ll be presenting a new tool at the TYPO3 Developer Days that builds on Rector and Fractor. I’m curious to see what’s coming.

Conclusion

For me, Fractor has long since ceased to be a niche tool; it’s now an integral part of my upgrade workflow, right alongside Rector. Anyone taking over projects from older TYPO3 versions—or setting them up from scratch—should definitely check out this tool. Version 1.0 makes the user experience even more consistent with Rector, making it even easier to get started.