--- title: "Maintaining TYPO3" manual: "Getting Started" version: "main" permalink: "https://docs.typo3.org/permalink/t3start:getting-started-typo3-updates@main" source: "Installation/Updates/Index.rst" rendered: "2026-09-20T09:47:06+00:00" --- # Maintaining TYPO3 {#getting-started-typo3-updates} **Content on this page** - [When and why should we perform TYPO3 updates?](https://docs.typo3.org/permalink/t3start:when-and-why-should-we-perform-typo3-updates@main) - [Major, minor and patch level updates](https://docs.typo3.org/permalink/t3start:major-minor-and-patch-level-updates@main) - [Extension updates](https://docs.typo3.org/permalink/t3start:extension-updates@main) - [Deprecations](https://docs.typo3.org/permalink/t3start:deprecations@main) - [Little Helpers: Rector and Fractor](https://docs.typo3.org/permalink/t3start:little-helpers-rector-and-fractor@main) - [Language updates](https://docs.typo3.org/permalink/t3start:language-updates@main) ## When and why should we perform TYPO3 updates? {#when-and-why-updates} With the newest version of TYPO3 you receive free bugfixes and free security patches for at least three years from the time of the first LTS minor (for example v14.3) release. In TYPO3 however, we follow a specific [cycle](https://typo3.org/cms/roadmap) which usually takes 1.5 years long. Every 1 and a half year a new TYPO3 version occurs. We explain the different parts in the [roadmap](https://typo3.org/cms/roadmap) now. When you follow the roadmap you see dark red strokes. They represent the **sprint releases**. Sprint release is a version that starts for example with v14.0 and then the next sprint release follows with v14.1. After the last sprint release (v14.2) the **Long Term Support release (LTS release)** v14.3 follows. The aim of the sprint releases is to test the new code with the new features extensively, until the LTS-release is reached. Therefore, the reason for sprint releases is to make the new code with the new features as agile and stable as possible. The order is: sprint release (0), sprint release (1), sprint release (2), sprint release (3), LTS release (4). Sometimes more sprint releases are possible. The green area represents the **regular maintenance** state. The orange area is the time where the focus lays on fixing bugs - so it is the **bug fixing phase**. The light orange area corresponds to the **extended support**. This means, when you want to get further bugfixes you have to book an [extended support](https://typo3.com/services/extended-support-elts) which usually costs money. Before we look a bit deeper into the [types of updates](https://docs.typo3.org/permalink/t3start:getting-started-major-minor-patchlevel-updates@main) we summarize how a TYPO3 user should act with respect to TYPO3 updates: - When a new major LTS version is released, users **should** focus on updating to this version as soon as possible. - When a new minor version is released, users **must** update to the new minor version, since the previous minor version is **not** supported any more. - When a new patch level version is released, users **should** always update to the new version, because it contains **important** bugfixes and security fixes (if announced). Here you find the [security advisories](https://typo3.org/help/security-advisories). Additionally, users should take care of updated extensions on a regular schedule in order to use the most recent versions. When you feel safe with the concepts of TYPO3 updates you can in general use this [Upgrade Guide](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/Index.html#upgrading). Now we explain the types of updates. ## Major, minor and patch level updates {#getting-started-major-minor-patchlevel-updates} In TYPO3 you can update your TYPO3 version. There exist three different types of updates: 1. Major updates: for example, from 13.4.23 to 14.0.0 1. Minor updates: for example, from 14.0 to 14.1 1. Patch and bugfix level updates (often security updates): for example, from 14.3.0 to 14.3.1 ### Major updates {#getting-started-major-typo3-updates} In major updates you will definitely have **breaking changes** and incompatible API changes. A breaking change can cause your system to break. You need to find a replacement for any usage that was removed or changed. For example in version 14.0 was a breaking change [Breaking: #107473 - TypoScript condition function getTSFE() removed](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/14.0/Breaking-107473-TypoScriptConditionFunctionGetTSFERemoved.html#breaking-107473-1758113238). That means, whenever and wherever you used `[getTSFE() && getTSFE().id == 42]` as condition in your TypoScript Such usages have to be replaced with the update to something like `[request?.getPageArguments()?.getPageId() == 42]`. When you update your TYPO3 version you should be aware of those changelog entries which you can find in the [ChangeLog v14](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog-14.html#changelog-v14). When dealing with a major version update, you usually have to use the backend module called **Upgrade wizard**. This module will take care of database table changes that came along with the new TYPO3 version. In TYPO3, we can separate a TYPO3 update into three stages: the [pre-upgrade stage](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/Major/PreupgradeTasks/Index.html#preupgradetasks), [actual update](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/Major/UpgradeCore.html#upgradecore) and the [post-upgrade stage](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/Major/PostupgradeTasks/Index.html#postupgradetasks). ### Minor updates {#getting-started-minor-typo3-updates} Minor changes - `14.3.2`: For example 14.3 has new functionalities compared to 14.2. The version 14.3 is compatible with 14. So within a version like major 14, the steps do not lead to breaking changes. For example in version 14.2 compared to version 14.1 a new [Feature: #108726 - Introduce Fluid f:render.contentArea ViewHelper](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/14.2/Feature-108726-IntroduceFluidRenderContentAreaViewHelper.html#feature-108726-1769071158) was introduced. When performing minor updates, you often have to clear the cache, run the Upgrade wizard, and run a database compare. Usually minor and patch changes are also referred to as **non-breaking** changes. ### Patchlevel updates {#getting-started-patchlevel-typo3-updates} Patchlevel changes - `14.3.*`: The version 14.3.2 indicates a backwards-compatible bugfix or patch release. It can be for example a security update. Clear the cache and check if the website is working as expected. For further information we refer to the [Patch/Bugfix update guide](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/Minor/Index.html#minor). ## Extension updates {#getting-started-extension-updates} In a TYPO3 instance you have usually third party extensions installed. When you update your TYPO3 version, you have to update the third-party extensions too. In the **TER**, [TYPO3 Extension Repository](https://extensions.typo3.org/), you can enter the name of that extension and get information about supported TYPO3 versions. Some extension authors prefer to only publish their extensions on [packagist](https://packagist.org/packages/typo3/). When the extension does not exist for the current TYPO3 version you can create an issue or search for an alternative extension offering the same functionality. For example, any blog extension could be replaced by another of several blog extensions. Useful commands to simplify the updates of extensions can be found in the [Upgrade extensions guide](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Upgrade/UpgradingExtensions/Index.html#upgradingextensions). ## Deprecations {#getting-started-deprecations} In TYPO3, deprecations indicate that a specific functionality will be removed in the next TYPO3 version. For further information we refer to the [article about deprecation](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Deprecation/Index.html#deprecation). For example the [deprecation: #105171 - INCLUDE_TYPOSCRIPT TypoScript syntax](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.4/Deprecation-105171-INCLUDE_TYPOSCRIPTTypoScriptSyntax.html#deprecation-105171-1727785626) \- a deprecation notice telling you that in TYPO3 v14 you can't use the TypoScript syntax `INCLUDE_TYPOSCRIPT` to include TypoScript files anymore. ## Little Helpers: Rector and Fractor {#getting-started-little-helpers} In general you can use extensions like [Rector](https://github.com/sabbelasichon/typo3-rector) or [Fractor](https://github.com/andreaswolf/fractor) to find and replace deprecations. To reach this, you have to fill out a configuration file (in Rector `rector.php`, in Fractor `fractor.php`) that defines the scope in which you want to **perform deprecation replacements**. For both extensions, only the rules that exist can find the respective deprecation. For instance, check the [overview of existing rules for Rector](https://github.com/sabbelasichon/typo3-rector/blob/main/docs/all_rectors_overview.md) or [search for your desired Rector rule](https://getrector.com/find-rule) if it already exists. When a rule is missing, you can't find the deprecation using the extension. If you feel able to create your own Rector or Fractor rule and want to share it with the TYPO3 community, everyone using these tools would be happy to benefit from your efforts. ## Language updates {#getting-started-language-updates} After a TYPO3 update, you have to update your translations. We refer to the article [Update backend translations](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Administration/Tools/Maintenance/Index.html#update_backend_translation). You have to update the language packs that you are using after each TYPO3 update.