[Head-to-head comparison]

Contentful vs Strapi

Contentful vs Strapi for structured content, compared across editing, modeling, localization, governance, hosting, APIs, cost and migration.

Kalle Bertell

By Kalle Bertell

Direct answer

Choose Contentful when structured entries, field-level locales and a vendor-operated content API are the requirement. Choose Strapi when the team will own a Node.js CMS, either on its own servers or on Strapi Cloud. Contentful’s visual canvas needs Studio. Strapi’s live preview starts on Growth, while a preview URL is on Community. The split is who operates the CMS, and which governance features are already on the license.

Choose Contentful when

  • Vendor-operated content API

    Contentful runs the editor, APIs and CDN. Your team keeps the website and does not patch a CMS runtime.

  • Field locales on one entry

    Localized fields sit on the entry. Separate entries or spaces remain available when markets publish independently.

  • Published assurance reports

    ISO 27001 and SOC 2 Type 2 are documented for the managed platform. Still confirm SSO and the SLA on the plan.

Choose Strapi when

  • A CMS project you can host

    The same Strapi project can run on your servers or on Strapi Cloud. Community includes drafts, roles and locales.

  • Locales on the free CMS

    The pricing page lists unlimited locales on Community, Growth and Enterprise. Enable them per content type and field.

  • Admin content-type builder

    Editors and developers can model collection types, components and dynamic zones in the Content-type Builder.

Consider neither when

  • A visual page builder by default

    Contentful’s canvas needs Studio. Strapi live updates in the admin need Growth or Enterprise. A product with composition on the plan you will buy may fit better.

  • Review workflows on a free license

    Contentful workflows depend on the plan, and a Starter space lists them as unavailable. Strapi review workflows are Enterprise.

  • Cloud hosting plus paid CMS features

    Strapi Cloud is a separate hosting bill and does not include Growth or Enterprise CMS features. Price the CMS license as well if you need those features.

Criterion-by-criterion comparison

How we evaluate platforms

Marketer autonomy

Both default to structured entry forms. Page layout stays in the frontend unless an extra editing product is funded.

Contentful

Entry editing; page assembly is extra

Editors can update structured fields, references and localized values in the web app. Assembling pages from design-system components depends on Studio setup and the role granted to that editor.

Plan considerations: Free spaces include administrator and editor roles. Custom roles that narrow publishing or locales require Premium.

View sources (3)
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.
  • Contentful Experiences: Describes the drag-and-drop canvas, registered design-system components and field-level locales.
  • Contentful space roles: Lists default roles and states that custom, translator and freelancer roles require Premium.

Strapi

Editors fill types; layout follows the model

Editors manage entries, components and dynamic zones in the Content Manager. Adding a section type or a permission still happens in the content-type and role settings developers control.

View sources (2)

Choosing between them

Contentful:

Editors change fields, references and locales in the hosted app. Assembling pages depends on Studio and the role.

Strapi:

Editors fill types, components and dynamic zones. New section types and permissions stay in settings developers control.

Give a marketer one page task in each admin and count the steps that still require a developer.

Content modeling

Both model structured types and reusable pieces. Contentful hosts the model. Strapi stores it in the project.

Contentful

Content types, fields, references and rich text

Teams model entries with up to 50 fields, rich text and references to other entries. The same model can be edited in the web app or changed with the management API and CLI migrations.

Plan considerations: Premium cross-space references allow three reference fields per type and cap how many entries can be linked.

View sources (3)
  • Contentful data model: Defines spaces, content types and up to 50 fields, including rich text and entry references.
  • Contentful references: Describes one-to-one and one-to-many entry references, including Premium cross-space references.
  • Contentful import and export: CLI export and import cover entries, assets, models and roles. Version history is not migrated.

Strapi

Collection types, components and dynamic zones

The Content-type Builder defines collection types, single types, components and repeatable dynamic zones. Saving a type requires at least one configured field.

View sources (1)

Choosing between them

Contentful:

Use it when entries and references should be shared across channels on a managed API.

Strapi:

Use it when collection types, components and dynamic zones should live in a project you can also edit in the admin.

Model one shared record and one page with repeatable sections, then see which admin matches the content you already have.

Workflow and governance

Contentful plan limits workflows and custom roles. Strapi includes drafts and roles on Community, and review workflows on Enterprise.

