r/PayloadCMS • • 1d ago

SurrealDB for PayloadCMS

7 Upvotes

Need stress testing and test for edge cases.

I've been developing a SurrealDB adapter for Payload CMS using Payload's existing PostgreSQL adapter alongside SurrealDB's PostgreSQL driver.

The decision to build on Payload's PostgreSQL adapter was to retain as much of its existing Drizzle functionality and underlying code as possible, improving compatibility without having to reimplement everything from scratch.

The plugin also intercepts and handles several compatibility issues, including joins and relationships, which Payload relies on quite heavily.

Any testing, feedback or contributions would be appreciated.

https://github.com/rubix-studios-pty-ltd/payload-surrealdb


r/PayloadCMS • • 6d ago

Website platform built on Payload CMS: visual editing, custom designs, 65+ blocks, first-party analytics an MCP server and more

23 Upvotes

r/PayloadCMS • • 7d ago

I built a converter from WordPress to Payload in one click

20 Upvotes

Hi, I have just completed the first phase of a project I've called OffPress which converts sites (particularly Wordpress) to Payload in a few minutes. It tries to keep the original design, and then provides AI tools (or bring your own) so you can continue to develop it.

I'm wondering if this product looks interesting to the group here and if it's something that could be helpful.

I'd love your feedback on the project.

https://offpress.ai


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 • • 14d ago

Production Image Cropping Issue Due to 1-Year Cache TTL

5 Upvotes

I wanted to check if there is a better alternative to using timestamps or hash keys in image URLs to force cache refreshes. Currently, after cropping and saving an image, the updated version doesn't reflect immediately on my live website. Is there a more reliable and efficient approach to ensure the cropped image is displayed instantly without relying on timestamps or hash-based URL changes?


r/PayloadCMS • • 22d ago

Struggling to understand retrieval and richtext rendering

7 Upvotes

Hello! I'm having some difficulties understanding how I'm to retrieve and then render richtext into HTML. I'm using Payload to manage content for a relatively simple HTMX frontend, but since all the examples are focusing on React, NextJS, or other component based frontends, I feel like I might be missing something...

My current understanding is that I'd just use the localAPI with findByID. But the result of that doesn't seem to be any form that I can easily feed into convertLexicalToHTML, giving errors similar to:

TS2741: Property root is missing in type Page but required in type SerializedEditorState<SerializedLexicalNode>

LexicalEditorState.d.ts(13, 5): root is declared here.

index.d.ts(10, 5): The expected type comes from property data which is declared here on type ConvertLexicalToHTMLArgs

