Payload review

The same six dimensions used across every platform in this directory, so the numbers are directly comparable. Two things to hold in mind. This is our featured pick and it is also what this site runs on, so read it sceptically. And the scale does not score operational burden: running Payload means running a database, which is a real, recurring cost that is entirely absent below. Read the limits section alongside it.

• Developer experience5/5

  Config is TypeScript, the admin is generated from it, and the Local API removes the network hop entirely.

• Editor experience4/5

  A genuinely good admin panel with live preview, but no real-time collaborative editing and it still reads as a developer's tool.

• Content modelling5/5

  Blocks, arrays, relationships, localisation and access control at field level, all version-controlled.

• Pricing clarity4/5

  Free and unmetered under MIT, which is as clear as it gets. Enterprise is unpublished, which is the only deduction.

• Lock-in risk5/5

  MIT licence plus your own Postgres. The content is queryable with plain SQL and the licence cannot be revoked.

• SEO and AEO fit5/5

  It runs inside the Next.js app, so rendering mode, metadata and schema are entirely yours by construction.

An editorial read, not an aggregate of user reviews, and deliberately kept out of this page's structured data.

From Payload's own YouTube channel. Vendor marketing rather than an independent review, included because it is the quickest way to see the product before you sign up.

Payload overview

A minimal fetch against the live API, with credentials read from the environment rather than pasted inline.

import { getPayload } from "payload"
import config from "@payload-config"

// Runs in the same Node process as the page being rendered. There is no
// network hop, no API key and no rate limit, because there is no vendor
// in the request path: this is a query against your own database.
const payload = await getPayload({ config })

const { docs } = await payload.find({
  collection: "posts",
  where: { slug: { equals: slug } },
  depth: 1, // resolves the author relationship in the same query
  limit: 1,
})

const post = docs[0]

• There are no software limits. No seat cap, no request metering, no document ceiling, no feature gate. The constraints below are all operational.
• Requires Node.js 20.9.0 or later and one of Postgres, MongoDB or SQLite, which you provision and back up yourself.
• File uploads need a storage adapter. Local disk does not survive a serverless deploy, so plan on Vercel Blob, S3 or R2 from the start.
• On serverless, the admin panel and the database connection both pay cold-start cost. A connection pooler such as Neon's or PgBouncer is effectively mandatory at any real traffic.
• The Local API is only available in the same process. A separate front end has to use REST or GraphQL and gives up the main performance advantage.
• Upgrades are yours to run. Major versions have migration guides, but nobody applies them for you.

• “All of that can be done pretty easily with PayloadCMS. I wouldn't pick Strapi if I needed even a slight bit of customization. Directus is a no-go since you need localization. Give Payload a shot.”

  r/PayloadCMS on Reddit

• “I switched from Strapi to Payload after research and so far I really like how Payload works, the documentation, etc. Also if you know nextjs, payload will be easier as it's also build with nextjs. Strapi is easier to use (you need less Backend knowledge). With Payload you define in code what you need. Harder first but this means you will learn more how it works as well.”

  r/PayloadCMS on Reddit

• “I've used Wordpress, Payload and Strapi. And although the latter two are very powerful and preferrable from a developer perspective, my customers still prefer Wordpress”

  r/nextjs on Reddit

• “Just sounds like you prefer a more gui based approach than a code-first approach. I like to have a record of my changes from a code perspective as that's what I'm hired to do. I've found the payload community to be more ambitious than strapi's, and have seen faster feedback loops in discord than most.”

  r/PayloadCMS on Reddit

• “I knew nothing about NextJs when I started my Payload project. NextJs is in my opinion simple to learn if you know Js well enough. I was also learning react for the first time so it was literally all new to me. I think its very doable dependent on how comfortable you are with Js, reading docs, and learning from YouTube/tutorials.”

  r/PayloadCMS on Reddit

• StrapiFree
• WordPress (headless)Free
• SquidexFree
• DirectusFree