 | It has been suggested that this article besplit out into a new article titledNeos (content management). (Discuss)(March 2021) |
 | This articlecontainspromotional content. Please helpimprove it by removingpromotional language and inappropriateexternal links, and by adding encyclopedic text written from aneutral point of view.See ouradvice if the article is about you and read ourscam warning in case someone asks for money to edit this article.(April 2020) (Learn how and when to remove this message) |
| TYPO3 | |
|---|---|
 Logo of TYPO3 | |
 TYPO3 CMS 10.4 back end | |
| Original author | Kasper Skårhøj |
| Developer | TYPO3 Association |
| Initial release | 1998; 28 years ago (1998) |
| Stable release | 14.0.1[1]  / 2025-12-02; 2 months ago |
| Written in | PHP,SQL,JavaScript |
| Operating system | Windows,Linux,FreeBSD,macOS,OS/2 |
| Platform | IA-32,x86-64 |
| Size | 18.5MB |
| Available in | 51 languages |
| Type | Content management framework,content management system |
| License | GNU General Public License version 2 |
| Website | typo3 |
| Repository | |
TYPO3 is a webcontent management system (CMS) written in theprogramming languagePHP. It isfree and open-source software released under theGNU General Public License version 2.
TYPO3 is similar to other content management systems such asDrupal,Joomla!, andWordPress. It is used more widely in Europe than in other regions, with a larger market share in German-speaking countries, the Netherlands, and France.[2][3]
TYPO3 was acknowledged as aDigital Public Good by theDigital Public Goods Alliance in April of 2025.[4]
TYPO3 allows for the separate maintenance of code and content. It can beextended with new functions without writing any program code. TYPO3 supports publishing content in multiple languages due to its built-inlocalization system.
TYPO3 was initially authored by Kasper Skårhøj in 1997.[5] It is now developed by over 300 contributors under the lead of Benjamin Mack.[6]
Calculations from the TYPO3 Association show that it is currently used in more than 500,000 installations. The number of installations detected by the public website "CMS Crawler" was around 384,000 in February 2017.[3][7]
TYPO3 provides a base set of interfaces, functions and modules. Most functionality exceeding the base set can be implemented via the use of extensions. More than 5000 extensions are currently available for TYPO3 for download under theGNU General Public License from a repository called the TYPO3 Extension Repository, or TER.[8]
TYPO3 is able to run on most HTTP servers such asApache,Nginx andIIS on top ofLinux,Microsoft Windows,FreeBSD,macOS, andOS/2. It uses PHP 7.2 or newer[9] and any relational database supported by the TYPO3DBAL includingMySQL/MariaDB,PostgreSQL, andSQLite.[10] Some 3rd-party extensions – not using the database API – support MySQL as the only database engine. The system can be run on anyweb server with at least 256 MBRAM and aCPU appropriate for that RAM.
The back end can be displayed in any modern browser withJavaScript. There is no browser restriction for displaying user-oriented content generated by TYPO3. A developer setting up a website with TYPO3 would need to work intensively with theDomain-specific language Typoscript.[11]
Conceptually, TYPO3 consists of two parts: thefront end, visible to visitors, and the administrativeback end. The front end displays the web content. The back end is responsible for administration and managing content. The core functions of TYPO3 include user privileges and user roles, timed display control of content (show/hide content elements), a search function for static and dynamic content, search-engine friendly URLs, an automatic sitemap, multi-language capability for front and back ends, and more.
Like most modern CMS's, TYPO3 follows the policy ofseparation of content and layout: The website content is stored in a relational database, while the page templates are stored on the file system. Therefore, both can be managed and updated separately.
TYPO3 defines various basic types of content data. Standard content elements are described as text, text with media, images, (plain) HTML, video etc. Various added types of content elements can be handled usingextensions.
The fundamental content unit is a "page". Pages represent a URL in the front end and are organized hierarchically in the back end's page tree. Standard pages serve as "containers" for one or multiple content elements. There are several added special page types, including:
Internally, TYPO3 is managed by various PHP arrays. They contain all the information necessary to generate HTML code from the content stored in the database. This is achieved by a unique configuration language called Typoscript.
Designing and developing with TYPO3 is commonly based on the following elements, among others:
###MARKER###) and range markers, calledsubparts (e.g.,<!-- ###CONTENT### Start --> … <!-- ###CONTENT### End -->); that were replaced by various content elements or served as a sub template. This template system can still be found in older extensions or installations.Extensions are the cornerstone in the internal architecture of TYPO3. A feature that was introduced with version 3.5 in 2003 is theExtension Manager, a control center managing all TYPO3 extensions. The division between the TYPO3 core and the extensions is an important concept which determined the development of TYPO3 in the past years. Extensions[12] are designed in a way so they can supplement the core seamlessly. This means that a TYPO3 system will appear as aunit while actually being composed of thecore application and aset of extensions providing various features.[13]
They can be downloaded from the online repository (TER) directly from the back end, and are installed and updated with a few clicks. Every extension is identified by a unique extension key (for example,tt news). Also, developers can share new or modified extensions by uploading them to the repository.[8]
Generally, extensions are written in PHP. The full command set of PHP 5.3 can be used (regarded the system requirements of the specific TYPO3 version), but TYPO3 also provides several library classes for better efficiency: Best known and most used is the Pibase library class. With introduction of TYPO3 4.3 in 2009, Pibase has been replaced (or extended) by theExtbase library, which is a modern,model–view–controller (MVC) based development framework. To ensure backward compatibility, both libraries can be used in the same TYPO3 installation. Extbase is a backport of some features of FLOW3, renamedNeos Flow, a general web application framework.[14]
Several companies and organizations base their web or intranet sites on TYPO3. The majority are based in German-speaking countries, such as the state ofSaxony-Anhalt, the GermanGreen Party, the University of Lucerne (Switzerland), the University of Vienna (Austria) andTechnische Universität Berlin.[15] International organizations running one or more TYPO3 sites are:Airbus,Konica-Minolta,Leica Microsystems,Air France,Greenpeace, andMeda (Sweden).[16][17][18]
| Branch | Version [19] | Release date | Major changes |
|---|---|---|---|
| 3.x | |||
| Unsupported: 3.0 | 2001[citation needed] |
| |
| Unsupported: 3.2 | 17 May 2002 |
| |
| Unsupported: 3.3 | 3 June 2002 |
| |
| Unsupported: 3.5 | 18 February 2003 |
| |
| Unsupported: 3.6 | 30 April 2004 |
| |
| Unsupported: 3.7 | 24 September 2004 |
| |
| Unsupported: 3.8 | 23 May 2005 |
| |
| Unsupported: 3.8.1 | 14 November 2005 |
| |
| 4.x | Unsupported: 4.0 | 7 April 2006 |
|
| Unsupported: 4.1 | 6 March 2007 | ||
| Unsupported: 4.2 | 24 May 2008 |
| |
| Unsupported: 4.3 | 30 November 2009 |
| |
| Unsupported: 4.4 | 22 June 2010 |
| |
| Unsupported: 4.5 LTS | 26 January 2011 |
| |
| Unsupported: 4.6 | 25 October 2011 | ||
| Unsupported: 4.7 | 24 April 2012 | ||
| 6.x | Unsupported: 6.0 | 27 November 2012[52] | |
| Unsupported: 6.1 | 30 April 2013 | ||
| Unsupported: 6.2 LTS | 25 March 2014[58] |
| |
| 7.x | Unsupported: 7.0 | 2 December 2014 |
|
| Unsupported: 7.4 | 4 August 2015 |
| |
| Unsupported: 7.5 | 29 September 2015 |
| |
| Unsupported: 7.6 LTS | 10 November 2015 |
| |
| 8.x | Unsupported: 8.0 | 22 March 2016 |
|
| Unsupported: 8.1 | 3 May 2016 |
| |
| Unsupported: 8.2 | 5 July 2016 |
| |
| Unsupported: 8.3 | 30 August 2016 |
| |
| Unsupported: 8.4 | 18 October 2016 |
| |
| Unsupported: 8.5 | 20 December 2016 |
| |
| Unsupported: 8.6 | 14 February 2017 |
| |
| Unsupported: 8.7 LTS | 4 April 2017 |
| |
| 9.x | Unsupported: 9.0 | 12 December 2017 |
|
| Unsupported: 9.1 | 30 January 2018 |
| |
| Unsupported: 9.2 | 10 April 2018 |
| |
| Unsupported: 9.3 | 12 June 2018 |
| |
| Unsupported: 9.4 | 4 September 2018 |
| |
| Unsupported: 9.5 LTS | 2 October 2018 |
| |
| 10.x | Unsupported: 10.0 | 23 July 2019 | |
| Unsupported: 10.1 | 1 October 2019 | ||
| Unsupported: 10.2 | 3 December 2019 | ||
| Unsupported: 10.3 | 25 February 2020 | ||
| Supported: 10.4 LTS | 21 April 2020 |
| |
| 11.x | Unsupported: 11.0 | 22 December 2020 | Support PHP 7.4 and 8.0 / MySQL 5.7+ / MariaDB / Postgres / SQLite |
| Unsupported: 11.1 | 23 February 2021 | ||
| Unsupported: 11.2 | 4 May 2021 | ||
| Unsupported: 11.3 | 13 July 2021 | ||
| Unsupported: 11.4 | 7 September 2021 | ||
| Supported: 11.5 | 5 October 2021 | Long Term Support Release (LTS), fully supported for three years until October 2024[71] | |
| 12.x | Unsupported: 12.0 | 4 October 2022 | First release of TYPO3 12.0[72] |
| Unsupported: 12.1 | 6 December 2022 | Interoperability with third-party systems[73] | |
| Unsupported: 12.2 | 7 February 2023 | Improved Back-end UI[74] | |
| Unsupported: 12.3 | 28 March 2023 | Last-Minute Features[75] | |
| Supported: 12.4 | 25 April 2023 | Long Term Support Version with 3 years of official security and maintenance support[76] | |
| 13.x | Unsupported: 13.0 | 30 January 2024 | First release of TYPO3 13.0 with breaking changes and new system requirements[77] |
| Unsupported: 13.1 | 23 April 2024 | Reusable components for creating new sites | |
| Unsupported: 13.2 | 2 July 2024 | Content blocks and new APIs for integrations | |
| Unsupported: 13.3 | 17 September 2024 | Feature freeze[78] | |
| Latest version:13.4 | 15 October 2024 | LTS release |
A completely rewritten version (code-named "Phoenix") was originally planned as TYPO3version 5.0. While working on this new release and analyzing the 10-year history and complexity of TYPO3 v4, the TYPO3 community decided to branch out version 5 as a completely separate product, one that wouldn't replace version 4 in the near future and as such needed to have its own name. Published as FLOW3, now renamedNeos Flow, it along with various other packages then served as the basis for the start of development of project Phoenix.[79]
In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos".[80] With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012.[81][82] In May 2015 the TYPO3 Association and the Neos team decided to go separate ways, with TYPO3 CMS remaining the only CMS product endorsed by the Association and the Neos team publishing Neos as a stand-alone CMS without any connection to the TYPO3 world.[83]
In January 2017, Neos 3.0 has been published, along with a new version of Flow framework and a name change of its configuration language fromTypoScript2 toFusion.[84]
{{cite web}}: CS1 maint: numeric names: authors list (link)