TYPO3 v10 has reached end-of-life as of April 30th 2023 and is no longer being maintained. Use the version switcher on the top left of this page to select documentation for a supported version of TYPO3.

Need more time before upgrading? You can purchase Extended Long Term Support (ELTS) for TYPO3 v10 here: TYPO3 ELTS.

Directory Structure

By default a TYPO3 installation consists of a structure of main directories within the web server document root. You will find this structure to be almost always like that. Depending on the installation variant you choose however, this may be slightly different. For instance, it is possible to have all PHP files except the entry points index.php within the composer managed vendor/ directory, outside of the document root. This setup however did not fully settle yet, and is not documented here in detail. So, if you look at "casual" TYPO3 installations, you will almost always find the directory structure as outlined below.

Also see Environment for further information, especially how to retrieve the paths within PHP code.




This is a directory in which editors store files. Typically images, PDFs or video files appear in this directory and/or its subdirectories.

Note this is only the default editor's file storage. This directory is handled via the FAL API internally, there may be further storage locations configured outside of fileadmin/, even pointing to different servers or using 3rd party digital asset management systems.


Note this directory is meant for editors! Integrators should not locate frontend website layout related files in here: Storing HTML templates, logos, Css and similar files used to build the website layout in here is considered bad practice. Integrators should locate and ship these files within a project specific extension.


TYPO3 Backend directory. This directory contains most of the files coming with the TYPO3 Core. The files are arranged logically in the different system extensions in the sysext/ directory, according to the application area of the particular file. For example, the "frontend" extension amongst other things contains the "TypoScript library", the code for generating the Frontend website. In each system extension the PHP files are located in the folder Classes/. See extension files locations for more information on how single extensions are structured.

getConfigPath() either typo3conf/ or config/

TYPO3 configuration directory. This directory contains installation wide configuration.

The most important file within this folder is LocalConfiguration.php. This one contains local settings of the main global PHP array $GLOBALS['TYPO3_CONF_VARS], crucial settings like database connect credentials are in here. The file is managed by the Install Tool and the Extension Manager and the content should not be managed manually since Extension Manager or Install Tool may override manually changed settings again.

The file LocalConfiguration.php can be enriched by AdditionalConfiguration.php which is never touched by TYPO3 internal management tools. Be aware that having settings within AdditionalConfiguration.php may prevent the system from doing automatic upgrades and should be used with care and only if you know what you are doing.


Directory for local TYPO3 extensions. Each subdirectory contains one extension.

getLabelsPath() either typo3conf/l10n or var/labels

Directory for extension localisations. Contains all downloaded translation files.


Directory for temporary files. It contains subdirectories (see below) for temporary files of extensions and TYPO3 components.


Although it is a most common understanding in the TYPO3 world that typo3temp/ can be removed at any time, it is considered bad practice to remove the whole folder. Developers should selectively remove folders relevant to the changes made.

  • Directory



    Directory for temporary files that should be public available (e.g. generated images).

  • Directory



    Directory for temporary files that contains private files (e.g. cached Fluid templates) and should not be publicly available. See also Environment-configuring-paths for a more detailed description.