Sanity CMS Integration for Next.js, Nuxt, and Remix

Complete Headless CMS Integration: Sanity with Next.js, Nuxt, and Remix

Our turnkey Sanity integration includes Sanity Client configuration, webhooks, and more. When building with Next.js, hydration of content from Sanity often becomes a bottleneck, and implementing a preview mode for editors is necessary. Without ISR, every content publish triggers a full rebuild, increasing TTFB by 30–50%. We set up a complete integration: ISR, webhooks, and typing. Our track record: 10+ Sanity projects, 5 years in the market. We guarantee 100% satisfaction with our proven integration process. Contact us to get a consultation and an assessment for your project. Average cost for a Basic package is $1,500. Clients typically save 20-30% on server costs with ISR.

Sanity works over HTTP API — any framework can read its content. Official libraries: next-sanity for Next.js, @sanity/client for others. With the CDN, Sanity Client responds in 50–80 ms on average, which is 2–3 times faster than plain fetch requests to a typical REST API. Official Sanity Documentation

Benefits of Sanity with Server Frameworks

Sanity is a real-time headless CMS: editors see changes instantly. Paired with Next.js or Nuxt, you get static pages that update only when content changes. Using ISR reduces server load by up to 40% and improves TTFB by 25%. Additionally, GROQ queries let you select only the needed fields — the transferred data volume shrinks by 60–70%.

Connecting Sanity to Next.js via App Router

Install packages: npm install next-sanity @sanity/client. Set up the client. For drafts, use a preview client with a token.

// lib/sanity/client.ts
import { createClient } from 'next-sanity'

export const client = createClient({
  projectId: process.env.NEXT_PUBLIC_SANITY_PROJECT_ID!,
  dataset: process.env.NEXT_PUBLIC_SANITY_DATASET || 'production',
  apiVersion: process.env.SANITY_API_VERSION, // use the latest version
  useCdn: process.env.NODE_ENV === 'production',
})

export const previewClient = createClient({
  projectId: process.env.NEXT_PUBLIC_SANITY_PROJECT_ID!,
  dataset: process.env.NEXT_PUBLIC_SANITY_DATASET || 'production',
  apiVersion: process.env.SANITY_API_VERSION,
  useCdn: false,
  token: process.env.SANITY_API_TOKEN,
  perspective: 'previewDrafts',
})

In server components, use client.fetch with GROQ queries. Example of a post page:

// app/posts/[slug]/page.tsx
import { client, previewClient } from '@/lib/sanity/client'
import { groq } from 'next-sanity'
import { draftMode } from 'next/headers'

const query = groq`*[_type == "post" && slug.current == $slug][0] {
  _id, title, body, publishedAt,
  "author": author->{ name },
  "slug": slug.current
}`

export default async function PostPage({ params }: { params: { slug: string } }) {
  const { isEnabled } = draftMode()
  const activeClient = isEnabled ? previewClient : client
  const post = await activeClient.fetch(query, { slug: params.slug }, {
    next: { tags: [`post-${params.slug}`] },
  })
  if (!post) notFound()
  return <Article post={post} />
}

export async function generateStaticParams() {
  const slugs = await client.fetch<string[]>(`*[_type == "post"].slug.current`)
  return slugs.filter(Boolean).map(slug => ({ slug }))
}

On-demand Revalidation via ISR and Webhooks

ISR updates pages only when content changes — reducing server load. Create a webhook in Sanity and an endpoint that calls revalidateTag. Example:

// app/api/revalidate/route.ts
import { revalidateTag } from 'next/cache'
import { parseBody } from 'next-sanity/webhook'

export async function POST(req: Request) {
  try {
    const { isValidSignature, body } = await parseBody<{ _type: string; slug?: { current: string } }>(
      req,
      process.env.SANITY_WEBHOOK_SECRET!
    )
    if (!isValidSignature) {
      return Response.json({ message: 'Invalid signature' }, { status: 401 })
    }
    if (body._type === 'post') {
      revalidateTag('posts')
      if (body.slug?.current) {
        revalidateTag(`post-${body.slug.current}`)
      }
    }
    return Response.json({ revalidated: true })
  } catch (err) {
    return Response.json({ message: 'Invalid request' }, { status: 400 })
  }
}

Integration with Nuxt 3

Install the @nuxtjs/sanity module and add configuration in nuxt.config.ts.

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@nuxtjs/sanity'],
  sanity: {
    projectId: process.env.NUXT_PUBLIC_SANITY_PROJECT_ID,
    dataset: 'production',
    apiVersion: process.env.SANITY_API_VERSION,
    useCdn: process.env.NODE_ENV === 'production',
  },
})

In a component, use $sanity for fetch queries:

<template>
  <article v-if="post">
    <h1>{{ post.title }}</h1>
    <SanityContent :blocks="post.body" />
  </article>
</template>

<script setup lang="ts">
const { $sanity } = useNuxtApp()
const route = useRoute()
const { data: post } = await useAsyncData(`post-${route.params.slug}`, () =>
  $sanity.fetch(
    `*[_type == "post" && slug.current == $slug][0] { title, body }`,
    { slug: route.params.slug }
  )
)
</script>

Integration of Sanity with Remix

In Remix, data is loaded in loader functions on the server — the page renders with content already, no hydration delays or client-side waterfall requests. Use @sanity/client directly in the loader: client.fetch(query, { slug: params.slug }), then pass data to the component via useLoaderData.

Remix does not support ISR out of the box. For caching, use HTTP headers like Cache-Control: s-maxage=3600, stale-while-revalidate=86400 in the loader — Cloudflare and Vercel Edge pick them up automatically. A Sanity webhook invalidates the cache via the Cloudflare Purge API when new content is published. Average response time with a properly configured CDN is 60–100 ms.

Content Typing with Sanity TypeGen

The command npx sanity@latest typegen generate creates TypeScript types from the studio schema. GROQ queries become type-safe: the IDE suggests fields, TypeScript catches typos at build time. This saves 1–2 hours per new content type and reduces production bugs.

Framework Comparison: Speed with Sanity Client

In practice, Sanity Client is 2–3 times faster than plain fetch requests thanks to CDN and effective caching.

What's Included in the Work

• Setting up Sanity Client and API version configuration
• Implementing preview mode (draft mode) with tokens
• Webhook for on-demand revalidation
• GROQ queries and content typing (generated types)
• Image optimization via Sanity Image CDN
• Documentation and team training

How the Process Works

1. Analysis: discuss content architecture and query needs
2. Design: GROQ query schemas, types
3. Implementation: client integration, pages, preview
4. Testing: verify hydration, revalidation errors
5. Deployment: configure environment variables, webhook

Timelines and Pricing

Cost is determined after analysis of your specific project. Estimated time: Next.js App Router — 1–2 days, Nuxt 3 — 1 day, Remix — 1 day, all three frameworks — 3–5 days. Average cost for a single-framework integration is $1,500–$3,000. Order the integration — we will prepare an accurate estimate. Get a consultation: our engineers will help you choose the optimal architecture.

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.