Contentful

Roles and releases depend on the plan

Workflow count depends on the plan, and a Starter space lists workflows as unavailable. Custom roles are Premium, and Launch lists specific paid plans for grouped releases.

Plan considerations: Confirm current plan names. The Launch page still lists Team and Enterprise alongside Lite and Premium.

View sources (4)
  • Contentful workflows: Says workflows are available only on specific plans and limits one workflow to 20 steps.
  • Contentful space roles: Lists default roles and states that custom, translator and freelancer roles require Premium.
  • Contentful pricing: Free column and Starter quotas include two locales, API caps and no Starter workflows.
  • Contentful Launch app: Groups entries into releases and lists Team, Lite, Enterprise and Premium as eligible plans.

Strapi

Drafts and roles free; reviews are Enterprise

Community includes draft and publish, RBAC and API tokens. Releases and content history start on Growth. Review workflows and audit logs are Enterprise.

Plan considerations: Growth history is 14 days. Enterprise history is documented as 30 days, extendable to 90.

View sources (1)

Choosing between them

Contentful:

Custom roles are Premium, and Launch lists specific paid plans for grouped releases.

Strapi:

Draft and publish and RBAC are on Community. Releases start on Growth. Review workflows and audit logs are Enterprise.

List the approval and release steps you need, then map each one to a Contentful plan or a Strapi CMS tier.

Localization and multisite

Contentful localizes fields and caps locales by plan. Strapi lists unlimited locales on every CMS tier.

Contentful

Field locales, with other structures optional

Field-level locales are built in. Entry, content-type and space copies support independent publishing, and those separated approaches do not get straightforward fallback.

Plan considerations: The free plan lists two locales. Translator roles require Premium, and locale-based publishing is described as an Enterprise-space feature.

View sources (3)

Strapi

Locales on every plan, including Community

Turn internationalization on for a content type, then for individual fields. The pricing page lists unlimited locales on Community, Growth and Enterprise.

View sources (2)

Choosing between them

Contentful:

Translator roles require Premium, and locale-based publishing is described as an Enterprise-space feature.

Strapi:

Turn internationalization on per content type and field. The pricing page lists unlimited locales, including Community.

Count launch locales and decide whether each market must publish alone. Then check the Contentful plan against Strapi’s free locale support.

Developer experience

Contentful developers script a hosted model. Strapi developers own the Node project and can model in the admin.

Contentful

CLI migrations, environments and management APIs

Developers script content-model changes, merge environments and call management APIs. The team still owns the frontend, the Live Preview SDK and any custom editor extensions.

View sources (4)
  • Contentful import and export: CLI export and import cover entries, assets, models and roles. Version history is not migrated.
  • Contentful Merge app: Compares content-type changes between environments and can export a migration script.
  • Contentful API basics: Separates delivery, preview, management, Images and GraphQL APIs, including separate EU hosts.
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.

Strapi

Node project, admin builder and a CLI

Developers own the Strapi project and can model in the admin or extend it in code. The same project runs self-hosted or on Strapi Cloud.

View sources (2)

Choosing between them

Contentful:

CLI migrations and environment merges change content types. The frontend and preview SDK stay with the team.

Strapi:

The team owns the Strapi project, whether it runs self-hosted or on Strapi Cloud.

Decide if content-type changes should be a hosted migration or a change in a repository you deploy.

APIs and extensibility

Both offer REST and GraphQL. Contentful splits delivery, preview and management hosts. Strapi serves them from the project.

Contentful

Delivery, preview, management, GraphQL and webhooks

Published content uses the delivery and GraphQL APIs, drafts use the preview API, and the management API plus webhooks cover writes and events. EU customers have separate API hosts.

View sources (2)
  • Contentful API basics: Separates delivery, preview, management, Images and GraphQL APIs, including separate EU hosts.
  • Contentful webhooks: Webhooks call a public endpoint for selected content events from the web app or management API.

Strapi

REST and GraphQL on every CMS plan

REST and the GraphQL plugin read and write content types, including locale and draft status. The features table includes both APIs on Community.

View sources (3)
  • Strapi REST API: Documents REST reads and writes, including locale and draft status parameters.
  • Strapi GraphQL API: The GraphQL plugin queries and mutates content types with filters, sort and pagination.
  • Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.

