TYPO3 requires a web server, PHP and a database system.
- TYPO3 requires a web server which can run PHP (e.g. Apache, Nginx or IIS). If you use an Apache web server, some module (e.g. mod_rewrite) must be activated. See Web Server Environment for details.
- TYPO3 10 requires PHP >= 7.2 <= 7.4 (Mac users: see warning at the end of this document). For PHP, several PHP extensions are necessary, others recommended. You possibly want to adjust the memory limit. See PHP Environment.
- TYPO3 can be used with a great many database systems (e.g. MySQL >= 5 <= 5.7, PostgreSQL, Microsoft SQL Server, SQLite or MariaDB >= 10 <= 10.3). See Database Environment on this page for details.
- If you want TYPO3 to automatically carry out image processing – for example scaling or cropping – you will need GraphicsMagick (version 1.3 or newer) or ImageMagick (version 6 or newer) installed on the server. (GraphicsMagick should be preferred.)
For an overview see also get.typo3.org.
Should you encounter problems, the “Troubleshooting” chapter will help.
TYPO3 works with database management systems in the above mentioned versions. The InnoDB engine is required to be enabled in MySQL.
Required Database Privileges¶
The database user needs at least the following privileges on the TYPO3 database:
- SELECT, INSERT, UPDATE, DELETE
- CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES
It is recommended to also grant the following privileges:
- CREATE VIEW, SHOW VIEW
- EXECUTE, CREATE ROUTINE, ALTER ROUTINE
Web Server Environment¶
- Make sure AllowOverride
in the webserver configuration includes “Indexes” and “FileInfo” if you use Apache as
webserver and override the default configuration with
.htaccess(as done by default).
- Enable Apache modules (see Enable mod_rewrite in the Troubleshooting
section). The following modules are used by the default
- Block access to vcs directories (strongly recommended for security reasons).
- Block access to specific files and directories (strongly recommended for security reasons).
- Used for disabling directory listings (strongly recommended for security reasons).
- Used for compression, better performance.
- Adds HTTP headers for browser caching and better performance
- Used with mod_deflate. For Apache versions below
version 2.3.7 you don’t need to enable
- Used in combination with
- Enable human readable urls.
- Also used with
If the modules are not active, the corresponding directives in
not be activated (due to the
<IfModule conditions). This leaves you with a system,
which is less secure, slower and / or where some things will simply not work
(e.g. URL rewriting due to missing
<IfModule> directives in the default
for more clues about which modules are used for what purpose. Not all used modules
may have directives in the .htaccess file so do not necessarily expect
to contain a complete list of modules.
- During the installation process (first install) the default
.htaccessfile is copied to the document root folder of the project, if the file does not exist already.
Microsoft Internet Information Services (IIS)¶
- During the installation process (first install) the default IIS web config file is copied to the document root folder of the project, if the file does not exist already.
- Default IIS web config file with rewrite rules can be found in
- NGINX web server does not support any static file like htaccess in the document root by default. The NGINX configuration has to be setup manually.
- Examples of NGINX vHost config files with rewrite rules can be found in TYPO3 Forge. Provide a Nginx server configuration.
- memory_limit set to at least 256M recommended
- max_execution_time set to at least 30 (240 seconds recommended)
- max_input_vars set to at least 1500
PHP Required Extensions¶
Your PHP needs to support the following extensions. Install will check if these are available.
- These are usually part of the standard PHP package on most distributions:
- pcre >= 8.38 (Mac users: see warning a the end of this document)
- These might have to be installed separately:
- mysqli (if you use MySQL, MariaDB as DBMS)
- postgresql (if you use PostgreSQL as DBMS)
- sqlsrv (if you use SQL Server as DBMS)
- sqlite (if you use SQLite as DBMS)
With PHP 7.3 in combination with macOS 10.13.6 (and probably also 10.14 - unconfirmed) pcre causes problems with brew as well as native or MAMP installations. It is recommended to use PHP 7.2. More information can be found here: