Can I use Sanity CMS with Next.js Partial Prerendering (PPR)?

Yes, but since PPR is experimental, you must wrap all dynamic Sanity data-fetching components in React Suspense boundaries to prevent the static shell from bailing out.

Does next-sanity support Next.js 15 and PPR?

Yes, next-sanity is designed for the App Router; however, you must manually ensure that dynamic functions like draftMode() are used within deferred components.

Why is my Sanity content not streaming with PPR?

This usually happens if the fetching logic is not identified as dynamic or if the component is not wrapped in a Suspense boundary, causing Next.js to render it during the initial static pass.

Sanity+Nextjs 15 Ppr

Compatibility analysis and integration guide

Sanity

Nextjs 15 Ppr

Compatible

Score:85/100

Highly compatible but requires wrapping dynamic Sanity fetches in Suspense boundaries to leverage Partial Prerendering effectively.

Technical Analysis

Sanity CMS and Next.js are technically highly compatible, but Partial Prerendering (PPR) introduces a specific architectural requirement. PPR works by generating a static shell and streaming dynamic holes. When fetching from Sanity, if you use dynamic functions (like draftMode(), cookies(), or headers()) or set cache: 'no-store', Next.js needs to know which parts of the tree are dynamic.

To make this work, you must ensure your Sanity fetching components are wrapped in a boundary. If a Sanity fetch is executed in a component that is part of the static shell without a boundary, the entire route may opt out of PPR and revert to fully dynamic rendering. For Visual Editing (Stega), ensure the preview client is only instantiated within these dynamic segments to maintain optimal build-time performance.

Known Issues (2)

1Static Shell De-optimization

If Sanity data is fetched in a top-level layout or component without a Suspense boundary, the static shell cannot be generated, forcing the whole page to dynamic rendering.

Workaround

Always wrap components that call 'client.fetch' with dynamic parameters or 'draftMode()' in a <Suspense fallback={<Skeleton />}> boundary.

2Draft Mode Streaming Conflicts

Enabling Next.js Draft Mode triggers a dynamic segment which can behave inconsistently with PPR if the cookie check is performed outside of a deferred component.

Workaround

Isolate the 'draftMode().isEnabled' check inside a component that is intentionally deferred via Suspense.

Best Use Cases

E-commerce product pages with static Sanity descriptions and dynamic inventory streaming.
Marketing sites with static layouts and dynamic, Sanity-driven 'Live Preview' capabilities.
Personalized landing pages where the hero section is static but the content grid streams from Sanity based on user segments.
Content-heavy blogs using PPR to serve an instant header/footer while the Sanity-sourced article body streams in.

Frequently Asked Questions

Share this Badge

Add this compatibility badge to your GitHub README or website.

GitHub README (Markdown)

[![Sanity + Nextjs 15 Ppr](https://devradar.dev/api/v1/badge/sanity-cms-with-nextjs-15-ppr.svg)](https://devradar.dev/check/sanity-cms-with-nextjs-15-ppr)

Website (HTML)

<a href="https://devradar.dev/check/sanity-cms-with-nextjs-15-ppr"><img src="https://devradar.dev/api/v1/badge/sanity-cms-with-nextjs-15-ppr.svg" alt="Sanity + Nextjs 15 Ppr" /></a>

Direct Badge URL

https://devradar.dev/api/v1/badge/sanity-cms-with-nextjs-15-ppr.svg

Get Started

Architecture isn't a gamble.
It's a calculation.

Eliminate incompatible technologies and build a defensible tech stack.

Launch Architect Wizard

No assumptions. No account required. Deterministic validation.