Choosing between them

Contentful:

Drafts use the preview API, published content uses delivery and GraphQL, and webhooks use the management side.

Strapi:

REST and the GraphQL plugin read and write content types, including locale and draft status, on Community.

Request one published read, one draft read and one write from the frontend you will ship before choosing the API layout.

Hosting and operations

Contentful is only a managed platform. Strapi can be self-hosted or placed on Strapi Cloud.

Contentful

Managed AWS platform; frontend stays with you

Contentful runs the content APIs, editor and CDN on AWS, with US or EU residency options. Your team still hosts the website, builds and application runtime.

View sources (1)

Strapi

Self-host the project, or use Strapi Cloud

You can operate the Node.js app and database, or deploy that project to Strapi Cloud. Cloud plans meter hosting resources and do not include Growth or Enterprise CMS features.

View sources (2)

Choosing between them

Contentful:

The vendor runs the content APIs, editor and CDN. Downloading the platform to host it yourself is not offered.

Strapi:

You operate the Node app and database, or deploy that project to Cloud. Cloud does not include paid CMS features.

Name who will patch the CMS and database. Choose Contentful when that owner does not exist, and Strapi when it does.

Security and governance

Contentful documents platform assurance. Strapi’s SOC 2 report, SSO and audit logs are paid CMS items.

Contentful

ISO 27001 and SOC 2; controls vary by plan

Documented assurance includes ISO/IEC 27001:2022, SOC 2 Type 2, encryption and daily backups on AWS. Confirm SSO, SCIM, embargoed assets and the uptime SLA on the plan you will buy.

Plan considerations: Custom roles are Premium. EU residency is a documented customer option with separate API hosts, not the default US regions.

View sources (3)

Strapi

RBAC everywhere; SSO and audit logs are paid

Community includes role-based access. SSO is a Growth add-on and included on Enterprise. Audit logs and the SOC 2 report are Enterprise items on the pricing page.

Plan considerations: Self-hosted data residency is yours. Strapi Cloud regions and backups follow the Cloud plan.

View sources (2)
  • Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
  • Strapi CMS pricing: Lists the free MIT Community plan, Growth at $45 per month, and Enterprise review workflows.

Choosing between them

Contentful:

ISO 27001 and SOC 2 Type 2 are documented. Confirm SSO, SCIM and the SLA on the exact plan.

Strapi:

Community includes role-based access. SSO is a Growth add-on or included on Enterprise. Audit logs and the SOC 2 report are Enterprise.

Match the questionnaire to Contentful’s plan and, for Strapi, to the CMS tier plus whoever operates the host.

Pricing and cost drivers

Contentful bills the space and API use. Strapi can be a free CMS plus a separate Cloud invoice.

Contentful

Spaces, users, API calls and add-on products

Free includes one Starter space, 10 users and hard API and bandwidth caps. Lite raises the user cap and can add one space; Premium prices spaces and users by contract, and Studio is licensed separately.

Plan considerations: Starter spaces list 25 content types, two environments, 10,000 records, two locales and no workflows. Confirm current overages before you budget.

View sources (3)

Strapi

Free Community, then CMS and Cloud bills

Community is free under MIT, with unlimited entries on the CMS pricing page. Growth starts at $45 per month before user charges, and Strapi Cloud is a separate hosting invoice.

View sources (2)
  • Strapi CMS pricing: Lists the free MIT Community plan, Growth at $45 per month, and Enterprise review workflows.
  • Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.

Choosing between them

Contentful:

Free is one capped Starter space. Paid plans change users and spaces, and Studio is a separate license.

Strapi:

Community is free. Growth starts at $45 per month before user charges, and Strapi Cloud is billed separately.

Price locales, users, API volume and preview or Studio. Add a Strapi CMS license if Cloud alone will not include the features you need.

Migration and exit

Contentful exports a space with the CLI. Strapi transfers content between projects with matching schemas.

Contentful

CLI export and import; history is not copied

The CLI can export entries, assets, content types, roles, tags and webhooks, then import them into another space. Version history starts fresh, and your frontend, URLs and preview code still need a separate plan.

Plan considerations: Drafts are excluded unless include-drafts is set. Embargoed assets need the download and upload options.

View sources (1)

Strapi

Transfer content between matching Strapi instances

