TYPO3 installation overview
TYPO3 can be installed in two ways:
Composer-based installation
Composer-based setups are common in professional environments with development teams. Extensions are installed via Packagist (not from the TYPO3 Extension Repository (TER)), providing more flexibility in dependency management, better integration with version control, and easier environment automation. It is ideal for advanced projects or team-based workflows.
Classic installation
This method includes access to the TYPO3 Extension Repository (TER) via a regular backend module. It is ideal for managed hosting, automated updates by the hosting provider, and simpler setups. Also well-suited for beginners due to GUI-based extension handling.
Switching to Composer later is possible, but takes effort and means restructuring the project.
Both methods are fully supported and recommended depending on your project needs and environment.
As of now, there is no official plan to deprecate the classic installation method.
System requirements
System requirements for the host operating system, including its web server and database and how they should be configured prior to installation.
Tuning TYPO3
This chapter contains information on how to configure and optimize the infrastructure running TYPO3.
TYPO3 Release Integrity
Every release of TYPO3 is electronically signed by the TYPO3 release team. In addition, every TYPO3 package also contains a unique file hash that can be used to ensure file integrity when downloading the release. This guide details how these signatures can be checked and how file hashes can be compared.