Joomla vs TYPO3
Joomla is an open-source traditional CMS that you host yourself. TYPO3 is an open-source traditional CMS that you host yourself. The table below sets them side by side on 28 features. They get a different status on 12.
- Joomla Traditional · Open source · 12 of 28 built in
- TYPO3 Traditional · Open source · 20 of 28 built in
Sources checked: Joomla on 29 Sept 2026, TYPO3 on 29 Sept 2026. Plans and releases can change after those dates.
WAYF is an official Payload partner and top contributor. Every platform in the table is classified by the same published definitions, and each answer lists the vendor page it came from.
Feature comparison
| Platform | | |
|---|---|---|
| Overview | ||
| What it is | Open-source PHP CMS built around articles, custom fields, core multilingual support and group-based access control. Self-hosted. | Open-source PHP CMS for multi-site, multilingual websites, with workspaces and granular backend permissions. Self-hosted, often run by agencies. |
| Edition compared The product and release each column describes. | Joomla 6.1, open source. Joomla 5.4 is still maintained. Version 6.1.3, released 18 Aug 2026 | TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026 |
| Vendor | Open Source Matters, Inc. (Joomla project) joomla.org | TYPO3 Association (project); TYPO3 GmbH sells support and extended LTS typo3.org |
| Licence | Open source GPL-2.0-or-later | Open source GPL-2.0-or-later |
| Hosting | Self-hosting No vendor cloud The project's launch.joomla.org offers free hosted sites through a hosting partner. | Self-hosting No vendor cloud No vendor SaaS. TYPO3 agencies and hosts run managed installations. |
| Built with | PHP | PHP, Symfony components, Fluid |
| Database | MySQL, MariaDB, PostgreSQL | MySQL, MariaDB, PostgreSQL, SQLite |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | Free to start Free and open source. Hosting and commercial extensions cost extra. | Free to start Free and open source. Commercial support and extended LTS are sold separately. |
| Content modelling | ||
| Content model in code You define content types in files in your repository, review them like any other code and apply them from there. Imperative migration scripts alone count as limited. | Not available Fields live in the database. A new content type means writing a component. | Built in TCA in PHP. The Content Blocks extension adds YAML definitions. 11 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Limited Custom fields on articles, contacts, users and categories. No new content types. 5 | Plugin or add-on Mask extension builds content elements in the backend. 12 |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Limited Modules placed in template positions. No page-level block editor in core. 4 | Built in Content elements on pages, reordered by drag and drop. |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Built in Per-item language with multilingual associations. 7 | Built in Page and record translations. Guided translation wizard in v14. 2 |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Limited Manual crop and resize in Media. No generated sizes or URL transforms. 9 | Built in Server-side image processing with crop variants. 10 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Built in Web Services API with token authentication. 10 | Plugin or add-on EXT:headless outputs pages as JSON. Core has no content API. 13 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Not available | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Not available None in core. Only small third-party extensions. 19 | Built in Webhooks system extension, in core since v12. 6 |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Built in Template system, with Cassiopeia as the default. | Built in Fluid templates. Camino default theme in v14. 2 |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Limited Unpublished items only. Saving a published article updates it live. 8 | Built in Via the Workspaces system extension. 5 |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Built in Start and finish publishing dates. 8 | Built in Start and stop dates on pages and content. |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Built in Compare and restore. Includes custom field values since 6.0. 34 | Built in Record history with diff and undo. |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Limited Backend Preview shows the last saved version of an article. 8 | Built in Workspace preview links. 5 |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Limited Front-end editing opens the article or module form on the site. 4 | Plugin or add-on Visual Editor extension from Friends of TYPO3. TYPO3 plans core support for v15. 3 |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Built in Workflows component, off by default. Visual workflow editor since 6.1. 112 | Built in Custom stages in Workspaces. 5 |
| Content releases Editors group changes across several entries and publish them together as one release. | Not available | Built in Workspaces publish staged changes together. 5 |
| Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. | Not available Joomla checks out and locks an item while someone edits it. | Not available |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in User groups, access levels and ACL. 4 | Built in Backend user groups. 9 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Built in Per-field Edit Custom Field Value permission. 6 | Built in Exclude fields per backend group. 9 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Plugin or add-on SAML or OIDC extensions from the JED. Core authenticates against LDAP only. 1314 | Plugin or add-on OpenID Connect extensions such as causal/oidc. 14 |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Built in User Actions Log. 12 | Built in Log module records backend changes by user. |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Not available One site per install. Third-party multisite extensions only. 15 | Built in Several site configurations in one installation. |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in Components, modules, plugins and custom field types. | Built in Backend modules and custom form elements. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Joomla Extensions Directory, the JED. 14 | Built in TYPO3 Extension Repository. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Limited Contact forms accept custom fields. Core emails submissions and does not store them. 20 | Built in Form Framework with a backend form editor. 7 |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Built in Front-end registration and login. 4 | Built in Frontend users and the felogin extension. 8 |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Not available No first-party AI. Third-party extensions such as 4AI. 18 | Not available Core ships AI integration points only. Third-party extensions such as AI Suite. 417 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Not available Third-party only, e.g. Onepoint's MCP Server for Joomla. 16 | Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15 |
Joomla sources
Checked 29 Sept 2026. Joomla 6.1, open source. Joomla 5.4 is still maintained..
- Joomla Downloads: latest release
- Joomla 6.1 is here
- What's new in Joomla 6.0?
- Joomla Core Features
- Fields (user manual)
- Help5.x: Fields: Edit (permissions)
- Multilingual Associations
- Article: Preview
- Media: Image Crop Resize Rotate
- Web Services (programmers documentation)
- Workflows (user manual)
- User Actions Log
- LDAP authentication
- Joomla Extensions Directory
- JED: Multiple Sites category
- MCP Server for Joomla (JED)
- Free Hosting (user manual)
- 4AI (JED)
- Content Sharing - Webhooks (JED)
- Adding Custom Fields to the Joomla Contact Form
TYPO3 sources
Checked 29 Sept 2026. TYPO3 v14 LTS, version 14.3, open source.
- get.typo3.org: latest TYPO3 14 release
- TYPO3 Releases v14 LTS (press release)
- Changing the Playing Field: Visual Editing in TYPO3 v14
- TYPO3 v14: Building a System for Community-Driven AI Integrations
- TYPO3 Workspaces documentation
- TYPO3 Webhooks documentation
- TYPO3 Form documentation
- TYPO3 Frontend Login documentation
- Access control options (TYPO3 Explained)
- Crop variants for images (TYPO3 Explained)
- TYPO3 Content Blocks documentation
- Mask extension (TER)
- EXT:headless documentation
- OpenID Connect integration for TYPO3
- hauptsacheNet/typo3-mcp-server on GitHub
- How to find extensions (Getting Started)
- AI Suite extension (TER)
Considering more platforms? Compare Joomla and TYPO3 with the rest of your shortlist in the CMS comparison tool.
Where they differ
Joomla and TYPO3 get a different status on 12 of the 28 features and the same status on 16. Joomla has 12 built in on its baseline edition, TYPO3 has 20. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
Built in on Joomla, a different answer on TYPO3 1
- REST API Joomla: Built in. TYPO3: Plugin or add-on.
Built in on TYPO3, a different answer on Joomla 9
- Content model in code Joomla: Not available. TYPO3: Built in.
- Reusable blocks Joomla: Limited. TYPO3: Built in.
- Image transformations Joomla: Limited. TYPO3: Built in.
- Webhooks Joomla: Not available. TYPO3: Built in.
- Drafts Joomla: Limited. TYPO3: Built in.
- Preview Joomla: Limited. TYPO3: Built in.
- Content releases Joomla: Not available. TYPO3: Built in.
- Multiple sites Joomla: Not available. TYPO3: Built in.
- Form builder Joomla: Limited. TYPO3: Built in.
Built in on neither, with different answers 2
- Content model in the UI Joomla: Limited. TYPO3: Plugin or add-on.
- Visual editing Joomla: Limited. TYPO3: Plugin or add-on.
More comparisons
Joomla against other platforms
- Adobe Experience Manager vs Joomla
- Contentful vs Joomla
- Contentstack vs Joomla
- CoreMedia Content Cloud vs Joomla
- Craft CMS vs Joomla
- DatoCMS vs Joomla
- Decap CMS vs Joomla
- Directus vs Joomla
- Drupal vs Joomla
- EmDash vs Joomla
- FirstSpirit vs Joomla
- Framer vs Joomla
- Ghost vs Joomla
- HubSpot CMS vs Joomla
- Hygraph vs Joomla
- Instatic vs Joomla
- Joomla vs Keystone
- Joomla vs Kirby
- Joomla vs Liferay DXP
- Joomla vs Optimizely CMS
- Joomla vs Payload
- Joomla vs Prismic
- Joomla vs Progress Sitefinity
- Joomla vs Sanity
- Joomla vs Sitecore
- Joomla vs Squarespace
- Joomla vs Statamic
- Joomla vs Storyblok
- Joomla vs Strapi
- Joomla vs Umbraco
- Joomla vs Wagtail
- Joomla vs Webflow
- Joomla vs Wix
- Joomla vs WordPress
- Joomla vs Xperience by Kentico
TYPO3 against other platforms
- Adobe Experience Manager vs TYPO3
- Contentful vs TYPO3
- Contentstack vs TYPO3
- CoreMedia Content Cloud vs TYPO3
- Craft CMS vs TYPO3
- DatoCMS vs TYPO3
- Decap CMS vs TYPO3
- Directus vs TYPO3
- Drupal vs TYPO3
- EmDash vs TYPO3
- FirstSpirit vs TYPO3
- Framer vs TYPO3
- Ghost vs TYPO3
- HubSpot CMS vs TYPO3
- Hygraph vs TYPO3
- Instatic vs TYPO3
- Keystone vs TYPO3
- Kirby vs TYPO3
- Liferay DXP vs TYPO3
- Optimizely CMS vs TYPO3
- TYPO3 vs Payload
- Prismic vs TYPO3
- Progress Sitefinity vs TYPO3
- Sanity vs TYPO3
- Sitecore vs TYPO3
- Squarespace vs TYPO3
- Statamic vs TYPO3
- Storyblok vs TYPO3
- Strapi vs TYPO3
- TYPO3 vs Umbraco
- TYPO3 vs Wagtail
- TYPO3 vs Webflow
- TYPO3 vs Wix
- TYPO3 vs WordPress
- Xperience by Kentico vs TYPO3
Open the CMS comparison tool to put up to six platforms in one table.
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.