How to Check Your TYPO3 Version: Backend, Composer, CLI and No-Login Methods

Without backend or server access, public version checkers and page-source inspection may provide an estimate, although these methods are not always accurate. Knowing the exact installed version helps you confirm whether security updates are still available, check hosting and extension compatibility, and decide whether your website needs a patch update, ELTS coverage or a full TYPO3 Upgrade.

In this guide, we will explain every reliable way to check your TYPO3 Version, including backend, CLI, Composer, DDEV, Docker, core-file and no-login methods. You will also learn how to verify its support status and choose the right next step for your installation.

Quick Reference: Which TYPO3 Version Check Should You Use?

The best method depends on the level of access you have. Backend access is usually the fastest option, while CLI, Composer and the TYPO3 PHP API provide more reliable technical results. Public checks are useful only when no authenticated access is available.

Whenever possible, use the TYPO3 Backend, CLI, Composer or PHP API because these methods check the installed environment directly. Public checkers and visual clues should be treated as preliminary indicators, not as definitive proof of the version running on the live website.

What Is the Current TYPO3 Version in July 2026?

Source: https://typo3.com/typo3-cms/development-roadmap/roadmap

As of July 17, 2026, TYPO3 14.3.5 is the latest stable LTS release and the recommended choice for new TYPO3 projects. TYPO3 13.4.33 is the previous stable LTS version and remains actively supported for existing projects. Both versions were released on July 14, 2026.

Older branches, including TYPO3 12, 11 and 10, have reached the end of free community support. They can continue receiving security, compatibility and maintenance updates only through an active Extended Long-Term Support subscription.

The official TYPO3 download page confirms these current releases, support deadlines and maximum ELTS periods.

*ELTS generally provides up to three additional years of vendor support. A fourth year is available only to eligible TYPO3-Partners, so the dates shown above represent the maximum possible ELTS period.

Patch versions change as TYPO3 publishes maintenance and security releases. Before starting an update or upgrade, verify the latest release for your branch on the official TYPO3 download page and review the current development roadmap.

How to Check Your TYPO3 Version

The best method depends on the level of access you have. Backend users can usually find the version in a few clicks, while developers can verify it through the CLI, Composer, project files or the TYPO3 PHP API. If you only have access to the public website, you can still attempt a version check, although the result may be less precise.

Method 1: Check the Version in the TYPO3 Backend

For site owners, editors and administrators, the backend is usually the fastest way to check the installed TYPO3 version.

1. Open the TYPO3 backend login page, normally located at a URL ending in /typo3.
2. Sign in using your backend credentials.
3. Open the system information panel in the backend header.
4. Look for the TYPO3 version number and installation mode.

In TYPO3 14, the system information panel can display the installed version and indicate whether the website is running in Composer or Classic mode. Depending on the TYPO3 branch, configuration and user permissions, version information may also appear in an About or system-information area.

Always rely on the displayed version number rather than the appearance of the backend. Custom themes, extensions and interface changes can make an older installation look newer. TYPO3 14 also introduced significant backend changes, so visual inspection is not a reliable identification method.

If the version is not visible, your backend account may not have sufficient permissions. Ask a TYPO3 administrator to check it or use one of the technical methods below.

Method 2: Check the TYPO3 Version with the CLI

For developers and system administrators, the command line is one of the most accurate methods because it checks the TYPO3 Installation running in the current environment.

Open the project directory and run:

vendor/bin/typo3 --version

If the executable cannot be run directly because of file permissions, use PHP:

php vendor/bin/typo3 --version

The vendor/bin/typo3 command is the standard CLI entry point for Composer-based TYPO3 installations. Running it through PHP produces the same version information when the file is not executable directly.

Make sure the command is executed in the environment you want to inspect. A command run on a local development machine confirms the local version, not necessarily the version running on the live server.

Check the TYPO3 Version in DDEV

For a TYPO3 project running in DDEV, use:

ddev typo3 --version

DDEV runs the command inside the project container and accesses the TYPO3 executable from the Composer installation.

You can also run:

ddev exec vendor/bin/typo3 --version

This form makes it explicit that the command is being executed inside the DDEV container.

Check the TYPO3 Version in Docker

When TYPO3 runs in Docker, execute the version command inside the container that contains PHP and the TYPO3 application.

For example:

docker exec -it my_php_container bash
cd /var/www/html
vendor/bin/typo3 --version

Replace my_php_container and /var/www/html with the container name and application path used by your project.

Running the command on the host system may not work because the TYPO3 installation, PHP runtime and Composer dependencies are often available only inside the container.

Method 3: Check the TYPO3 Version with Composer

