What does a Payload CMS integration do on a marketing site?
Payload is an open-source, TypeScript-first CMS that installs into a Next.js app instead of running as a separate hosted service. You define your content in code, and Payload gives you an admin panel, a database layer and APIs from that config. The marketing site reads the same content directly, without calling another vendor.
- Collections and globals: pages, posts, case studies, authors and team members as collections; navigation, footer and site settings as globals.
- Admin panel: a React admin served from your own app, usually at /admin, with field validation, help text and custom components.
- Local API: server components query the database directly in the same process, so pages don't make a network round trip to fetch content.
- Drafts and versions: editors save drafts, schedule changes and roll back to earlier versions.
- Rich text: a block-based editor where you control which formats and embedded blocks editors can use.
- Access control and hooks: rules for who can edit what, and code that runs on save, such as revalidating a page.
The main reason to choose Payload is ownership. Your content sits in your own Postgres, MongoDB or SQLite database, there's no per-seat CMS bill for editors, and the whole stack deploys as one app. New to the idea of a separate CMS? Start with our headless CMS explainer for non-developers.
Does Payload work with Next.js, Framer and Webflow?
Payload is built for Next.js and is a poor fit as the CMS behind a Framer or Webflow site. Both builders have their own CMS inside the visual editor, so using Payload with them means syncing content across through an API, which leaves you with two copies of everything.
Next.js | Framer | Webflow | |
|---|---|---|---|
How Payload connects | Installed in the same app, queried with the Local API | Content synced into Framer's CMS by a plugin or script | Content synced into Webflow's CMS through its API |
Live preview | Yes, on the real page | No, editors preview in Framer after sync | No, editors preview in Webflow after sync |
Where content lives | Your own database | Two systems | Two systems |
Hosting | One deployment for site and CMS | Framer hosting plus a Payload server | Webflow hosting plus a Payload server |
Our recommendation | Strong fit | Use Framer's CMS | Use Webflow's CMS |
The exception is a company already running Payload for its product or docs that wants a Framer or Webflow marketing site to show some of that content. We'd scope that sync carefully. For most startups, the choice is really between a visual builder with its own CMS and a coded Next.js site with Payload. Our guide to Webflow vs Framer vs WordPress vs Next.js helps with that decision, and Next.js development explains when code is worth it.
How do we set up Payload with Next.js?
We set Payload up as part of the build, starting with what your editors need to change and ending with a handover they can run without us.
Model the content
We define collections, globals and fields around your real content, such as use cases, posts and authors, rather than around one layout.
Choose the database and storage
Postgres, MongoDB or SQLite for content, and an object storage adapter for images and files, picked to match where the site is hosted.
Configure the admin
Clear labels, descriptions, validation, required alt text and grouped navigation so editors find things without a guide.
Build the front end
Next.js server components read content through the Local API, and rich text renders through the same components as the rest of the design.
Wire drafts, preview and revalidation
Editors preview unpublished changes on the real page, and an after-change hook revalidates only the pages that changed.
Train and hand over
A walkthrough with your editors, plus short notes on adding pages, posts, redirects and images.
We've written up what we learned setting up Payload CMS for a marketing site in production, and our guide to live preview in headless CMS setups covers the step most teams skip.
Where should a Payload site be hosted?
A Payload site needs a host that runs a Next.js server, a database and file storage, because the CMS isn't a hosted service you rent. That's the trade for ownership: someone has to own the infrastructure. In practice, this is less work than it sounds, since the site and admin deploy together.
Designify's own site runs on Next.js and Payload on Cloudflare Workers, so we know that path first hand. Vercel, container hosts and your own server all work too, each with different trade-offs on database location, cold starts and cost. Our guide on where to host Payload CMS compares the options. Hosting and database plans are billed by those providers and change often, so check their current pricing pages before you commit.
Payload, Sanity or Contentful for a Next.js marketing site?
Payload suits teams that want the CMS inside their own app and database, with no CMS subscription. Sanity and Contentful suit teams that would rather rent a hosted content platform and not think about servers. All three can power a fast Next.js site; the difference is who runs what.
Pros
- Payload: content stays in your own database, so there's no vendor lock-in on your data
- Payload: no per-editor CMS fees, since the software is open source
- Payload: one codebase and one deployment for the site and the admin
- Payload: TypeScript types generated from your config, so content bugs show up in the editor
Cons
- Payload: you own hosting, backups and upgrades
- Payload: real-time multi-editor collaboration is less mature than hosted platforms
- Payload: changing the content model means a code change and a deploy
- Payload: for a two-page site with no blog, any CMS can be more than you need
Our comparisons of Sanity vs Payload and Contentful vs Sanity vs Payload vs Strapi go deeper, and the Sanity integration page shows how we set up the hosted alternative.
What are the common Payload setup mistakes?
Most Payload problems appear after launch, when the people editing the site aren't the people who built it. These are the ones we design out.
- Fields named after layouts: a field called 'hero subtitle 2' breaks at the next redesign. Model content, not sections.
- Unlimited page-builder blocks: too many loosely defined blocks let editors build off-brand pages.
- No revalidation hook: cached pages don't update after publishing, and editors stop trusting the CMS.
- Images on local disk: uploads stored on the server's file system vanish on serverless hosts. Use an object storage adapter.
- No backups: owning the database means owning its backups. Schedule them before launch.
- Missing SEO and redirect fields: no place for titles, descriptions, social images or redirects after a URL changes.
What does a Payload CMS website cost?
A Next.js site with Payload is part of our website package: $8,000 fixed for up to six pages, then $500 per extra page. That covers copy, custom design, the content model, admin setup, the Next.js build and animation. Hosting, database and storage are billed by those providers.
Moving content from another CMS is separate work. Migration is scoped on the intro call, and we include redirects and SEO checks in any migration we take on. Our guides to Webflow to Next.js and Payload and Contentful to Payload cover what a move involves, and headless CMS development covers larger builds. The next step is a free 30-minute call.
















