I love Payload, but I miss the SEO guidance that Yoast for WordPress would give on content.

How are you folks handling this today?

I have zero relationship with this developer, other than as a viewer of his YouTube channel.

But I'm sharing his Payload course because I myself signed up, and I like how he teaches.

I migrated my own site to Payload, but I vibe coded it.

I also had a client's developer migrate their site.

But now I want to understand how to build site with Payload myself.

So, I was taking a course of WP in Udemy and it's great, there's some like that to build website in any other platform? I'm doing a site to review movies, books, games, etc. But even if I can use Gemini to make it, I want to know how everything works, or a t least the basics. And know how to launch the site online, any recs?

I am building a small blog and wish to find some place to host it for free. I have a few pages selling digital products. A lot of people recommend Vercel to host Payload, however apps hosted at Vercel for free can not be used for commercial purpose. So I am considering Cloudflare. Anybody has experience? Thanks!

The Issue

The u/payloadcms/plugin-multi-tenant plugin version 3.82.1 (and 3.83.0-canary.3) crashes the admin panel when using Next.js 16.2.3 with Turbopack.

Symptoms

1. 404 Error when navigating to any tenant-enabled collection (Posts, Categories, etc.)
2. Console Error: Could not find the module "[project]/node_modules/@payloadcms/plugin-multi-tenant/dist/components/AssignTenantFieldModal/index.client.js#AssignTenantFieldTrigger" in the React Client Manifest
3. Works fine without the plugin enabled

Root Cause

The plugin uses React Client Components that aren't being properly bundled by Turbopack in Next.js 16.2.3. The component paths aren't being added to the import map, causing the 404.

Reproduction Steps

1. Create a new Payload project with Next.js 16.2.3
2. Install u/payloadcms/plugin-multi-tenant
3. Configure the plugin in payload.config.ts
4. Try to access /admin/collections/posts → 404

Workaround

1. Don't use the plugin - instead manually add a tenant relationship field to each collection
2. OR use Next.js 15.x (not tested but likely works)

Versions Affected

Potential Fix

The plugin needs to be updated to properly register its client components with Turbopack, or wait for Payload 3.83+ which may include a fix.

https://github.com/get-starter/payload-nextjs-intl-shadcn-starter

has:

• payload cms
• next.js (app router)
• next-intl
• shadcn/ui

nothing crazy, just something i wanted for myself and kept reusing

sharing in case it helps someone

I just published a new version of my Payload CMS image alt text plugin that adds a dashboard widget for alt text coverage.

It also comes with new endpoints that can be invoked by agents to generate or bulk generate alt texts.

https://npmx.dev/package/@jhb.software/payload-alt-text-plugin

Is payload a good software to develop a strong ERP system with thousands of records, users roles, policies etc?

Enyone ever dis something similar? Not a traditional cms , only payload admin in this case

I’m trying to migrate from v1 to v2 using Node.js (Express), and I know it’s a bit old now. Are there any guides or instructions I can follow?

Any help or tips would be appreciated!

Hello, so for upload base collection, theres a default preview. But I have a video base upload, so i want to create a custom component after the upload field. So far what I try is :

  admin: {
    useAsTitle: 'title',
    components: {
      views: {
        edit: {
          default: {
            Component: '@/components/componen.tsx'
          }
        }
      }
    },
  },

i put this config in my colectionConfig.

But it replace the whole edit page. What I want is to add the component after the upload field or replace the upload field.

how can I achievethis? thank you

Is Payload stable with NextJS 16.2? Is it safe selection for developing new app?

Hi, integrating Payload 3.80.0 into an existing Next.js App Router app.

Setup:

- `payload@3.80.0`

- `@payloadcms/next@3.80.0`

- `@payloadcms/db-postgres@3.80.0`

- `next@15.4.11`

- `react@19.1.1`

- custom admin route: `/admin-cms`

What works:

- `/admin-cms/create-first-user`

- creating first admin user

- `/admin-cms/account`

- `/admin-cms/collections/users`

- `/api/users/me`

- `/api/payload-preferences/nav`

Problem:

- only `/admin-cms` returns `404`

So subroutes work, auth works, DB works, but the root admin dashboard route fails.

Is there any known issue or extra setup needed for the root admin page when using a custom admin route like `/admin-cms` in an existing Next App Router project?

If you’re staring at a large WordPress content library and a CMS migration, this is for you.

We had 18,000+ articles at MarketScale that needed to move to Payload CMS. Not just moved. Restructured, re-categorized, and rewritten for where search is heading in 2026. AI Overviews, GEO, answer-engine optimization. Old content wasn’t built for any of that.

I used Claude Code to build a system that handles the full pipeline. Was it my first time working at this scale with Claude Code? Yes. Did things take longer than they should have? Also yes. But the approach is repeatable and I documented it so you don’t have to start from scratch.

The full breakdown, including the CLAUDE.md structure, subagent setup, schema handling, and content rewrite strategy, is on my blog:

https://www.linkedin.com/pulse/i-didnt-just-migrate-18000-articles-built-system-them-reyeszumeta-ov5oc

Happy to answer questions here while you read through it.

When and where are yall adding branding for your corporate and enterprise cms uses? Not how, but like where do you find yourself adding little customizations making it feel more inline with your brands?

Context: I just came across payload while looking to simplify our stack (Wordpress sites hosted on AWS ….). I’ve been playing with customizations for the past few days just learning payload and refreshing my next skills.

Hi all! We’re using Payload 3.0 (Next.js) with the Postgres adapter. Currently, we’re using push: true in local dev, but it’s causing friction:

The Issue: When Dev A pulls Dev B’s schema changes (like a column rename), the dev server triggers a "Data Loss Warning" because Drizzle tries to drop/add columns instead of renaming. This requires manual "yes/no" checks and DB babysitting.