For a Composer-based TYPO3 Website, run:

composer show typo3/cms-core

The command displays information about the installed TYPO3 core package, including its exact version.

You can also inspect the Composer files, but each file provides different information:

• composer.json defines the TYPO3 version range the project is allowed to install.
• composer.lock records the exact package version resolved by Composer.
• composer show typo3/cms-core reports the package installed in the current environment.

For example, composer.json may contain:

"typo3/cms-core": “^14.3”

This does not confirm that the website is running TYPO3 14.3.5. The constraint allows compatible releases within the specified range. Check composer.lock or run composer show typo3/cms-core to identify the resolved version.

You should also confirm that the project files match the live installation. A local repository, staging environment and production website can run different versions when deployments are incomplete or dependencies are installed separately.

Method 4: Check the TYPO3 Version Programmatically

Extension and application developers can retrieve the runtime version through TYPO3’s Typo3Version class.

use TYPO3\CMS\Core\Information\Typo3Version;
use TYPO3\CMS\Core\Utility\GeneralUtility;
$typo3Version = GeneralUtility::makeInstance(Typo3Version::class);
echo $typo3Version->getVersion();
echo $typo3Version->getMajorVersion();
echo $typo3Version->getBranch();

The available methods include:

• getVersion() returns the complete installed version.
• getMajorVersion() returns the major version number.
• getBranch() returns the current TYPO3 branch.

This approach is useful when an extension needs to apply version-specific compatibility logic. Using TYPO3’s official version API is more reliable than hardcoding version assumptions throughout custom code.

Method 5: Check the TYPO3 Core Files

If you have access to the server through FTP, SFTP, SSH or a hosting file manager, you can inspect the TYPO3 project files.

For a modern Composer-based installation, use one of the following methods:

• Check composer.lock.
• Run composer show typo3/cms-core aus.
• Run the TYPO3 CLI command.
• Use the Typo3Version PHP API.

For a Classic installation without Composer, the CLI entry point may be:

typo3/sysext/core/bin/typo3 --version

Older installations may also expose version information in:

typo3/sysext/core/ext_emconf.php

Inside the file, you may find an entry such as:

'version' => '12.4.45',

Use ext_emconf.php only as a legacy fallback. It is not the preferred method for modern TYPO3 installations, especially Composer-based projects and current TYPO3 branches.

Method 6: Check the TYPO3 Version Without Backend Access

If you only have access to the public website, you can try page-source inspection, a public TYPO3 version checker or frontend fingerprinting. These methods may identify the major branch, but they cannot always confirm the exact installed patch.

Check the Page Source

Open the website in a browser, view the HTML source and search for a generator meta tag such as:

<meta name="generator" content="TYPO3 CMS">

Some websites may include TYPO3 or version-related information in this tag. However, developers often remove or customize generator metadata, so the absence of the tag does not mean the website is not running TYPO3.

Use a Public TYPO3 Version Checker

A public checker may inspect:

• accessible TYPO3 files
• frontend asset paths
• backend login behaviour
• HTML markup
• publicly visible version fingerprints

These tools can sometimes identify the TYPO3 major or minor branch. Exact patch-level detection is much less reliable because websites may hide, cache or customize the files used for identification.

Inspect Public TYPO3 Fingerprints

Backend login markup, TYPO3-specific URLs, JavaScript files, stylesheets and frontend asset structures may offer clues about the installed branch.

However, these signals can be affected by:

• custom TYPO3 distributions
• rewritten asset paths
• content delivery networks
• reverse proxies
• caching systems
• security rules
• restricted core files

A failed public check does not prove that the website is not using TYPO3. It may simply mean that the identifying information is hidden, modified or blocked.

For an accurate result, verify the version through the backend, CLI, Composer or the TYPO3 PHP API whenever possible.

Exact TYPO3 Version vs Major-Version Estimate

Not every method provides the same level of accuracy.

For security checks and upgrade planning, use the backend, CLI, Composer or PHP API. Public checkers are useful only when direct access is unavailable.

What Is a TYPO3 Version?

TYPO3 is an open-source CMS used for corporate, multilingual and enterprise websites. A version such as 14.3.5 contains three parts:

• 14: Major version
• 3: Minor or LTS branch
• 5: Patch release

Major versions may introduce new features, API changes and updated system requirements. Patch releases usually include bug fixes, maintenance improvements and security updates.

Your version determines which documentation, PHP versions, databases, extensions and upgrade instructions apply to your website.

Types of TYPO3 Releases

Sprint Releases

Sprint Releases introduce new features before a branch reaches LTS status. They have short support periods and are mainly suitable for testing and early adoption.

