Contentful vs Payload CMS

All schemas are TypeScript config files, no GUI limits. Union types, custom components, and hooks all first-class.

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

Fields and blocks are shared as named exports. Lexical blocks map cleanly to design system components.

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

Custom TypeScript validators are first-class, the most powerful validation system in any headless CMS.

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

Admin UI is developer-oriented. Significant customization needed before non-technical editors can work independently.

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

Live preview via a configurable preview URL. Requires developer setup to connect your frontend deployment.

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

Drafts, versions, and autosave. Scheduling supported. Approval chains and custom stages need custom code.

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

Media collections handle uploads with basic resizing on ingest. CDN and advanced transforms need Cloudinary or S3.

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

No simultaneous editing. Concurrent edit locking prevents conflicts, one editor holds a document at a time.

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

Access control is extremely powerful, any async function can gate any operation. Field-level access is first-class.

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

Built-in localization supports field-level variants across all collection and global types, set in schema.

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

Fallback configured in Payload config and honored by Local API, REST, and GraphQL, a clean open-source implementation.

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

Docs are well-written and rapidly improving. Schema-generated TypeScript types. REST and GraphQL auto-generated.

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

Runs inside your Next.js app, the deepest CMS integration possible. Astro and other framework adapters coming.

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

The Local API gives in-process data access with no HTTP overhead. REST and GraphQL cover external management.

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

No built-in environment branching, staging requires a separate instance. Payload Cloud adds environments on paid plans.

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

Self-hosted with no CDN. Asset delivery via S3, Cloudinary, or local disk, CDN is your responsibility to set up.

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

Requires Node.js and a database. v3 cohabitation removes one service but the database is still your responsibility.

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

Official Stripe, Cloudinary, and SEO plugins available. Community ecosystem is growing but less mature than others.

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

Highly active GitHub with fast maintainer response. Discord is engaged and growing since the v3 release.

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