Joomla vs Payload
Joomla is an open-source traditional CMS that you host yourself. Payload is an open-source headless CMS that you can host yourself or run on the vendor's cloud. The table below sets them side by side on 28 features. They get a different status on 18.
- Joomla Traditional · Open source · 12 of 28 built in
- Payload Headless · Open source · 13 of 28 built in
Sources checked: Joomla on 29 Sept 2026, Payload 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 TypeScript headless CMS and app framework that installs into a Next.js app and stores content in your own database. |
| 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 | Payload 3, MIT-licensed open-source core Version 3.90.2, released 23 Sept 2026 |
| Vendor | Open Source Matters, Inc. (Joomla project) joomla.org | Figma (acquired Payload in June 2025) payloadcms.com |
| Licence | Open source GPL-2.0-or-later | Open source MIT |
| Hosting | Self-hosting No vendor cloud The project's launch.joomla.org offers free hosted sites through a hosting partner. | Self-hosting Vendor cloud Payload Cloud is paused for new projects. Payload offers hosting to enterprise customers. |
| Built with | PHP | TypeScript, Node.js, Next.js, React |
| Database | MySQL, MariaDB, PostgreSQL | PostgreSQL, MongoDB, 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 to self-host. Enterprise licence, support and hosting on request. |
| 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 Collections, globals and fields are TypeScript config. 2 |
| 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 | Not available No schema builder in the admin. |
| 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 Blocks field. |
| 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 Field-level localization. |
| 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 Generates configured image sizes on upload, with crop and focal point. 11 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Built in Web Services API with token authentication. 10 | Built in |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Not available | Built in |
| 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 | Not available No webhook settings. Call URLs from afterChange hooks in code. 17 |
| 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. | Not available Runs inside your Next.js app. You build the pages. |
| 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 10 |
| 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 Scheduled publish and unpublish run through the jobs queue. 10 |
| 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 Opt-in per collection or global. 10 |
| 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 |
| 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 | Not available Payload lists the Enterprise Visual Editor as coming soon. 37 |
| 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 | Paid tier Enterprise publishing workflows. 39 |
| Content releases Editors group changes across several entries and publish them together as one release. | Not available | Not available |
| 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 Document locking only. Payload lists enterprise multi-player editing as coming soon. 12320 |
| 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 | Limited Roles are access-control functions written in code. No role editor in the admin. 18 |
| 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 Field-level access functions. 18 |
| 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 | Paid tier Enterprise licence, SAML and OAuth 2.0. 35 |
| 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 | Paid tier Enterprise audit logs. 6 |
| 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 | Plugin or add-on Official multi-tenant plugin. 15 |
| 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 Custom React components, views and fields. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Joomla Extensions Directory, the JED. 14 | Limited Docs list official plugins. Community plugin directories are third-party. 13 |
| 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 | Plugin or add-on Official Form Builder plugin. 16 |
| 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 Any auth-enabled collection can hold site users. |
| 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 | Paid tier Enterprise AI writing assistant. Payload lists AI translation and image generation as coming soon. 8 |
| 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 | Plugin or add-on Official open-source MCP plugin. 14 |
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
Payload sources
Checked 29 Sept 2026. Payload 3, MIT-licensed open-source core.
- payload on the npm registry
- Get started with Payload
- Payload for Enterprise
- Payload Cloud update: Payload has joined Figma
- Payload enterprise SSO
- Payload enterprise audit logs
- Payload Visual Editor
- Payload enterprise AI
- Payload publishing workflows
- Payload docs: Drafts
- Payload docs: Uploads
- Payload docs: Document locking
- Payload docs: Plugins
- Payload docs: MCP plugin
- Payload docs: Multi-tenant plugin
- Payload docs: Form Builder plugin
- GitHub discussion: Webhooks?
- Payload docs: Access control
- Figma blog: Welcoming Payload to the Figma team
- Payload multi-player editing
Considering more platforms? Compare Joomla and Payload with the rest of your shortlist in the CMS comparison tool.
Where they differ
Joomla and Payload get a different status on 18 of the 28 features and the same status on 10. Joomla has 12 built in on its baseline edition, Payload has 13. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
- Vendor cloud
- Joomla has no vendor-run cloud. Payload has a vendor-run cloud.
Built in on Joomla, a different answer on Payload 5
- Renders the website Joomla: Built in. Payload: Not available.
- Approval workflows Joomla: Built in. Payload: Paid tier.
- Custom roles Joomla: Built in. Payload: Limited.
- Audit log Joomla: Built in. Payload: Paid tier.
- Plugin marketplace Joomla: Built in. Payload: Limited.
Built in on Payload, a different answer on Joomla 6
- Content model in code Joomla: Not available. Payload: Built in.
- Reusable blocks Joomla: Limited. Payload: Built in.
- Image transformations Joomla: Limited. Payload: Built in.
- GraphQL API Joomla: Not available. Payload: Built in.
- Drafts Joomla: Limited. Payload: Built in.
- Preview Joomla: Limited. Payload: Built in.
Built in on neither, with different answers 7
- Content model in the UI Joomla: Limited. Payload: Not available.
- Visual editing Joomla: Limited. Payload: Not available.
- Single sign-on Joomla: Plugin or add-on. Payload: Paid tier.
- Multiple sites Joomla: Not available. Payload: Plugin or add-on.
- Form builder Joomla: Limited. Payload: Plugin or add-on.
- AI writing assistant Joomla: Not available. Payload: Paid tier.
- Official MCP server Joomla: Not available. Payload: 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 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 TYPO3
- Joomla vs Umbraco
- Joomla vs Wagtail
- Joomla vs Webflow
- Joomla vs Wix
- Joomla vs WordPress
- Joomla vs Xperience by Kentico
Payload against other platforms
- Adobe Experience Manager vs Payload
- Contentful vs Payload
- Contentstack vs Payload
- CoreMedia Content Cloud vs Payload
- Craft CMS vs Payload
- DatoCMS vs Payload
- Decap CMS vs Payload
- Directus vs Payload
- Drupal vs Payload
- EmDash vs Payload
- FirstSpirit vs Payload
- Framer vs Payload
- Ghost vs Payload
- HubSpot CMS vs Payload
- Hygraph vs Payload
- Instatic vs Payload
- Keystone vs Payload
- Kirby vs Payload
- Liferay DXP vs Payload
- Optimizely CMS vs Payload
- Prismic vs Payload
- Progress Sitefinity vs Payload
- Sanity vs Payload
- Sitecore vs Payload
- Squarespace vs Payload
- Statamic vs Payload
- Storyblok vs Payload
- Strapi vs Payload
- TYPO3 vs Payload
- Umbraco vs Payload
- Wagtail vs Payload
- Webflow vs Payload
- Wix vs Payload
- WordPress vs Payload
- Xperience by Kentico vs Payload
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.