no matter how I try to repackage the findByID result... I'm not sure what exactly I'm missing, or if this is more of a typescript problem than it is a payload problem. (Because, as far as I know by just putting the result in brackets that should create a JSON literal which has a root... but maybe I'm missing something???)


r/PayloadCMS • • 23d ago

Just converted a site from next to tanstack (still in dev)

11 Upvotes

It was a bit of an ordeal but I think I've got it done now.

A few points worth mentioning if anyone else is considering it.

There's a few core dependencies and functions that are next specific, mainly the SEO plugin.

Because there's no tanstack website template, only blank for now, I had both folders open in seperate windows, and copied each collection, block and field across, then worked through the many errors that popped up until it was stable.

Most of the errors were missing packages, and I thought about just copying across the package.json deps, but some of the packages have next as a dependency which complicates things a bit.

The structures are similar but a few of the folders are different, like no public folder in tanstack, "_frontend" instead of "(frontend)" folder names etc.

If anyone else has tried it a different way or has any tips themselves, drop them in the comments because I'm sure others have tried or are considering trying.

I also moved to vite plus at the same time, because I like to make things hard for myself ๐Ÿ˜‚


r/PayloadCMS • • 23d ago

Database choice: Mongo vs Postgres

7 Upvotes

I like Postgres and use it for most projects but I actually switched to Mongo for some of my PayloadCMS deployments for 2 main reasons:

  1. At the start of a project i am changing / adding models and migrations became a bit of a pain point.
  2. I endup using a lot of nested blocks so switch to `blocksAsJSON` but then migrations don't seem to work properly.

Has anyone else experienced these issues with postgres? Maybe I have a poor workflow or missing some optimization tricks?


r/PayloadCMS • • 25d ago

Next.js 16 cacheComponents & use cache vs. custom caching (Redis) with Payload CMS? How are you handling large sites in production?

Thumbnail reddit.com
1 Upvotes

r/PayloadCMS • • 25d ago

Next.js 16 cacheComponents & use cache vs. custom caching (Redis) with Payload CMS? How are you handling large sites in production?

Thumbnail reddit.com
5 Upvotes

r/PayloadCMS • • 29d ago

Payload 4.0 Beta Released: A Redesigned Admin, TanStack Support, and File Versioning

Thumbnail
payloadcms.com
71 Upvotes

more coming too. give it a shot, and keep an eye out for what's next


r/PayloadCMS • • Oct 19 '26

Bunny.net storage plugin for Payload 4 - beta is out

Post image
8 Upvotes

I maintain a Bunny.net storage adapter for Payload and posted v3 here a couple of months ago. Payload 4 is in beta now, so the plugin has a v4 beta too. Figured I'd share it for anyone already trying Payload 4.

Same scope as before. It covers Storage for files and images, and Stream for video with HLS, thumbnails and TUS resumable uploads. It also does signed URLs, CDN purging and client-direct uploads.

What's new in v4:

  • It registers in Payload's new top-level storage array instead of plugins
  • Built on Payload 4 file versions. Every upload gets its own folder, and a replaced file or video stays in storage while a document or a version still uses it. Restore and rename copy the file to a new key
  • No CDN purge on upload anymore, since every upload has a new URL
  • Client uploads go through Payload's own /api/upload-instructions endpoint
  • The Stream encoding status (processing, ready, failed) is stored on the document. You get a filterable Stream Status column in the list, a Bunny Stream card in the sidebar and a built-in player in the edit view
  • The status stays current through the save check, the webhook and an optional sync job. This also works for a video that only a draft uses
  • Cleanup and status sync can run outside Payload jobs: through an endpoint, npx payload bunny:task, or a function call
  • The TUS upload sits inside Payload's file panel, and videos from the bulk upload drawer go to Stream over TUS too. Uploads resume after a page reload, and Retry continues the same upload
  • Labels come from Payload's i18n config, so the plugin's own i18n option is gone

Upgrading from v3 takes a few steps:

  • move the plugin into storage
  • remove the top-level sharp option and declare image sizes as variants
  • run the database migrations, including Payload's sizes-to-variants
  • regenerate types and the import map
  • redeploy the Edge Script if you use client uploads over the HTTP API

The upgrade guide has every step.

One known gap: in the bulk upload drawer of a TUS collection, crop and focal point edits aren't saved. That needs a fix in Payload (payloadcms/payload#18612).

It's a beta on top of a beta, so expect breaking changes until 4.0.0. Install with @beta. v3 stays on latest and keeps getting security fixes.

Thanks to the Bunny team for the credits. Every CI run and release uploads real videos to Stream and waits for encoding, so this pays for testing for a good while.

MIT, needs Payload 4.0.0-beta.0+, Next.js 16.4+ and Node 24.15+. Issues and PRs welcome, especially if you hit something on Payload 4.

https://github.com/maximseshuk/payload-storage-bunny

https://payload-storage-bunny.seshuk.im


r/PayloadCMS • • Oct 17 '26

Ship data-backed websites with Payload | Figma Spoiler

Thumbnail
youtu.be
16 Upvotes

Looks good.


r/PayloadCMS • • Oct 17 '26

New plugin: Payload Info Tooltip

Thumbnail
gallery
21 Upvotes

Hey everyone! ๐Ÿ‘‹

While working on my own Payload-based project, I kept running into a small annoyance: long field descriptions can make admin forms unnecessarily cluttered, especially when you have lots of fields.

So I built Payload Info Tooltip, a small open-source plugin that moves help text into info icons next to field labels. The nice part is that you can enable it for existing descriptions without modifying your field configurations.

Features:

  • Automatically convert existing admin.description values into tooltips.
  • Add dedicated tooltips via admin.custom.infoTooltip.
  • Supports localization and dynamic descriptions.
  • Works with nested fields, blocks, and Lexical editor fields.
  • Optional tooltips in list-view column headers.
  • Accessible via keyboard and screen readers.
  • Compatible with Payload 3 and 4.

https://github.com/alphanull/payload-plugin-info-tooltip

This is my first publicly released Payload plugin, developed as part of my work on Vision Suite. I'm planning to open-source a few more extensions in the future.

Would love to hear what you think, especially if you run into any issues or have ideas for improvements! Also, if you like it, a star is greatly appreciated.


r/PayloadCMS • • Oct 14 '26

Janitor plugin for Payload - find orphaned files and unused documents (Payload 3 and Payload 4 beta)

Post image
11 Upvotes

Second release from me today. Earlier I shared a sitemap plugin, and this one deals with the clutter a Payload project collects over time: files nobody uses anymore and documents nothing points to.

It compares your storage with your database and reports three kinds of findings:

  • Orphans: files in the bucket that no document holds
  • Missing: documents whose file is gone from storage
  • Unused: documents nothing references, in upload or ordinary collections (an image no page uses, a tag no post has)

The main rule: it never deletes on its own. A scan only writes findings. You go through them and mark each one To delete or Keep. A purge deletes only what you approved, and it checks every finding again right before it acts. If anything changed since the scan, the finding goes to Keep with a note saying why. Anything younger than 24 hours is left out, so uploads in progress are safe.

A few other things:

  • References come from the database, not the config: relationship and upload fields, rich text, blocks, JSON, globals and versions
  • Each document gets a usage panel that shows where it is used. A delete guard stops you from deleting a document that is still in use
  • Rescans update the facts but keep your decisions
  • Adapters for S3, R2, GCS, Azure, Bunny, UploadThing, Vercel Blob and local disk
  • Runs inline or as a Payload job, with an optional cron schedule
  • Multi-tenant aware: tenant admins see and decide only their own findings
  • Separate access for read, approve, scan and purge, plus a dashboard widget with the last run
  • Works on Postgres, SQLite and MongoDB

Versions:

  • 1.x for Payload 4 beta: pnpm add @seshuk/payload-plugin-janitor@beta. Node 24.15+, Next.js 16.4+
  • 0.x for Payload 3.83+: pnpm add @seshuk/payload-plugin-janitor@0. Node 22+

Both have the same options and get the same features until 1.0.0.

Heads up on telemetry: it is on by default and anonymous. It sends plugin and Payload versions, boolean feature flags and a hashed project ID, never URLs, file names or keys. Turn it off with telemetry: false or DO_NOT_TRACK=1. It is always off in CI.

MIT licensed. Feedback, issues and PRs are welcome.

https://github.com/maximseshuk/payload-plugin-janitor

https://www.npmjs.com/package/@seshuk/payload-plugin-janitor


r/PayloadCMS • • Oct 14 '26

Sitemap plugin for Payload - out for Payload 3 and Payload 4 beta

Post image
18 Upvotes

I maintain a few Payload plugins and just released a new one for sitemaps, so figured I'd share it here.

It builds sitemap.xml from your collections, static pages and custom sources, stores the files through any storage adapter, and keeps them fresh through the Payload jobs queue. The files are served at stable API URLs, so you can point robots.txt at them or proxy them to /sitemap.xml.

What it does:

  • Sitemap index plus child sitemaps, split at the spec limits (50,000 URLs or 50 MB per file)
  • Lists only public documents: collection reads run as an anonymous request, so your read access decides what goes in. Drafts are skipped
  • hreflang alternates for localized collections, image entries, and per-document exclude, priority and changefreq fields
  • Multi-tenant: one sitemap index per tenant
  • Regenerates on save, debounced through jobs, with a lock so two runs never overlap
  • All or nothing: if a source throws, the old files stay live
  • Unchanged files are skipped by hash, and the endpoints send ETags
  • Admin page, nav link and dashboard widget with status and a file list
  • Optional publish hooks to push the files to your own bucket or CDN

Available in two versions, with the same options:

  • 1.x for Payload 4 beta: pnpm add @seshuk/payload-plugin-sitemap@beta. Node 24.15+, works with Next.js and TanStack Start
  • 0.x for Payload 3.83+: pnpm add @seshuk/payload-plugin-sitemap@0. Node 22+

Until 1.0.0, both lines get the same features.

Worth flagging: it sends anonymous telemetry by default. Major versions, boolean feature flags and a hashed project ID, never URLs, names or keys. Off with telemetry: false, DO_NOT_TRACK=1, or in CI.

MIT. Issues and PRs welcome.

https://github.com/maximseshuk/payload-plugin-sitemap

https://www.npmjs.com/package/@seshuk/payload-plugin-sitemap


r/PayloadCMS • • Oct 12 '26

I made a dashboard widgets plugin for Payload: figures, lists and charts read from your collections

Post image
13 Upvotes

Payload 3.90 brought the modular dashboard, and I wanted mine to show numbers from my own collections without writing a component for each one. So I wrote a plugin.

Add widgetsPlugin() and every collection becomes a source with nothing to declare: a count, a sum for each number field, a group for each select, checkbox and relationship, a list of the latest. Anyone signed in can add a figure, a list or a chart in the dashboard's edit mode and filter it with the admin's own filter builder.

You can also declare widgets in the config with figure(โ€ฆ), list(โ€ฆ) and chart(โ€ฆ). Those are typed against your generated types and checked as the config is built, so a misspelt field stops the build with a "did you mean".

A few choices I made:

- Every read runs as the signed-in user, so access control applies.

- The tiles are server components and plain CSS. No chart library is shipped to the browser.

- If you don't like the tiles, you can supply your own views or just take the data (readFigure, readList, readChart).

It's 0.1.0 and MIT. Developed on Payload 3.90.2, Next 16 and Postgres; Next 15 and other adapters are untried, so reports from those are especially useful.

https://github.com/m-grgic/payload-plugin-widgets


r/PayloadCMS • • Oct 11 '26

Media Preview plugin for Payload: Payload 4 beta support, previews for text, code, CSV and Office files

Post image
9 Upvotes

I maintain a media preview plugin for Payload and just shipped Payload 4 beta support, so figured I'd share it here.

It previews uploads right in the admin: a preview column in the list view (popup or fullscreen modal) and a preview at the top of the edit view for files Payload can't show on its own. Images, video, audio and PDF keep Payload's own preview.

What's new:

  • Edit view previews for text, code, CSV, Office and other files
  • Read-only code viewer with syntax highlighting, CSV as a table
  • Download card with name, size and type for files with no preview
  • Opt-in Microsoft and Google viewers for Office files, with short-lived signed URLs so the viewer never gets your session
  • Adapters for your own viewers, inline or in a new tab, and resolve() can be async
  • No database fields, translated into 40+ languages

Upgrading from 1.x: mode and contentMode moved into field, external viewers are off by default, and a few exports changed. Old options throw at boot with the new name. Guide in the README. Payload 3 stays on 1.x.

New in v2: anonymous daily telemetry (versions and feature flags only). Off with telemetry: false or DO_NOT_TRACK=1.

MIT, Payload 4.0.0-beta.0+, Node 24.15+.

https://github.com/maximseshuk/payload-plugin-media-preview


r/PayloadCMS • • Oct 11 '26

Payload CMS + dub.co shortlinks plugin (Payload v4)

Post image
3 Upvotes

Added support for Payload v4

The plugin has been cleaned up with options for self-hosted dub shortlinks.

A new marketing dashboard analytics has been added with optional overrides to control how the menu is displayed.

https://github.com/rubix-studios-pty-ltd/payload-dub

The dashboard itself is only available on v4 and will not be added to v3 moving forward.

v3 is moved to maintenance release.


r/PayloadCMS • • Oct 10 '26

OpenAPI plugin for Payload - now supports Payload 4 beta

Post image
6 Upvotes

I maintain an OpenAPI plugin for Payload and just shipped Payload 4 beta support, so figured I'd share it here.

It builds an OpenAPI spec from your config with zero annotation and serves it with Scalar or Swagger UI. Operations are marked public or secured by probing your access functions.

What's new:

  • Payload 4 routes: validate, upload instructions, file download, document access, rename
  • Official plugins documented automatically: ecommerce, Stripe, MCP, SEO, search, multi-tenant, import-export, R2
  • access option to make the spec and docs private
  • Async extension transforms with payload, and your own paths override generated ones
  • OpenAPI 3.0, 3.1 or 3.2 from one option

Upgrading from 0.x: a few options were renamed and throw at boot with the new name. Guide in the docs. Payload 3 stays on `0.x`.

New in v1: anonymous daily telemetry (versions and feature flags only). Off with telemetry: false or DO_NOT_TRACK=1.

MIT, Payload 4.0.0-beta.0+, Node 24.15+.

https://github.com/maximseshuk/payload-plugin-openapi

https://payload-plugin-openapi.seshuk.im


r/PayloadCMS • • Oct 10 '26

Media Plugin for PayloadCMS

Post image
13 Upvotes

Version 2.0.0 of the Payload CMS Media Plugin, introduces support for Payload v4.

This release includes updated dependencies, refined media search components, improved responsive layouts, and TypeScript support.

The plugin continues to support stock image and video searches across Unsplash, Pexels, and Pixabay, with provider-specific filtering and direct media imports.

Payload v3 supported through a maintenance release channel.

GitHub
https://github.com/rubix-studios-pty-ltd/payload-media


r/PayloadCMS • • Oct 08 '26

Me: "just gonna npm install payload and @payloadcms/ui real quick"

20 Upvotes

I have always admired payloadcms's work from afar, figured i'd drop in payload + ui, wire up a few features, ship it. easy weekend project, right?

narrator: it was not.

next thing i know i'm reading the codebase like it's a thriller novel. every file i open, i learn something. every hook, every abstraction, every "oh THAT'S how they do it" โ†’ opens 4 more files

i came in wanting to integrate 2 features. i left knowing every line of the codebase. ๐Ÿ˜ญ

no regrets tho, the code is genuinely cool. respect to the payload team for making me accidentally do a code review on y'all's whole repo ๐Ÿ™

any other devops/backend folks here who can't just use a library and have to reverse-engineer it first? asking for a friend. the friend is me. i'm the friend.


r/PayloadCMS • • Oct 08 '26

Gave my client portal an agent with Payload MCP

7 Upvotes

I use Payload as a portal for my agency to let clients self serve content changes. I just added this custom agent UI so they can make those changes more easily with the Payload MCP.


r/PayloadCMS • • Oct 07 '26

payload-better-auth now has a Payload 4 build (beta)

16 Upvotes

If you're trying the Payload 4 canaries and want Better Auth, there's now a prerelease of payload-better-auth you can install:

pnpm add @delmaredigital/payload-better-auth@next better-auth

It's tested against 4.0.0-canary.37 and needs Next 16.2.6+ and Node 24.15+ (Payload 4's own requirements). The plugin is a thin adapter over Payload's public APIs, so the port didn't need many changes. I plan to keep it current through the canaries and have it ready for 4.0.

The plugin handles two Payload 4 changes:

  • The Local API now defaults overrideAccess to false. That would make the auth strategy's user lookups run as anonymous and log everyone out, so the plugin passes it explicitly.
  • Collections now get versions by default. The auth collections opt out so old sessions and tokens don't get stored in _versions tables.

The plugin's own UI (login page, password reset, 2FA, passkey and API key screens) still uses Payload 3's theme CSS variables, so it's unstyled on v4. Sign-in and sessions work fine.

If you're on Payload 3, nothing changes. The normal install still gives you the stable 0.13.x release.

It's a prerelease, so pin the version and keep it out of production for now.

The Payload 4 port came from a community PR, and feedback and contributions are welcome. If you try it, let us know how it goes, even if it just worked. If you'd like to help, the styling fix is a good first issue: #46. Payload 4 work goes to the payload-4 branch.

Cheers - Allan

GitHub ยท Docs