The CLI can export, import or stream content, files and schemas. A transfer requires matching schemas, and it does not move admin users or API tokens.

View sources (2)
  • Strapi data transfer: Streams content, files and schemas between instances. Admin users and API tokens are excluded.
  • Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.

Choosing between them

Contentful:

Entries, assets, types, roles, tags and webhooks can move. Version history starts fresh in the destination.

Strapi:

The CLI can export, import or stream content, files and schemas. It does not move admin users or API tokens.

Run a sample transfer of entries, assets and locales into a trial, and plan a separate path for users and tokens.

Marketing website fit

Both can feed a marketing site from structured entries. Live visual composition is an extra license on each.

Contentful

Fits structured sites when preview is funded

Marketing pages work when entries, references and a preview URL match the design system. Visual composition is practical only after Studio components and roles are set up.

View sources (3)
  • Contentful data model: Defines spaces, content types and up to 50 fields, including rich text and entry references.
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.
  • Contentful Experiences: Describes the drag-and-drop canvas, registered design-system components and field-level locales.

Strapi

Fits structured pages when preview is funded

Dynamic zones let editors place components that the frontend already renders. Seeing those changes live in the admin depends on a Growth or Enterprise Live Preview license.

View sources (2)
  • Strapi Content-type Builder: Creates collection and single types, with draft-and-publish and internationalization settings.
  • Strapi preview: Preview is configured for every plan. Live Preview requires Growth or Enterprise.

Choosing between them

Contentful:

A preview URL and entries can run the site. Drag-and-drop composition waits on Studio.

Strapi:

Dynamic zones place components the frontend already renders. Seeing those edits live in the admin needs Growth or Enterprise.

If weekly page composition is the job, fund Studio or Strapi Live Preview, or choose a page builder included on the base plan.

Visual editing and preview

Contentful’s canvas needs Studio. Strapi opens a preview URL on every plan, and live updates are paid.

Contentful

Live preview; visual canvas needs Studio

Side-by-side preview works after a preview URL is configured. Live updates, click-to-field editing and drag-and-drop Experiences need the relevant SDK, and Experiences also need a Studio license.

Plan considerations: A Studio license enables Experiences in up to three spaces unless additional spaces are purchased.

View sources (3)

Strapi

Preview URL on every plan; live updates are paid

Preview opens the frontend from the Content Manager after you set a client URL. Live Preview, which refreshes as the entry changes, is a Growth and Enterprise feature.

View sources (2)
  • Strapi preview: Preview is configured for every plan. Live Preview requires Growth or Enterprise.
  • Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.

Choosing between them

Contentful:

Fits teams that will license Studio and connect the Live Preview SDK.

Strapi:

Fits teams that can launch with a preview URL, or fund Growth for live updates in the admin.

Preview the same draft entry in both products and record whether editors see changes without a paid preview add-on.

Recommendations by use case

[Marketing website]

Contentful unless you will own Strapi

Contentful fits a managed marketing backend. Choose Strapi when the team will run the project and can accept a preview URL until Live Preview is funded.

[Structured content platform]

Either, based on who hosts it

Both suit reusable types and components. Choose Contentful for a managed API, and Strapi when the model should live in a project you operate.

[Multilingual multisite]

Strapi when locale count is open

Strapi lists unlimited locales on Community. Contentful locale caps, translator roles and locale-based publishing follow the plan. Test independent publishing.

[Ecommerce]

Match the catalog owner

Contentful references suit a managed catalog API. Strapi collection types fit when product content should live in the Node project the store team runs.

[Enterprise governance]

Validate tier, not the product name

Contentful assurance is documented for the platform, with plan-based roles and workflows. Strapi review workflows, audit logs and the SOC 2 report are Enterprise.

[Small team]

Contentful if nobody will patch it

Contentful bills a managed space. Strapi Community is free only if someone will operate the app and database, or you add a Cloud bill.

[Self hosted control]

Strapi when the CMS must be yours

Strapi can run on your servers. Contentful does not offer a downloadable platform. Strapi Cloud remains optional and is a separate hosting product.

Related resources

Strapi logo

[Platform]

Strapi

Open-core content types you host or run on Cloud.

Read more
Contentful logo

[Platform]

Contentful

Structured entries with plan-dependent visual page composition.

Read more