Long-Term Support Releases

LTS releases are intended for stable production websites. They receive regular maintenance and security updates for a defined support period.

Maintenance and Security Releases

Maintenance releases fix bugs and compatibility issues. Security releases address known vulnerabilities. Even supported LTS installations should remain on the latest available patch.

Extended Long-Term Support

ELTS is a paid service for older TYPO3 versions after free support ends. It provides additional security and maintenance updates while an organization prepares for an upgrade.

For most new production websites, the current stable LTS version is the best choice.

Why Does Your TYPO3 Version Matter?

Your installed version affects:

• security-update availability
• PHP and database compatibility
• extension support
• custom-code compatibility
• hosting requirements
• upgrade complexity
• maintenance and compliance planning

An older TYPO3 website may continue to work after support ends, but it will no longer receive regular free security and maintenance updates. Over time, outdated PHP versions, unsupported extensions and deprecated custom code can make future upgrades more difficult and expensive.

Is Your TYPO3 Version Still Supported?

Use this guide to decide what to do next:

• TYPO3 14: Current stable LTS. Keep the installation on the latest available patch.
• TYPO3 13: Supported previous LTS. Continue installing patches and plan a future TYPO3 14 upgrade based on project requirements.
• TYPO3 12: Free community support ended on April 30, 2026. Upgrade to a supported branch or obtain ELTS coverage.
• TYPO3 11 or 10: Available only through ELTS. Begin a structured upgrade assessment.
• TYPO3 9 or older: Unsupported. Prioritize a security, compatibility and modernization review.

TYPO3 12 installations did not stop working when free support ended. However, without an active ELTS subscription, they no longer receive official maintenance and security updates. TYPO3 10.4.59, 11.5.53 and 12.4.48 were released as ELTS updates on July 14, 2026.

TYPO3 Update vs Upgrade: What Is the Difference?

The terms “update” and “upgrade” describe different levels of change:

• Patch update: Moves within the same TYPO3 branch, such as 14.3.3 to 14.3.5. It normally includes bug fixes, maintenance improvements and security patches.
• Major upgrade: Moves from one major branch to another, such as 13.4 to 14.3. It can require extension checks, code changes, upgrade wizards and database updates.
• ELTS update: Installs maintenance or security fixes provided through an active Extended Long-Term Support subscription.
• Classic-to-Composer migration: Changes how TYPO3 and its dependencies are installed and managed. It is a project-structure migration rather than a normal core update.

TYPO3 recommends Composer mode for major upgrades from Classic installations, although Classic mode remains supported. Moving to Composer can improve dependency management, deployment consistency and future upgrade workflows.

Do You Need to Upgrade Through Every Major Version?

Not in every case, but skipping several major versions requires careful planning.

The TYPO3 Core includes upgrade wizards for the two preceding major versions. An installation that is further behind may require intermediate upgrade steps, additional migration tools or manual data and extension work.

Choose the upgrade path after reviewing:

• Current and target TYPO3 versions
• Available core and extension upgrade wizards
• Third-party and custom extension compatibility
• PHP and database requirements
• Deprecated or removed APIs
• Composer and deployment setup
• Required database migrations

Do not automatically follow a generic sequence such as v10 → v11 → v12 → v13 → v14. First audit the actual installation, then choose the safest supported route. A simple website may allow some work to be combined, while a heavily customized platform may require staged upgrades and testing at each major branch.

Now That You Know Your TYPO3 Version, What Should You Do?

Finding the version is only the first step. Next, confirm whether it is supported, compatible with your technology stack and safe to update.

Step 1: Check the Latest Release in Your Branch

Compare the installed version with the latest available patch for the same TYPO3 branch. Patch releases can include bug fixes, compatibility improvements and security updates.

Step 2: Confirm the Support Status

Determine whether your version:

• Receives free community support
• Requires an active ELTS subscription
• Has reached the end of all official support

An unsupported installation should be reviewed promptly, even when the website still appears to work normally.

Step 3: Audit Extensions and Custom Code

Check whether third-party and custom extensions support the target TYPO3 version.

Review:

• Composer version constraints
• Deprecated or removed APIs
• Abandoned extensions
• Custom integrations
• Extension upgrade instructions

One unsupported extension can turn an otherwise simple upgrade into a much larger project.

Step 4: Review the Technology Stack

Confirm that the server environment supports the current or target TYPO3 release. Check PHP, the database, required PHP extensions, image-processing tools and web-server configuration. TYPO3 checks several of these requirements during Composer-based installation.

Step 5: Create Verified Backups

Back up:

• The database
• Project and configuration files
• Publicly uploaded files
• Environment configuration
• Composer files and lock file

