Now booking enterprise content platform builds for 2026. Contact us

CMS comparison Framer vs TYPO3

Framer vs TYPO3

Framer is a closed-source site builder that runs on the vendor's cloud. 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 16.

  • Framer Site builder · Closed source · 14 of 28 built in
  • TYPO3 Traditional · Open source · 20 of 28 built in

Sources checked: Framer 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

Built inPaid tierPlugin or add-onLimitedNot available
Framer vs TYPO3 feature comparison. Columns are the two platforms. Rows are features, grouped by area.
Platform
Framer Site builder
TYPO3 Traditional
Overview
What it is Hosted visual site builder with a CMS, hosting and AI agents. Designers build pages on a canvas. Run by Framer.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. Framer 3.0 site plans, Free to Enterprise SaaS, continuously updated TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026
Vendor Framer B.V. framer.com TYPO3 Association (project); TYPO3 GmbH sells support and extended LTS typo3.org
Licence Closed source Proprietary Open source GPL-2.0-or-later
Hosting No self-hosting Vendor cloud A paid plan is required to connect a custom domain. Self-hosting No vendor cloud No vendor SaaS. TYPO3 agencies and hosts run managed installations.
Built with Hosted SaaS with React code componentsPHP, Symfony components, Fluid
Database Managed by FramerMySQL, MariaDB, PostgreSQL, SQLite
Pricing Public list prices only. Hosting and implementation are extra everywhere. Free to start Free plan. Basic $10, Pro $30 per site per month billed yearly. Extra editors $20 per month. 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 You build collections in the editor or sync them through the Plugin and Server APIs. 313 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. Built in 13 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. Built in Components with properties that content editors can change on-page. 14 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. Plugin or add-on Translation locales add-on, $20 per locale per month. One free locale to try. 117 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. Built in Generates 512 to 4096 px variants served through srcset. 8 Built in Server-side image processing with crop variants. 10
APIs and delivery
REST API A documented REST or JSON HTTP API returns content. Limited Server API in open beta, through the framer-api package over WebSocket. No plain REST. 23 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 Webhooks cover form submissions only. 10 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 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. Built in CMS items can stay in draft. 13 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. Not available No native scheduling. Third-party Marketplace plugins add it. 18 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 Version history and rollback of published versions. 67 Built in Record history with diff and undo.
Preview Editors can see unpublished content rendered as it will appear on the site before publishing. Built in 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. Built in Canvas editing and on-page editing of the live site. 14 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. Limited Editors review and merge Pro branches. Only Deploy permission publishes. No stages. 45 Built in Custom stages in Workspaces. 5
Content releases Editors group changes across several entries and publish them together as one release. Paid tier Branching on Pro groups changes and ships them in one merge. 15 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. Built in Free workspaces allow up to three editors. 1 Not available
Access and governance
Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. Limited Fixed roles plus Design, Content and Deploy permissions per project. No role builder. 4 Built in Backend user groups. 9
Field-level permissions Admins can restrict access to single fields, on top of content types and entries. Not available 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. Paid tier Enterprise. 116 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. Not available Not documented publicly. 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. Built in A workspace holds many site projects, each on its own plan. 4 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 Plugins add custom panels and tools to the editor. 11 Built in Backend modules and custom form elements.
Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. Built in Framer Marketplace. 12 Built in TYPO3 Extension Repository. 16
Form builder Editors can build and publish forms and collect submissions without code. Built in Native forms. Submissions can also go to a webhook. 10 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. Not available 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. Built in Agents write, rewrite and translate content. AI credits meter usage. 115 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 No MCP server. External Agents, in preview, link AI tools through a CLI and skills. 9 Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15

Considering more platforms? Compare Framer and TYPO3 with the rest of your shortlist in the CMS comparison tool.


Where they differ

Framer and TYPO3 get a different status on 16 of the 28 features and the same status on 12. Framer has 14 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.

Licence
Framer is closed source (Proprietary). TYPO3 is open source (GPL-2.0-or-later).
Self-hosting
Framer cannot be self-hosted. TYPO3 can be self-hosted.
Vendor cloud
Framer has a vendor-run cloud. TYPO3 has no vendor-run cloud.

Built in on Framer, a different answer on TYPO3 4

  • Content model in the UI Framer: Built in. TYPO3: Plugin or add-on.
  • Visual editing Framer: Built in. TYPO3: Plugin or add-on.
  • Real-time co-editing Framer: Built in. TYPO3: Not available.
  • AI writing assistant Framer: Built in. TYPO3: Not available.

Built in on TYPO3, a different answer on Framer 10

  • Content model in code Framer: Not available. TYPO3: Built in.
  • Localization Framer: Plugin or add-on. TYPO3: Built in.
  • Webhooks Framer: Not available. TYPO3: Built in.
  • Scheduled publishing Framer: Not available. TYPO3: Built in.
  • Approval workflows Framer: Limited. TYPO3: Built in.
  • Content releases Framer: Paid tier. TYPO3: Built in.
  • Custom roles Framer: Limited. TYPO3: Built in.
  • Field-level permissions Framer: Not available. TYPO3: Built in.
  • Audit log Framer: Not available. TYPO3: Built in.
  • Site member accounts Framer: Not available. TYPO3: Built in.

Built in on neither, with different answers 2

  • REST API Framer: Limited. TYPO3: Plugin or add-on.
  • Single sign-on Framer: Paid tier. TYPO3: Plugin or add-on.

More comparisons

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.