Contentful logo

[Platform profile]

Contentful for marketing websites

Contentful for structured entries, field-level localization, live preview and marketing website delivery.

Managed SaaS Proprietary Official website
Kalle Bertell

By Kalle Bertell

Direct answer

Contentful suits teams that model marketing content as structured, reusable entries and can fund a frontend, preview integration and governance tier. Field-level locales and a managed content API make multi-channel delivery plausible. Consider another platform when you need a self-hosted content backend or visual page building without a Contentful Studio license.

Good fit

  • Reusable structured entries

    Content types and references let editors reuse an entry across pages and channels once the model is in place.

    View sources (2)
    • 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.
  • Built-in field localization

    Multiple locales can live on one entry. Separate entries, content types or spaces remain available when markets publish independently.

    View sources (1)
  • Scripted content-model changes

    Developers can move content-type changes with CLI migrations and environment merges instead of editing production by hand.

    View sources (2)

Consider alternatives

  • Self-hosted content backend

    Contentful is a managed cloud service. The vendor states that downloading the platform to host it yourself is not offered.

    View sources (1)
  • Visual pages without Studio

    Drag-and-drop page assembly needs a Contentful Studio license and registered design-system components. The default editor is an entry form.

    View sources (2)
  • Custom roles on a free plan

    Custom, translator and freelancer roles require Premium. A Starter space also lists workflows as unavailable.

    View sources (2)
    • 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.

Evidence by criterion

How we evaluate platforms

Visual editing and preview

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)

Marketer autonomy

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.

Content modeling

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.

Workflow and governance

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.

Localization and multisite

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)

Developer experience

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.

APIs and extensibility

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.

Hosting and operations

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)

Security and governance

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)

Pricing and cost drivers

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)

Migration and exit

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)

Marketing website fit

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.

Team takeaways

For content teams

Content teams edit structured entries and localized fields in the web app, then preview them when a preview URL is connected. Independence stops at layout: drag-and-drop composition needs Contentful Studio and registered components, and publishing rights follow the role on the plan.

For developers

Developers get a managed content API, CLI migrations and environment merges, and they keep the website runtime. Plan for the Live Preview SDK, any Experiences components and ongoing content-type migrations. There is no supported path to run the content backend on your own infrastructure.