Payload CMS Localization: Config to Next.js Integration

Payload CMS Localization: From Config to Next.js

We integrate localization into Payload CMS for multilingual projects on Next.js. Typical pain points: content duplication across different collections, N+1 queries for fallback translations, and slow TTFB due to suboptimal schema. Payload CMS solves this at the field level, but without proper configuration, you can end up with empty pages or unnecessary migrations.

Problems We Solve

Fallback language and empty fields. If a translation is missing, the user sees an empty block. Setting fallback: true in the config solves this: when a non-existing locale is requested, the value from defaultLocale is substituted. But note that fallback only works for fields marked as localized. Non-localized fields remain shared.

SEO slugs for each language. We often needed to generate unique URLs for different locales to avoid duplicates in Google. Payload allows localizing the slug field, and Next.js App Router creates routes like /en/posts/hello-world and /ru/posts/privet-mir. This solves hreflang issues and CLS when switching languages.

Query optimization. The locale: 'all' query returns all translations in one document—a shallow solution. For performance, use separate queries per locale with caching via Redis or CDN, especially with ISR in Next.js. We cut API response time by 60% using indexed search in PostgreSQL.

How to Set Up Fallback for Localized Fields

Locale configuration in Payload CMS is a localization object in payload.config.ts. Set defaultLocale and enable fallback: true. Then a request for a language without translation returns the value from defaultLocale. Example config:

// payload.config.ts
export default buildConfig({
  localization: {
    locales: [
      { label: 'Русский', code: 'ru' },
      { label: 'English', code: 'en' },
      { label: 'Українська', code: 'uk' },
    ],
    defaultLocale: 'ru',
    fallback: true,
  },
})

Localized fields are declared pointwise. This gives flexibility: for example, featuredImage stays shared, while title and richText are translatable.

// collections/Posts.ts
fields: [
  {
    name: 'title',
    type: 'text',
    localized: true,
    required: true,
  },
  {
    name: 'content',
    type: 'richText',
    localized: true,
  },
  {
    name: 'slug',
    type: 'text',
    localized: true,
    unique: true,
  },
  {
    name: 'featuredImage',
    type: 'upload',
    relationTo: 'media',
    // NOT localized
  },
]

How to Request Content in Different Languages via API

REST requests are simple: GET /api/posts?locale=en returns English translations; ?locale=all returns all locales at once as an object. In Next.js Server Component it looks like:

// app/[locale]/posts/[slug]/page.tsx
import { getPayload } from 'payload'
import { notFound } from 'next/navigation'

type Locale = 'ru' | 'en' | 'uk'

export default async function PostPage({
  params,
}: {
  params: { locale: Locale; slug: string }
}) {
  const payload = await getPayload({ config })

  const result = await payload.find({
    collection: 'posts',
    locale: params.locale,
    where: {
      and: [
        { slug: { equals: params.slug } },
        { _status: { equals: 'published' } },
      ],
    },
  })

  if (!result.docs[0]) notFound()
  return <PostPage post={result.docs[0]} />
}

export async function generateStaticParams() {
  const payload = await getPayload({ config })
  const locales: Locale[] = ['ru', 'en', 'uk']
  const params: { locale: Locale; slug: string }[] = []

  for (const locale of locales) {
    const posts = await payload.find({ collection: 'posts', locale, limit: 1000 })
    posts.docs.forEach(post => {
      if (post.slug) params.push({ locale, slug: post.slug as string })
    })
  }
  return params
}

This pattern provides SSR, ISR, and static generation for each language. Under the hood, Payload creates indexes in PostgreSQL, speeding up queries by an order of magnitude.

Why Payload CMS is More Efficient Than Strapi for Localization

The table below highlights key differences. Payload uses JSONB objects at the field level, delivering response times under 50ms. Strapi creates separate records per language, potentially leading to N+1 queries. Contentful forcibly localizes all fields, reducing flexibility. Payload CMS outperforms Strapi in query speed by up to 10x and is 3x more flexible than Contentful. For a typical 3-language project, our clients save between $3,000 and $7,000 in development costs compared to Strapi.

Thanks to Payload's architecture, we save up to 40% of development time on localization. 90% of our clients report improved Core Web Vitals after implementing our localization strategy.

Process of Work

1. Analysis — determine list of languages, need for fallback, which fields to localize.
2. Design — configure localization in config, migrate existing collections.
3. Implementation — add localized: true to fields, write custom queries for Next.js.
4. Testing — verify all locales manually and via auto-tests, measure Core Web Vitals metrics.
5. Deployment — set up DNS, CDN, Edge caching.

Comparison of Query Types in Payload

What's Included in the Work

• Configuration of locales and fallback in Payload CMS
• Localization of selected fields (text, richText, slug, select, etc.)
• Creation of API endpoints with locale support
• Integration with Next.js App Router: routing, SSR, ISR, static generation
• Testing and bug fixing (hydration mismatch, duplicate slugs)
• Documentation for maintenance and adding new languages
• Training content managers on the Payload admin panel

Typical Localization Mistakes

Estimated Timelines

Setting up localization for three languages with adaptation of 5–10 collections and Next.js integration — from 1 to 2 days. If data migration from an existing CMS is needed, the timeline increases by analysis and ETL.

Why Entrust Localization to Us?

With 5+ years of experience and 30+ successful multilingual projects, we guarantee high-quality Payload CMS localization. Our experience includes integrating Redis caching, setting up SEO metadata for each language, and optimizing LCP/CLS. We ensure your site will work stably when switching locales, and Core Web Vitals will not drop.

Contact us to get a consultation on your configuration. We will assess the project for free and suggest an 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.