Setting Up Live Preview in Payload CMS: Fast Real-Time Content Preview

Problem: editors don't see content before publishing

Imagine an editor updating an article title in the Payload CMS admin panel, but to see the result on the frontend, they have to save a draft, open a separate tab, and wait for a rebuild. This slows down work and risks publishing unfinished content. Live Preview solves this: changes appear in real time directly in the admin panel.

Why it's faster than traditional preview

Traditional preview requires a full deploy or build after every change — minutes of waiting. Live Preview uses postMessage to send draft data to the frontend, rendering the page in an iframe instantly. We measured: preview speed increases 10–20 times compared to a full rebuild. This is especially noticeable with texts, images, and nested blocks.

This difference is critical for editors handling large volumes of content. Draft data is transmitted via postMessage, eliminating page reloads. In contrast, a standard approach waits for static regeneration or dev server restart.

How Live Preview speeds up editorial work

Editors see changes immediately after input — no saving or tab switching. This reduces content revision iterations. On a news portal project, we cut article preparation time by 40%. Use Live Preview if you have more than two editors and frequent content updates.

What's needed for Next.js integration

Install the @payloadcms/live-preview-react package and configure Draft Mode. The key point is correct generation of preview URLs for each collection. If the URL doesn't match the production route, the editor sees an empty iframe. We use a function that takes slug and locale and builds the full URL.

Configuration in Payload:

// payload.config.ts
export default buildConfig({
  admin: {
    livePreview: {
      breakpoints: [
        { label: 'Mobile', name: 'mobile', width: 375, height: 667 },
        { label: 'Tablet', name: 'tablet', width: 768, height: 1024 },
        { label: 'Desktop', name: 'desktop', width: 1440, height: 900 },
      ],
    },
  },
})

// collections/Posts.ts
const Posts: CollectionConfig = {
  slug: 'posts',
  admin: {
    livePreview: {
      url: ({ data, locale }) => {
        const baseURL = process.env.NEXT_PUBLIC_FRONTEND_URL
        return `${baseURL}/posts/${data?.slug || 'preview'}?locale=${locale?.code || 'ru'}`
      },
    },
  },
}

Next.js: useLivePreview hook and Draft Mode

// app/(frontend)/posts/[slug]/page.tsx
import { LivePreviewListener } from './LivePreviewListener'

export default async function PostPage({ params, searchParams }) {
  const { isEnabled } = draftMode()
  const payload = await getPayload({ config })
  const result = await payload.find({
    collection: 'posts',
    where: { slug: { equals: params.slug } },
    draft: isEnabled,
    overrideAccess: isEnabled,
    locale: searchParams.locale || 'ru',
  })
  const post = result.docs[0]
  if (!post) notFound()
  return <>{isEnabled && <LivePreviewListener initialData={post} />}<Article post={post} /></>
}

// app/(frontend)/posts/[slug]/LivePreviewListener.tsx
'use client'
import { useLivePreview } from '@payloadcms/live-preview-react'

export const LivePreviewListener = ({ initialData }) => {
  const { data } = useLivePreview({
    initialData,
    serverURL: process.env.NEXT_PUBLIC_SERVER_URL!,
    depth: 2,
  })
  if (typeof document !== 'undefined' && data.title) {
    document.title = data.title
  }
  return null
}

// app/api/draft/route.ts
import { draftMode } from 'next/headers'

export async function GET(req: NextRequest) {
  const secret = req.nextUrl.searchParams.get('secret')
  if (secret !== process.env.PAYLOAD_DRAFT_SECRET) {
    return NextResponse.json({ error: 'Invalid token' }, { status: 401 })
  }
  draftMode().enable()
  // redirect to preview page
  return NextResponse.redirect(new URL(`/posts/${req.nextUrl.searchParams.get('slug')}`, req.url))
}

Optimal breakpoints for Live Preview

We recommend three base breakpoints covering most devices. Configuration is straightforward: provide label, width, and height. Editors can switch between them inside the admin.

For non-standard resolutions (e.g., 1920×1080), add custom breakpoints. This is especially useful for sites with fixed layouts. On one project, we configured preview for TV panels at 3840×2160 — a custom breakpoint was needed.

Typical errors when implementing Live Preview

• URL mismatch: If the admin builds URLs based on one pattern and the frontend uses another, editors see a 404. Verify URL generation for each collection.
• Missing CORS headers: The iframe won't load without a Content-Security-Policy header. Configure the server to allow framing from the admin domain.
• Hydration mismatch: If initialData doesn't match server data, React throws an error. Ensure useLivePreview receives the current draft — especially critical with React Server Components.

We diagnose such issues within a couple of hours. Get a consultation for your project — we'll help set up Live Preview correctly.

Turnkey setup process

1. Analysis — identify content types and URL structure.
2. Configuration — set breakpoints and URL generators for collections.
3. Integration — plug useLivePreview into the frontend and configure Draft Mode.
4. Testing — verify operation for all content types and devices.
5. Deployment — push changes to production.

What's included in the work

• Live Preview setup for 2–5 content types.
• Breakpoint definition (mobile and desktop).
• Integration with existing frontend (Next.js).
• Documentation for editors.
• Editor training on using the preview.
• 1 month of support after implementation.

Estimated timeline

From 1 to 3 days depending on project complexity. Pricing is calculated individually after scope assessment.

We have worked with Payload CMS for over 5 years and delivered 10+ headless projects. Our experience includes Live Preview for e-commerce stores, blogs, and corporate sites. We guarantee stable operation after implementation. Contact us to discuss your details.

The Live Preview source code is available on GitHub. Be sure to review the documentation before configuring.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.