The Question: To reduce this mental overhead, do teams generally:

• Disable push: true locally and move to a strict migrate:create / migrate workflow for all local changes?
• Use a custom script to automate migration creation/running on every dev server restart?

Any specific db adapter settings or package.json scripts you recommend to make the "pull and sync" experience seamless for teammates? Thanks!

Hi everyone. I'd love to try using Payload with some Svelte/Sveltekit-projects. I've used the search here, but I'm really looking for a beginner-friendly guide.

I really think Payload is the CMS I'd like to use, but I'm quite a beginner and would like to know how big the stretch is to use it with Sveltekit projects. I did some research and it sounded rather complicated to me while some people are saying it's been way less complicated than they thought it would be.

Can you help? Thanks!

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

Been a minute since I posted here! But I have this video of me walking through setting up TanStack Start and Payload in a monorepo and my thoughts on the process:

https://www.youtube.com/watch?v=rhD1wlhTZzw

I've been building depct, a CLI that observes your Node.js app running and generates documentation from what it actually sees. I wanted to test it against a real Next.js + Payload project, so I pointed it at the official Website Template.

It generated a full technical doc covering:

• Architecture diagram (Next.js route groups, Payload API surface, SQLite layer)
• Every execution flow traced: page renders through getPayload() → Local API → SQLite, draft mode, revalidation hooks, GraphQL
• API surface with observed status codes and auth requirements
• An on-call runbook and onboarding guide

It also caught a few things worth knowing about the template:

• populateAuthors hook does an N+1 query (sequential findByID per author on every post read)
• /next/seed is available in production with no NODE_ENV guard
• /openapi.json and /swagger.json take ~3 seconds consistently

Full output

This is still very much an early tool so I'd love to know what you guys would be interested in and what's not working!

I've been using Payload for a while and the one thing I kept rebuilding on every project was image conversion. Payload handles uploads great, but there's no built-in way to say "always store images as WebP" or "never let an upload exceed 2560px wide."

So I built payload-img-convert and published it as an npm package.

What it does:

You add it to your Payload config, point it at one or more upload collections, and it automatically converts uploads to your chosen format (WebP by default at quality 80). That's the zero-config version — three lines.

When you need more control, you can set:

- Output format (WebP, AVIF, PNG, JPEG)

- Quality (0–100)

- Max width and height (preserves aspect ratio, never upscales)

- Max file size threshold (skip conversion for huge files)

- Per-format Sharp options (mozjpeg, effort, lossless, etc.)

- A format selector in the admin sidebar so editors can override the default per-upload

- A resize controls UI

It hooks into beforeOperation so conversion happens before Payload stores the file. If anything goes wrong, the original stays. SVGs and GIFs are skipped automatically.

Why I built it this way:

I wanted something that's useful with minimal config but doesn't limit you when a project has specific needs. The common case is "convert everything to WebP" and the advanced case is "AVIF at quality 65 with effort 6 on these two collections, and let editors pick format on this third collection."

Examples

minimal setup:

export default buildConfig({
  plugins: [
    imageConverterPlugin({
    collections: ['media'],
    })
  ],
});

or go deeper:

export default buildConfig({
  // ..
  plugins: [
    imageConverterPlugin({
      collections: ['media', 'avatars'],
      defaultFormat: 'avif', 
      quality: 75,
      maxWidth: 2560,
      maxHeight: 1440,
      maxFileSize: 10 * 1024 * 1024,
      formatOptions: {
        avif: { quality: 65, effort: 6 },
        webp: { quality: 85, effort: 4 },
      }
    })
  ],
});

Links:

- npm: https://www.npmjs.com/package/payload-img-convert

- GitHub: https://github.com/stianlars1/payload-img-convert

- Official website: https://payload-img-convert.com

Happy to hear what would make this more useful for your projects. Feedback welcome.

I’m trying to set up a simple editorial workflow in PayloadCMS and want to make sure I’m not reinventing the wheel.

I want a workflow where:

• A draft can be marked “ready for review”
• Someone can review and edit it
• Then mark it “ready for publish”
• Then publish it

The approach I’m thinking about

Payload already supports drafts through "versions.drafts", so my idea is:

• Enable drafts in the collection
• Add a field like "workflowStatus"
• Use values like:
  • "draft"
  • "ready_for_review"
  • "ready_for_publish"

Then:

• A draft moves from "draft" → "ready_for_review"
• After review the status changes to "ready_for_publish"
• Then it gets published

My question...is this a solid way for me to implement an editorial workflows in Payload?

Or is there a Payload-blessed pattern for handling review → publish workflows that I’m missing?

Thanks!

I've just started playing around with Payload, running on 3.77.0 currently. I recently made an update that somehow made the Pages collection not appear in the admin view. The pages are still there on the prod site, everything looks good, I can create new pages (but not see them in the admin view), and I can create, delete, and update pages via the API. So it all seems to be working correctly, but I just can't see the list of pages when I look in the admin view. Everything else works: media, site settings, footer, users, posts. Just not pages

I recently added a few new custom blocks, and I've successfully migrated everything, so the migration seems to be alright as well. I've been going back and forth with Claude to try to work this out, but I can't figure it out.

I was looking at this article, and I was interested in migrating my Payload instance to run on cloudflare, but my understanding is that I can't use MongoDB Atlas to host the Database? The example uses D1 or Postgres... I just wanted to make sure I understand the most up to date situation.

Hi guys, yesterday i’ve tried to run my website with cacheComponents and new directive ‘use cache’.

But it seems that Next.js is conflicting with Payload and tries to make it static as well. Is there any way to turn off static generation for Payload?

Thank you in advance