Contentful vs Headless WordPress

Strong content types with references. Lacks native union fields, workarounds need multiple reference fields.

WordPress custom post types and ACF (Advanced Custom Fields) give you significant flexibility, but content modeling requires plugin stacking rather than being native to the platform. Complex relational content and deeply nested structures need WPGraphQL plus ACF Plus plus Flexible Content layouts, workable, but fragile compared to schema-first headless platforms.

Content types can reference each other for reuse but there's no native block primitive. Rich Text embedded entries help.

Reusable content blocks exist via ACF Flexible Content or the block-based Gutenberg editor, but mapping them cleanly to design system components requires careful plugin configuration and custom development. There is no native concept of component-level reusability, you are adapting a publishing model into a component model.

Built-in validators for required, range, size, and regex. Custom validators need a UI extension to configure.

Field-level validation is available through ACF and custom plugin code, but it is not enforced at the API layer. A determined editor can bypass most constraints. Native WordPress offers required fields but no character limits, regex validators, or custom validation rules without additional development.

The web app is polished and familiar, editors with any CMS background can publish independently without developer help.

This is where WordPress earns its reputation. Millions of content editors already know the WP admin interface. Onboarding for an existing WP user is near-instant. For net-new editors, the Gutenberg block editor is reasonably intuitive and the learning curve is gentle compared to structured headless platforms.

Live preview requires developer config of the Preview API. No out-of-the-box visual editor available.

Live preview in a headless setup requires bespoke development. WordPress's built-in preview targets the traditional theme layer, not a decoupled frontend. Faust.js provides a preview mode, but configuring it correctly requires meaningful engineering effort and breaks if the frontend stack changes.

Draft and published states built in. Tasks and comments need Teams+ plans. Approval chains require external tooling.

Drafts, scheduled publishing, and basic role-based permissions are built in. Multi-step approval workflows require plugins (PublishPress, Nelio Content) that add maintenance overhead. Compared to platforms with native editorial workflow tooling, WordPress gets the basics right but requires plugins for anything beyond simple draft/publish.

Media Library handles uploads, tagging, and image API transforms. No native AI cropping or focal points.

The WordPress Media Library is functional and familiar. It handles uploads, basic organisation, and image cropping. At scale it becomes unwieldy, no tagging, no advanced search, folders require plugins. For a headless setup, images still need to be served from WordPress or offloaded to a CDN integration, adding configuration overhead.

No simultaneous editing, last save wins. Conflicts between concurrent editors are not surfaced in real time.

WordPress has no native real-time collaboration. Two editors working on the same post will overwrite each other without warning in most configurations. The Gutenberg editor has basic collaborative editing in development as of 2026, but it is not production-ready for simultaneous authoring at the level competitors provide.

Roles support content type and tag-based access. Field-level permissions need Contentful Apps or higher plans.

WordPress ships with five default roles (admin, editor, author, contributor, subscriber) and these cover most small team needs. Fine-grained permissions, by content type, taxonomy, or specific fields - require plugins like Members or User Role Editor. It is workable but not elegant.

Multi-locale is a core feature, every field localizes independently with locale-specific publishing states.

Multi-language in WordPress requires third-party plugins (WPML, Polylang, or TranslatePress). None of these are native, all add database complexity, and none offer true field-level localisation in a structured headless sense. For serious multilingual projects this is a significant limitation.

Fallback is configurable in space settings and honored by the Delivery API when a translation is missing.

Locale fallback logic is not a native WordPress concept. WPML and Polylang have partial support, but managing fallback behaviour programmatically via the API requires custom development. This is one of the clearest gaps vs. purpose-built headless platforms.

Comprehensive REST and GraphQL docs with a playground, official SDKs in JS, Python, and PHP, with TypeScript support.

The WP REST API is well-documented and stable. WPGraphQL has strong documentation and an active community, with the v2 release in 2025-2026 adding persisted queries and federation support. TypeScript type generation works via GraphQL Code Generator. The gap vs. native headless platforms is the complexity of the underlying data model, posts, meta fields, and custom post types create a schema that reflects decades of WordPress architecture decisions rather than clean content modeling.

Official Next.js and Astro starters for all major frameworks. The npm package is mature and well-documented.

Vercel maintains an official Next.js + WordPress starter. WP Engine's Faust.js provides a more opinionated React framework for headless WordPress, though its development pace slowed in 2025-2026 as WP Engine refocused resources. Astro and Nuxt integrations exist via community packages. The ecosystem is real, but most integrations require more configuration than native headless CMS SDKs.

The CMA supports migrations, bulk ops, and content type management. contentful-migration CLI is production-grade.

The WP REST API supports create, read, update, and delete operations, but it is optimised for traditional editorial use - not bulk content operations, AI ingestion pipelines, or programmatic schema management. There is no concept of environment-scoped content operations or transactional batch writes native to the platform.

Environment branching is a flagship feature. Each space supports multiple environments with full content promotion.

WordPress has no native staging or environment branching. Most teams solve this with separate WordPress installs, WP Migrate DB for database syncing, or managed hosting environments (WP Engine, Kinsta) that provide staging slots. Schema changes cannot be previewed or rolled back in any structured way, a core limitation for iterative development.

Content via Fastly CDN with sub 100ms API response times. Images via Fastly Image Optimizer.

WordPress itself does not deliver content via a CDN, that depends entirely on your hosting provider and caching plugins (WP Rocket, W3 Total Cache). In a headless setup, API responses come from a PHP application server, not a globally distributed edge network. Latency is highly dependent on infrastructure choices and requires deliberate engineering to optimise.

Fully managed SaaS with zero infrastructure to configure or maintain. Scales transparently with usage.

Deploying and maintaining WordPress headless requires running two systems: the WordPress backend (PHP, MySQL, web server) and the decoupled frontend (Node.js, CDN, build pipeline). This is significantly more infrastructure than a managed headless CMS. WordPress.com and WP Engine simplify the WordPress side, but the overall system complexity is real.

Largest CMS marketplace, apps for Shopify, Salesforce, Cloudinary, and Imgix. Enterprise integrations are solid.

With over 59,000 plugins and 20+ years of community development, the WordPress ecosystem is unmatched in breadth. ACF, WooCommerce, Yoast, and hundreds of other well-maintained plugins solve real problems quickly. For headless specifically, WPGraphQL, Faust.js, and official hosting integrations with WP Engine and Kinsta make the setup viable. The caveat: plugin quality is highly variable, and in a headless context you only use a fraction of this ecosystem.

Active forums and a certification program. Less community content than others but strong enterprise support.

WordPress's community is the largest in the CMS world, 40% of the web runs on it, and WordCamp events run globally. WPGraphQL and the headless ecosystem specifically have an active community and regular releases. However, the overall direction of WordPress is toward the full-site editing and block editor experience, not headless-first architecture, so community energy for headless specifically is a subset of the whole.