Getting ready: environment and prerequisites
Before you start configuring TYPO3, make sure your server environment meets the requirements. TYPO3 runs best on php supported versions (check the release documentation for the exact version you need), and requires common PHP extensions like pdo_mysql (or pdo_pgsql), fileinfo, intl, mbstring, xml, openssl and gd or imagick. You will also need composer for a modern installation workflow, a supported database (mysql/MariaDB or PostgreSQL), and a web server such as apache or nginx. Decide whether the project will use the public/ document root (recommended for composer installs). Prepare file system access (fileadmin/, typo3conf/, var/, public/ or web/) and ensure proper ownership and permissions are set so TYPO3 can write caches and upload files.
Install TYPO3
Composer-based installation is the recommended approach because it makes updates and dependency management more predictable. From your project folder you can run a command like the example below (replace the version constraint as needed). If you prefer a non-composer package, download the official distribution ZIP or tarball and extract it to your webroot.
composer create-project typo3/cms-base-distribution:^12 my-typo3-site
cd my-typo3-site
composer installAfter files are in place, configure your web server so the document root points to public/ (or web/ in some setups). For Apache, check that .htaccess is enabled and RewriteEngine is on; for nginx use the official server configuration examples. Create an empty database for TYPO3, and make sure the database user has permissions to create and alter tables.
First run: the Install Tool and initial configuration
Open the backend installer in your browser: /typo3/install.php. The Install Tool walks you through environment checks, database setup, encryption keys and creating an admin user. In the database section, supply host, database, user and password. After saving, the system will run database schema updates if required. Create a strong admin username and password,keep this credential safe and restrict access to the Install Tool once setup is complete.
Important Install Tool steps
- Check system environment and required PHP extensions.
- Configure database connection and run the database compare tool if prompted.
- Create the initial backend admin user (or use cli to create one).
- Save the LocalConfiguration.php and lock the Install Tool if your site is in production.
Configure the site: Sites module and routing
From TYPO3 v9 onward, the Sites module centralizes domain, base url, language and routing configuration. create a site configuration for each domain you serve. Define the base URL, the root page ID, and the languages you will publish. Route enhancers are a powerful YAML-based mechanism to map URL patterns to parameters for plugins and content elements; they replace older URL extensions. A minimal site configuration ensures correct link generation, language handling and canonical urls.
# Example: config/sites/example.com/config.yaml
rootPageId: 1
base: '
languages:
- title: English
enabled: true
languageId: 0
base: /
errorHandling: { 404: '/404' }Add route enhancers under the site configuration when you use plugins (for instance news listing/detail). Clear caches after changing site config so routing updates take effect.
TypoScript and templates: make the frontend work
TypoScript is the configuration language that tells TYPO3 how to render pages. Start by creating a root page (site root) in the page tree, then create a Template record on that page. Include static templates such as “Fluid Styled Content” and any extension static templates you need. Use the TypoScript Constants and Setup fields to define your main page object, include css/js through page.includeCSS or asset management, and configure meta tags for SEO.
# Minimal TypoScript Setup (Template -> Setup)
page = PAGE
page {
typeNum = 0
10 = FLUIDTEMPLATE
10.templateName = Default
10.templateRootPaths.0 = EXT:sitepackage/Resources/Private/Templates/
includeJSFooterlibs {
jquery =
}
}If you use a site package extension (recommended for custom themes), register your templates, partials and layouts in its ext_localconf and TypoScript setup. Keep TypoScript organized: constants for values editors can change, and setup for rendering rules.
Page tree, backend layouts and content elements
Build a clear page tree that reflects the site structure. For each page, set the correct page type and language. Backend layouts let editors choose a grid structure when creating content. Configure these layouts using backend layout records or via TypoScript; then assign them to pages. Teach editors to create content elements using the standard content types or custom plugins from installed extensions. Use filemounts to control where editors can upload assets (fileadmin/ or storage records), and configure storage drivers if you use external storage like S3.
Install and configure extensions
Extend functionality with extensions installed through Composer (preferred) or the Extension Manager. For example, add a news system, SEO meta management, or a site package. A Composer installation example:
composer require friendsoftypo3/news
composer require sitepackage/vendor-sitepackageAfter installing, activate and configure the extension in the Extension Manager and include any required static TypoScript templates. For modern extensions, follow their README for required site config or route enhancers. Remember to clear caches and, if the extension needs database tables, to run the Database Compare tool in the Install Tool to apply schema changes.
Security and performance hardening
Lock down the Install Tool after setup and use https for all domains. Limit database user permissions to what TYPO3 needs, and store secrets securely. Set file and directory permissions so the web server user can write to var/, fileadmin/, and typo3temp/ but not to sensitive system files. In the TYPO3 backend, configure system environment settings (e.g., backward compatibility and debug levels) for production. For performance, enable production caches and consider using caching backends like Redis for cache and session storage, configure HTTP caching with a reverse proxy (Varnish) or use HTTP cache headers, and use asset compression and bundling to reduce payload size.
Deploying and maintaining a live site
Use Composer to manage code dependencies and store configuration in version control. Keep LocalConfiguration.php out of public repositories; prefer environment-specific overrides through AdditionalConfiguration.php or environment variables. For updates, run composer update, then apply database migrations via the Install Tool or CLI upgrade wizards, and test on staging before production. Schedule regular backups of the database and fileadmin, and use the Scheduler module to run recurring maintenance tasks such as indexing or cleanup jobs.
Tips that save time
Set up a local development environment that mirrors production (same php version, extensions and a similar database). Use a site package to centralize templates and TypoScript, and document conventions for editors to reduce support overhead. Automate repetitive tasks,deployment, cache clearing, and database backups,so you can focus on content and feature development rather than ad-hoc maintenance.
Concise summary
Configure TYPO3 by preparing a compatible server environment, installing via Composer or distribution package, running the Install Tool to create the database and admin user, and setting up site configuration with the Sites module. Create a TypoScript template and a site package for layout and templates, install necessary extensions, and prepare backend layouts and filemounts for editors. Lock down security, enable caching and performance features, and maintain the site using Composer and upgrade tools. Test changes on staging and use automated deployment and backups for safe operations.
FAQs
How do I create a backend admin user if I lost access?
If you cannot log in, use the Install Tool (typo3/install.php) to create or reset a backend user, or run the TYPO3 CLI command (typo3cms) if available in your installation: use the install tool’s “Create Admin User” or the backend user management in the Install Tool. For CLI, a typical command pattern is vendor/bin/typo3 user:add depending on your version or extensions; check your TYPO3 version docs for the exact command.
How do I configure pretty URLs (no index.php)?
Pretty URLs are handled through the Sites configuration and route enhancers. Ensure your web server rewrite rules are active (Apache .htaccess or Nginx config) and that the site base and root page are set in the Sites module. Define route enhancers for plugin parameters so detail pages resolve to human-readable paths.
How can I add a second language to the site?
Add the new language in the Sites module under the site configuration for the domain: set languageId, ISO code and base path. Then in the page tree, create translations for pages and content elements, and configure TypoScript meta tags and hreflang if needed. Test URLs and fallback behavior.
What is the recommended way to install extensions?
Use Composer to require extensions where possible; this keeps dependencies and versioning consistent. After composer require, clear caches, install database updates via the Install Tool, and include any static TypoScript the extension requires.
How do I update TYPO3 safely?
Update through Composer: update your composer.json constraints, run composer update, then go through the Upgrade/Install Tool and follow the upgrade wizards in the backend to apply database changes. Test the entire update on a staging environment and review extension compatibility before applying updates to production.
