---
title: TYPO3 Rector - automated code upgrades for TYPO3
url: "https://www.typo3-rector.com/"
description: Use TYPO3 Rector for automated code upgrades of your TYPO3 website based on the official changelogs of TYPO3. Focus on testing instead of copy+paste.
date: 2018-01-22
modified: 2024-03-22
lastUpdated: 2024-10-15
---

# TYPO3 Rector - automated code upgrades for TYPO3

Support TYPO3 Rector
====================

Instantly upgrade and refactor the code of TYPO3
------------------------------------------------

TYPO3 Rector is based on Rector, a tool to instantly upgrade and refactor the PHP code of your application. We provide explicit rules and functionalities to rewrite your source code based on the official TYPO3 changelogs inbetween each release version.

---

    ![](https://www.typo3-rector.com/fileadmin/_processed_/a/f/csm_iStock-1215880495_ed1f762317.jpg) istockphoto.com 1215880495 What does TYPO3 RECTOR do?
--------------------------

Update and cleanup of:

- PHP Code
- TCA Configuration

Other file types like TypoScript, XML (FlexForm) and composer.json are supported by [Fractor](https://github.com/andreaswolf/fractor) which plays nicely together with TYPO3 Rector.

 TYPO3 Rector funding roadmap:
-----------------------------

Things that have to be done to use and enjoy the TYPO3 Rector in all versions now and in the future.

  ### Existence/Maintainance

The base of the funding will be used for pure maintenance and keeping rector alive.
This splits up like the following:

- dependency resolving after Rector core split
- general stability improvements along with those dependency changes
- transpiling PHP Version to useable version on migration process
- setup general release cycle/infrastructure to make TYPO3 Rector useable/accessible as package (this is where all previous points come together)

### Rules/Features

Basically this is what Rector is all about: the code migrations and a helping hand.

- develop TYPO3 core rules (test driven and based on the official core changelogs/docs)
- overall bug fixing and support for rector rules
- further development with upcoming releases
- reduce limitations/ increase features (like we did in the past with e.g. TypoScript and Flexform parsing)

### Giving back personally

As we are dependent on the community we will always give something back next to our tool itself.
This is nothing that can be defined in numbers or concrete actions, but we will provide support via slack or GitHub issues, but also be a helping hand in concrete issues, onboarding new users or even contributors and be present on events to spread awareness and serve the people that are helping us with using and feedback. In case there are any questions left, feel free to ask!

   Our Sponsors!
-------------

### You'd be in good company!

Please have a look at our Sponsors! These are companies and individualy that share a passion for efficiency and professionalis. Consider contacting them for collaboration or project requests!

    To display third-party maps, we need your consent.

 For more information, please see our [ privacy policy. ](https://www.typo3-rector.com/datenschutz/)

 Allow once  Always allow

   Need help? Get help!
--------------------

### We support you in many possible ways. Just pick one.

  [### TYPO3 Slack #ext-typo3-rector

Visit our slack channel within the official TYPO3 Slack #ext-typo3-rector

 Slack

 ](https://typo3.slack.com/archives/C019R5LAA6A)

 [### Github

Check the full docs within our repository or reach out with a GitHub issue.

 Github

 ](https://github.com/sabbelasichon/typo3-rector/issues)

 [### Twitter

check our TYPO3 Rector X account and DM or mention us to get our attention

 Twitter

 ](https://twitter.com/TYPO3Rector)