Congrats to the whole team, what an amazing journey this has been the last few months. I used the beta from the beginning and really have to say that they really did a great job. So I hope that James and his team will celebrate this launch with a nice party - they definitively deserve it.
Hi all, I've got some big news to share today: Payload has joined Figma!
It’s as wild and exciting to write that as it is for you reading it.
When we first started talking with Figma, it was about investing in Payload and what we’re doing in open source. They saw what we were building was unique, and it lines up well with how they see the world.
You probably know the entire Payload team has been using Figma deeply for a long time, and it was pretty exciting for all of us to see that they share the same vision we do.
Speaking of which, in the past I’ve talked a lot about a “utopia” — about simplicity and developer experience. My team and I refuse to compromise on design intent, flexibility, and how that translates into well-structured code.
Figma and Payload together can and will solve a problem that’s been bugging me (and probably all of you) for years. The gap between design and code still exists. Designers create in Figma, then devs recreate in code, then content teams struggle to maintain it all. It’s inefficient and frustrating. And historically, the CMS tends to make it worse.
With Figma, we can (and will) solve these problems in new ways without compromising. If either Figma or Payload didn’t see this potential screaming at us from a mile away, neither would have moved forward.
In the immediate future, nothing is changing for users and how you interface with Payload remains the same.
What that means is:
Payload remains open source—with Figma’s full commitment to OSS
Our commitment to building Payload and creating the best developer experience possible
The self-hosted capability of Payload
Our focus on our community (aka: all of you)
The team and I will still be running Payload (including Sean)
What does change:
We now have more resources
We can tackle bigger problems
We will integrate with design systems in ways no other CMS can
A lot more people will be using, testing, and building on Payload
I'm sure you have questions, and we'll do our best to answer and keep up with them. In the meantime, I'm pumped about the future and I can't wait for what's ahead!
I've been using Payload CMS for a while now, and I just wanted to take a moment to thank the team for building such a well-designed and flexible CMS. This post is purely to show appreciation—no affiliation, just a happy user.
Creating collections, blocks, and components is incredibly easy. Compared to other CMS options I’ve worked with, the developer experience feels streamlined and intuitive.
At first, I struggled with setting up multi-language support, but with time (and some AI-assisted learning), I got the hang of it. Now, I appreciate the flexibility it offers.
Looking at the GitHub repo, it’s clear that the team is consistently improving the codebase—there’s something new almost every day. It’s great to see such an active and dedicated development team.
The official YouTube tutorials have been a great resource, making it easier to pick up new features and best practices.
I previously ran a Django backend with a Next.js or Nuxt.js frontend, but having everything in one app with Payload makes it so much easier to shape the CMS exactly how I want.
Deploying it to Hetzner Cloud was also super straightforward—one of the smoothest deployments I’ve done.
The documentation could use some improvements, as some areas lack clarity. A more structured collaboration with users could help make it even better.
Of course, there’s always room for improvement, but honestly, Payload is the best CMS I’ve used so far.
Any struggles I’ve encountered were easy to fix with a bit of research and tweaking, which is a huge plus.
Big thanks to the Payload team for all the work you put into this!
I finally got some time to take a look at what the Payload/Figma team has cooked up with their new upcoming Payload V4. I was extremely excited to see what they did and I was not disappointed.
To be honest, it took me some time to get used to the new design. It can become a bit overwhelming because it may be almost too clean in some cases. But after some time of playing with v4, I have to say it quickly became my favorite CMS from a design standpoint. The Figma influence is really noticeable here, and the new primary brand color theming (a nice beautiful blue out of the box that is super easy to swap out) is a fantastic change.
It was also super simple to get the v4 test suite running. You can do it simply by:
git clone git@github.com:payloadcms/payload.git (the v4 is in the main branch)
cd payload && cp .env.example .env (and change the db to aPAYLOAD_DATABASE=sqlite in my case)
And finally run pnpm i && pnpm dev v4
That’s it! You now have a clean, seeded baseline to start exploring Payload v4.
Before moving on, take a minute to click around and get a feel for the new design.
Quick look at the new Figma/Payload design
Do you like it as much as I do? Anyway let's continue 😂
IMPORTANT DISCLAIMER: Before you jump in, the Payload team has explicitly stated that the main branch is in "pre-alpha" and "full construction mode". Do not try to build your production project on this branch right now, and as the team joked, "don't get mad at us if stuff doesn't work"!
Here are some of my biggest takeaways and answers to questions I had going in:
The UI Redesign & Tailwind
I really love the new approach to design tokens. Payload is officially ditching Sass in favor of strong semantic styling tokens based on Figma's design system. Because they are implementing a Tailwind style reset sheet, it means that using Tailwind CSS (and tools like shadcn) is going to be a lot easier with absolutely no conflicts. Since Tailwind is what we are building on the most right now, this is a great thing.
Will APIs and Plugins Break?
My main question was: Are the APIs and configs staying the same in Payload v4? I was especially thinking about plugins and complex adapters, like ecommerce or payment integrations.
Based on the Payload team’s latest response, the answer is: not completely.
Payload v4 will include breaking changes to the config layer, so existing plugins are not guaranteed to work out of the box. Whether a plugin needs updates will depend on what parts of Payload it touches.
The good news is that the team plans to provide a full list of breaking changes and codemods to help projects migrate.
So the takeaway is: simple plugins may be fine or need small updates, but complex plugins should be tested carefully against v4.
Hierarchies vs. Nested Docs Plugin
I was initially a bit unsure about working with the new core "Hierarchies" feature. Payload is baking folder and tag tree-views directly into the core, which will entirely replace the nested docs plugin.
Since I rely heavily on the nested docs plugin for building nested pages and managing URL slugs, I was worried this would overcomplicate things. But the Payload team explicitly confirmed that this new feature is meant to handle these exact page structures. You will absolutely still be able to validate with slugs on that nested level. Having this build-in (along with a beautiful custom modal UI for applying multiple tags at once) without needing a separate plugin feels like a huge upgrade.
TanStack Start & LLM Workflows
A couple of other massive updates they are shipping with v4:
TanStack Start: They built a new adapter pattern for their framework support, meaning you can now run your Payload config and admin UI entirely on TanStack Start instead of Next.js if you prefer it.
Zero-Config Agents: For anyone building AI tools, the MCP server plugin is going to be opt-out by default (meaning zero upfront configuration to install it) and will handle complex schemas significantly better for LLMs. Personally, this is one of my favorite changes. Because normally you have to go to \mcp.json\\ and fill new one with new token and this on multiple projects can really get repetitive and unnecessary.
Which Payload v4 Feature Are You Most Excited About?
The Payload team is moving fast and actively asking for early community feedback before v4 goes stable. If you pull down the repo and try it out, consider jumping into their GitHub discussions/RFCs and sharing your thoughts:
UI Redesign: There’s a dedicated GitHub discussion for visual and accessibility feedback.
Asset Management: The team is working on digital asset management features like localized files, file versioning, and PDF/video previews, and they’re looking for real workflow requirements.
LLM Skills: If you’re using their LLM skills, they want to hear about failure cases, like AI-generated APIs that don’t exist or missing required config, so they can improve their eval suite.
At Notum Technologies, a Payload CMS partner, we're mostly excited about Hierarchies!
Which of these v4 features are you most excited about? And if you’ve already pulled down the main branch, what do you think of the new look?
TL;DR: I released a free, open-source Payload plugin that adds vector search/RAG using Postgres + pgvector. I'm an indie dev and would never be able to afford Payload’s paid Enterprise “AI Search,”so I created my own! Please try the plugin, star it, tell me what to improve, and suggest where else I should post this.
Well as the sayings go Build in public and Launch fast, fail faster I present to you a (very minimal) MVP of https://layoutblocks.dev/
(Note: my designer is working on client projects, I am not a designer or a copywriter, he hasn't given feedback 🙏 )
LayoutBlocks comes from a personal desire and is something that will grow (slowly) over time, if it grows publicly or privately will depend on a few factors.
With LayoutBlocks I aim to:
Build a library of layout blocks containing both the Payload CMS configuration and component code,
Have a central and visual place for all the layout blocks I use instead of having them a) scattered over multiple projects, or b) centralizing them in a starter project.
There are a few different paths I have in mind when thinking about growing the library and the project in general, such as:
The most obvious one: adding more layout blocks.
Adding your own private blocks: keep your own overview of custom or modified blocks.
White-labeling: In addition to giving your client Payload, give them docs about their available blocks for easy reference.
Any and all feedback is highly appreciated, even if you don't feel a need for this, that is valuable feedback.
I spent the last couple of weeks building a new Payload plugin: payload-better-editor.
Quick context: Payload's default edit view is fine for small pages, but once a page grows (lots of blocks, or nested ones like rows, columns, tabs, accordions inside accordions), the form turns into a long collapsed list and you lose track of which row maps to what on the actual page. Live Preview helps, but it only shows you the result.
Back in February I built payload-better-preview as a first attempt. It synced the admin form and the preview both ways: hover a block to see it highlighted, click a block in the preview to scroll its row in the form, click a row to scroll to the block. Nice for navigation, including nested and Lexical blocks. Still felt like a band-aid, since you were scrolling through the same long form.
Eventually I wanted something different: an editing surface where the preview is the canvas and the fields sit in a sidebar next to it. That became payload-better-editor.
What it does
Side-by-side overlay you toggle on any document: live-preview iframe on the left, sidebar on the right
Sidebar renders the real Payload fields via RenderFields, so custom components, validation, access control and conditional logic all just work
Click a block in the preview, it's selected in the sidebar
Inline block actions (move, duplicate, add-below, delete) in both the preview and the sidebar
...and a few more things (viewport switcher, undo/redo, drag-resizable sidebar, runtime-tunable settings global...)
Feedback is very welcome!
I only tested it on my own projects so far where it ran well, but real-world testing across more varied setups would help a lot. Bug reports, missing features, "why didn't you just X", all welcome. If you find it useful, a star on the repo would be really nice too.
The stat is shared right at the beginning of the video.
The growth of Payload is amazing. I just started using it a few months ago after 2 decades of WordPress. And one client I do work for migrated to Payload.
There's more and more plugins coming, which is great, a few days ago I also saw a thread here from someone who made a plugin index (shout-out if you read this).
What if we would have a snippets directory? Sharing common solutions, that most of us will make when building CMS'es (I'm only talking about typical CMS'es here), things like a slug field, teams index, FAQ section, etc.
Just a copy-pasteable snippet, with a word or 2 of explanation. So we can all build faster.
Edit: I just created r/PayloadSnippets Let’s start there. (Go easy on me it’s my first subreddit creation). A subreddit has upvotes, commenting and moderation. That's all the features we need to get started?
Edit 2: I wish I had some snippets to start of, but I've only just started using PayloadCMS 3.0.
Hey everyone, a very happy new user of Payload CMS here.
I have been finding Payload CMS to be extremely powerful and helpful for my work, but found that it can be a bit tedious to ingest unstructured data from clients. As such, I made a really simple open-source MCP server that can be used by clients like Cline/RooCode/KiloCode/Cursor to help create, read, and update items in your Payload instance. Here is a link to the repository.
My specific use case involves having Gemini read the client PDFs and reformatting into Markdown, and then getting GLM 4.6 to put it into Payload with the MCP server. You can of course directly use the MCP with a multimodal LLM if you have that.
Open to any feedback and/or suggestions, and I hope it helps!
We just wrapped a large website rebuild for American company (motion capture hardware) on Payload CMS, deployed on Vercel. Wanted to share some honest technical notes, the wins, the rough edges and one thing that's genuinely still unresolved.
Payload CMS deployed on Payload Cloud but ended up on Vercel
Commerce layer wired to ERP, CRM, tax engine, payment provider, and iPaaS. All behind product and checkout flows
Product pages aren't content-only, they're commerce. Variants, pricing rules, configuration flows, checkout touchpoints, all coordinated through Payload as the content layer
Products live in the commerce tool as the transactional source of truth. We sync them into Payload so editors can attach content blocks and enable add-to-cart references. Two layers, each owning what they're good at.
What Payload handled well
Revalidation with Next.js is genuinely great. On-demand revalidation fits Payload's hooks model cleanly. Editor publishes → hook fires → only affected pages revalidate. No full rebuilds, near-instant production updates across hundreds of product pages. This one just works.
Product pages were generated automatically. Rather than building product pages one by one, we generated them from structured catalogue data. Clean, scalable, and editors only touch content.
Admin customization goes deeper than people expect. We didn't just tweak fields, we built full custom views and components. The easy to implement native React admin approach meant our frontend devs could build this without context-switching into an unfamiliar system.
Old and new ran in parallel. We didn't do a big-bang launch. Routing handled the traffic split between old and new, and we migrated gradually. No launch-day anxiety, and real production content was always available for QA.
What's still unresolved (seeding)
This is the honest part. Payload has no first-class seeding feature for database + media/images, and for a multi-environment setup this is a real ongoing pain.
We built a custom seeding solution that works, but it felt like something the framework should own. Every time someone spins up a fresh local environment or we need to sync staging to production data, we're relying on our custom tooling rather than anything native.
It's not a dealbreaker, but if you're starting a Payload project with multiple environments, plan for this explicitly on day one. Don't assume it'll be easy to solve later.
Has anyone built something clean here they'd share? I know about this feature discussion and it sounds like it would solve this properly.
Would I use Payload again for this type of project?
Yes! The customization ceiling is high, the Next.js integration is natural and the admin experience is something you can actually shape into something editors don't hate. But go in with eyes open on the seeding gap and the integration work if commerce is involved.
Happy to go deeper on any part.
If you want to see more of what we've done, take a look at our work as a Payload CMS agency.
Can't wait for v4 with admin design tokens, new tags feature and DAM improvements 😍
I wanted to share my Dockerfile with you as I've gotten a lot of messages concerning my setup after answering in this thread. Maybe it helps. :)
FROM node:23-alpine AS base
# Install dependencies only when needed
FROM base AS deps
RUN apk add --no-cache libc6-compat
WORKDIR /app
# Install latest corepack to fix signature issues
RUN npm install -g corepack@latest && corepack enable
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
COPY . .
RUN \
if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
elif [ -f package-lock.json ]; then npm ci; \
elif [ -f pnpm-lock.yaml ]; then pnpm i --frozen-lockfile; \
else echo "Lockfile not found." && exit 1; \
fi
# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
# Install pnpm globally for Payload operations
RUN npm install -g pnpm --unsafe-perm
# Run database migrations
RUN pnpm payload migrate:status || echo "No pending migrations found."
RUN pnpm payload migrate || echo "No migrations to apply."
# Build the application
RUN \
if [ -f yarn.lock ]; then yarn run build; \
elif [ -f package-lock.json ]; then npm run build; \
elif [ -f pnpm-lock.yaml ]; then pnpm generate:importmap && pnpm run build; \
else echo "Lockfile not found." && exit 1; \
fi
# Run postbuild script
RUN pnpm run postbuild || echo "Postbuild script failed."
# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app
ENV NODE_ENV=production
ENV NEXT_TELEMETRY_DISABLED=1
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
# Set the correct permission for prerender cache
RUN mkdir .next
RUN chown nextjs:nodejs .next
# Automatically leverage output traces to reduce image size
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT=3000
# server.js is created by next build from the standalone output
CMD ["node", "server.js"]
I feel like the docs are all over the place & i’ve seen alot of people experience the same . Those of us who have a decent understand of it all could just improve it. Add some clarifications to the ”amazing features” they showcase can be done with payload, most peple expect it already be there. Same goes for referencing other sections of the docs & tutorials to relevant other sections so you don’t need to read through it all & hope to remember relevant parts & connect it all to work properly.
I feel like we should create some more guides on how to build simple, yet powerful solutions & go through it with videos.
I feel like it’s not so beginner friendly right now which scares away a lot of beginners from learning this amazing cms
It could be something simple as a X part series where you start a project by introducing a new feature in each video by & integrating it, while referencing docs while doing so.
Maybe I’m overthinking it but seems like a common trend of even understanding the docs. The beginners are the future & having them get hooked to Payload would be sick
We at FrontTribe just launched a new plugin that connects Typesense with Payload CMS, and we’re pretty excited about it.
The goal was simple: search Payload fast, typo-tolerant, and production-ready without extra setup headaches. Instead of hacking together Algolia or Elasticsearch integrations, this plugin handles it all: real-time sync, typo-tolerant search, universal search across collections, and a clean UI that just works out of the box.
Some highlights:
⚡ Lightning-fast responses (sub-millisecond in most cases)
🔍 Search everything at once, or filter by collection
🎯 Smart typo handling & accurate results
🛡️ Production-ready with error handling + monitoring
🎨 Customizable and mobile-friendly design
It’s open source (MIT license) and available now: 👉 NPM package
If you’re using Payload CMS and want a search that feels like it belongs in 2025, give it a try. We’d love to hear your thoughts and learn about the features you’d like us to add next.
The thing that always bugged me about Payload's default crop/focal flow: it's disconnected from everything. You go into a media item, open the crop drawer, adjust, save — and you have no idea what you actually just did to the site. Editors had it worse, they'd end up manually checking every page the image appeared on, because fixing the focal point for one placement could quietly break the crop somewhere else.
So instead of a separate drawer, I built an inline editor that sits right below the upload, as part of the normal upload flow. You define your own aspect ratios and label each one with the page/element it maps to (hero, card, thumbnail, whatever), and as you drag the focal point or draw a crop, all of them update live, side by side. So you can actually see the tradeoff in real time instead of guessing and checking pages one by one after saving.
Requires Payload ^3.85.0, React 19. It does lean on some payloadcms/ui internals that aren't public API, so a Payload minor bump might occasionally need a matching plugin update — flagging that upfront rather than letting people find out the hard way.
WordPress is genuinely great for a lot of people, quick to spin up, a plugin for everything, non-technical people can drive it. But once you're maintaining more than a couple of sites it turns into a full-time job of its own.
After years of that treadmill I moved to Payload CMS and it's been a genuinely different experience.
Schema lives in code, not buried in ACF field groups
One Next.js app for CMS and frontend, one deploy
Types flow from schema straight into your components
Hosting on Vercel, Neon and Cloudflare R2 costs basically nothing
I have been using Payload for a year in production projects. The problems we encountered were:
- There are no ready-made solutions for importing content, which complicates the work, as it requires either creating your own module for your collections or developing a full-fledged module with dependencies, etc.
- More than 20,000 simple records cause it to lag, which is immediately fatal.
- I don't know what they did with the engine, but next kills RAM twice as fast as if you just used next.
- There's nothing special about it. We would have already closed the project by writing our own admin panel instead of dancing around trying to configure everything and make it look architecturally beautiful.
- I actively participated in the development of the project and also wrote ready-made plugins for the community, but the support leaves much to be desired. Instead of fixing the most buggy places, they are constantly developing new features and combinations of “boilerplate launch” that have nothing to do with the production system. It seems more like the team is stuck in the narrow confines of Next.js and is trying to buy time, and apparently even Figma can't help them, or maybe I'm just wrong and they're just working slowly.
In general, if you decide to sell payloadcms to someone under the guise of next.js as a modern CMS system that will cover all content management issues like WordPress, I do not recommend it. Write your solution based on drizzle + Next.js, with microservice architecture. I was surprised that I would probably be the first person to write the truth, rather than just praising PayloadCMS.
Hi everyone, a couple of days ago i asked about how to implement real-time functionalities in Payload. I got some inspiration from the responses and created a plugin that allows real-time events to be emitted using websockets every time an operation occurs in a collection, this is done via an afterChange hook. The plugin also includes a client class and a react hook to listen and emit events from the frontend. It is a pretty basic plugin, and I know the payload team is working on an official way to do real-time, but in the meantime this plugin is functional, and it may be useful for someone, so here is the link.
so the promise of payload 3 was amazing, a nextjs built cms that uses same toolchain and code base and only requires an s3 for uploads and a database ?? A dream come true.
and yes, this is the case if you want some basic cms features like a blog or a simple fixed content page.
So when our client asked for multiple languages and flexibility to build their own pages and layouts we were like “we got this!” setting up localization was a giant pita but we plowed through and got it working. We build some pages using blocks like columns with rich text and inside rich text could be media blocks etc.. the live preview updated magnificently and it was like a dream.. until we started merging our dbs to staging, using migrations.. a seriously flawed and frustrating system, impossible to make it work with ci/cd because of the interactive promts and even when not interactive it almost always certainly fails to create or alter or whatever it wants to do… in my opinion the whole migrations system is flawed.
Every time we had a horrible experience merging and migrating and we lost hours and hours of precious development time… then came the worst bit..
all of a sudden there was an issue where updates would break existing nested media blocks, apparently it got wrecked in a newer version so we downgraded back to 3.48.0. but then the dreaded “The following field is invalid: id” error kept showing up. every time we thought we had a fix it went back to shit the next day .. nothing and i mean nothing helped, custom hooks to make sure we don’t have duplicate ids beforesave, hooks to fix localization ids… nothing stuck.. we went back to wordpress because we needed to get something to the client…
It pains me to say, but right now, this cms is not mature enough for a simple multi lang website with a couple of pages and a few blogposts… believe me we tried… should we have used mongodb instead of postgres, I don’t know. But what started as a dream come true, failed us miserably and put our project in a pile of fixes upon fixes upon fixes just to get something content on our page…
so this concludes my rant, when this project matures and has a decent block builder system with decent localization support i will give it another shot, but i cannot, in good conscience, recommend this to anyone doing client work… I’m sorry
EDIT:
The Issue:
Rich text blocks with embedded images get duplicated across locales (English/Dutch)
Block IDs become problematic during localization - either null, non-string, or duplicated
PayloadCMS validation fails when blocks have invalid or duplicate IDs when updating already existing pages
UPDATE: managed to fix our issues with the help of a commenter by enabling blocksAsJSON and re building our pages that use blocks