Contentful

At a glance

Contentful is a hosted content backend: developers define structured fields, editors fill them in, and a separately built website or app retrieves the content through APIs. It is worth the setup when the same articles, product information or other content must serve several experiences without tying editors to each frontend’s code. For a small site that mainly needs a finished template and a Publish button, the content modeling and integration work may outweigh the benefit.

Good fit

Teams with developer support that need reusable, localized content and a consistent editing structure. A content type defines the fields; an entry holds one item, and reference fields connect items such as an article and its author. Developers control how that content appears. Agents can use the Content Management API to create or update content with a user’s authorization, while the read-only Delivery API serves published material. This separation lets editing and presentation evolve independently, provided someone maintains their contract.

Consider something else when

You want an immediately finished website, or your team cannot maintain content models, a frontend and its preview integration. Contentful Studio is a separate visual product rather than evidence that every Platform plan removes that work. If owning the CMS runtime is central to the decision, Strapi offers a headless CMS that can run on your own Node.js host. That changes who operates the backend; it does not eliminate frontend development.

Start here

In an authorized trial, use synthetic content in a Starter Space. Define one article content type with title and body fields, then open Content, choose Add entry and select that type. Connect a small frontend to the Delivery API and verify the published item appears. To review a draft in context, an administrator must configure Settings, then Preview against a working preview frontend using the Preview API. Keep preview credentials out of preview URLs. These are documented steps, not a publishing workflow performed for this review.

Cost and requirements

On 31 October 2026, Free included ten users, two locales, 100,000 monthly API calls and 50 GB of asset bandwidth, with hard usage caps. Lite was $300/month and included the same-size Starter Space: 25 content types, two environments and 10,000 records. The larger Lite Space was an additional $850/month, not part of the $300 price. Paid usage overages and frontend hosting add to the budget. Check the content structure, traffic and workflow requirements together before choosing a tier.

Limits to know

Content and assets live in the hosted service; editor permissions and API credentials need separate review. Protected, embargoed assets require an eligible plan and space configuration, and are disabled by default. Removing files from the delivery network can take 24–48 hours after deletion or archiving across all environments. APIs and a CLI can export core content, models and assets, but an export is not a ready-made replacement website or a complete copy of service configuration and credentials. Public plan controls were inspected; editor usability, API calls, publishing, export/restore and production reliability were not tested.

Related work

• Strapi: compare operating your own headless CMS (alternative)