A backup is useful only when it can be restored, so test the recovery process before beginning a major upgrade.

Step 6: Test the Update on Staging

Reproduce the live environment on a staging system and perform the update there first.

Test the backend, frontend, extensions, custom functionality and deployment process before making any changes to production.

Step 7: Validate the Production Deployment

After deployment, verify:

• Backend access
• Frontend rendering
• Forms and email delivery
• Search functionality
• Redirects and routing
• Multilingual content
• Scheduled tasks and CLI commands
• External integrations
• TYPO3 and server logs

Finally, check the TYPO3 version again in production. The local repository, staging environment and live installation should all report the intended release.

Double-Check Your TYPO3 Technology Stack

Component	What to verify
PHP	Supported version, required extensions and php.ini configuration
Database	Supported engine, version, credentials and privileges
TYPO3 extensions	Core compatibility and active maintenance
Composer	Valid composer.json, lock file and reproducible installation
Web server	Apache, Nginx or IIS configuration
Image processing	Compatible ImageMagick or GraphicsMagick installation
Custom extensions	Deprecated APIs and upgrade-breaking changes
DDEV or Docker	Matching PHP, database and container settings
Deployment pipeline	Production receives the same dependencies tested on staging

TYPO3 requires a PHP-capable web server and access to a supported database. Composer manages dependencies in Composer-based installations, but it does not necessarily need to run directly on the live server. Dependencies can be built and tested in a dedicated deployment environment before the completed release is transferred to production.

Why Running an Unsupported TYPO3 Version Is Risky

An unsupported TYPO3 branch may continue to work, but it no longer receives the same level of maintenance and protection.

Possible risks include:

• No free security updates
• Compatibility problems with supported PHP versions
• Abandoned or outdated extensions
• Increasing custom-code debt
• More complex future upgrades
• Higher recovery and maintenance costs
• Possible compliance and browser-compatibility issues

Unsupported does not mean the website will be hacked immediately. It means security fixes, extension support and infrastructure compatibility can become harder to manage over time.

Common Problems When Checking a TYPO3 Version

The TYPO3 Backend Does Not Load

Check the server and PHP logs, confirm the backend URL and clear caches where possible. If the backend remains unavailable, use the CLI, Composer or project files to identify the version.

The Version Is Hidden by Permissions

Restricted backend users may not see system information. Ask an administrator to check the version or use a server-level method.

Files Are Inaccessible on Shared Hosting

Request FTP, SFTP or file-manager access from the hosting provider. If no server access is available, use the backend or a public version checker, although the result may be less precise.

vendor/bin/typo3 Is Missing

Make sure you are running the command from the project root and that the vendor directory exists. If dependencies have not been installed, run composer install.

The project may also use a Classic installation, which has a different CLI path.

Composer Shows a Version Range

You are probably checking composer.json, which defines the allowed version range.

For the resolved package version, check composer.lock or run:

composer show typo3/cms-core

The Public Checker Cannot Detect TYPO3

The website may hide generator information, customize assets, block public paths or use a CDN, reverse proxy or firewall.

Use the backend, CLI or Composer before concluding that the website is not running TYPO3.

The Website Runs Inside Docker

Run the TYPO3 command inside the PHP container. The host machine may not have access to the application files or PHP environment.

Composer and Classic Paths Are Being Confused

Look for composer.json, composer.lock and the vendor directory. Their presence usually indicates a Composer-based installation.

Classic installations use different TYPO3 core and CLI paths.

Staging and Production Show Different Versions

Treat production as the source of truth for the live website. Review the deployment process and logs to identify why the environments are no longer aligned.

Repository Files Do Not Match the Running Website

A Git branch or local composer.lock file does not confirm what is installed in production.

Check the live version through the TYPO3 backend, CLI or PHP API.

Security and Accuracy Notes

Avoid publishing unnecessary patch-level details for an outdated or vulnerable TYPO3 installation. Public version checkers should be treated as estimation tools, while visual inspection should never be used for security or upgrade decisions.

Whenever possible, verify the version directly in the live environment through the backend, CLI, Composer or TYPO3 PHP API. Recheck it after every deployment, because the repository, staging environment and production website may not always run the same release.

Final Thoughts

Checking your TYPO3 version takes only a few minutes, but it reveals whether the website is supported, receives security updates and is ready for future upgrades.

Confirm the exact installed version, compare it with the TYPO3 support roadmap, apply current patches and plan major upgrades before the support deadline becomes urgent.

If you are unsure which version your website is running or how to move safely to a supported branch, contact an experienced agency for TYPO3 for a version, extension and upgrade assessment.