Headless CMS Localization: 10 Multilingual Platforms Compared

Headless CMS localization is how a CMS keeps several language versions of the same content, falls back to a default language when a translation is missing, and delivers the right locale through the API. If you want a shortlist: Storyblok for editor-friendly translation with a visual editor, Sanity for flexible modelling, Payload or Strapi if you self-host, and Drupal for large multilingual sites with many languages.

Locale limits and prices below come from vendor pages we opened on 27 October 2026. Where we could not open a page, the text says so. For the full market, see the headless CMS platform directory and our headless CMS guide.

What does multilingual support mean in practice?

Three questions decide it. How are translations stored: inside one entry per field, or as separate linked entries per language? What happens when a translation is missing: an empty page, or a fallback to another locale? And who does the work: editors in the CMS, an agency through a connector, or a machine translation step?

The cost side matters just as much. Several SaaS vendors cap locales by plan, so a ninth market can force an upgrade. Open source platforms rarely cap locales, but the translation interface is only as good as the configuration your team builds.

How we evaluated

We compared ten platforms on the storage model, fallback behaviour, API locale handling, plan limits and translation workflow. We read docs for Storyblok, Strapi, Directus, Payload, Sanity and Prismic, and pricing pages for the hosted vendors. Contentful, Hygraph and DatoCMS localisation docs and Drupal’s module list were not reachable or not specific, so those entries are partly general knowledge and flagged.

Multilingual CMS comparison table

PlatformHow translation worksTranslation integrations foundHostingFree tierBest for
StoryblokField-level, folder-level or space-levelLokalise, Smartling, Phrase, CrowdinSaaSYes, 2 localesMarketing teams with several markets
ContentfulLocales per space with field-level valuesLokalise, Crowdin, Smartling, Transifex, PhraseSaaSYesEnterprise multi-site setups
StrapiLocales per content type or fieldBuilt-in AI translation (Growth); Crowdin and DeepL via communitySelf-host or cloudOpen sourceNode.js teams
PayloadPer-field with fallbackCommunity plugins only, Crowdin among themSelf-hostOpen sourceNext.js teams
DirectusTranslations junction collectionDeepL and Crowdin (beta) via extensionsSelf-host or cloudOpen sourceRelational data with translations
SanityField-level arrays or document-levelTransifex, Smartling, Phrase, CrowdinSaaSYes, unlimited localesFlexible modelling
HygraphField-level localesLokalise, Crowdin, Smartling, DeepLSaaSYes, 2 localesLocalised GraphQL queries
DatoCMSLocalised fieldsCrowdin, AI Translations plugin with DeepLSaaSYes, 5 localesMulti-market sites on a budget
PrismicOne document per localeCrowdinSaaSYes, 2 localesMarketing sites
DrupalBuilt-in multilingual modulesTMGMT providers: DeepL, Lokalise, Smartling, PhraseSelf-hostOpen sourceLarge, complex multilingual sites

Storyblok

Storyblok offers three approaches. Field-level translation keeps one story with a version per language and suits similar page structures. Folder-level gives each language its own folder, so structure can differ per market, at the price of duplicated content. Space-level uses separate spaces for regional teams. You can combine them, for example a US folder with English and Spanish and an EU folder with four languages. The free Starter plan has 2 locales, as of October 2026. See Storyblok development.

Best for: teams with a mix of identical and market-specific pages. Skip if: you need more than 2 locales on a free budget.

Contentful

Contentful stores localised values per field across the locales you define in a space. It is a common choice for enterprise multi-market sites. We could not open its localisation docs today, so we do not quote locale limits or fallback rules; confirm them for your plan. See Contentful.

Best for: enterprise sites with established translation vendors. Skip if: you have not checked locale limits for your plan.

Strapi

Strapi enables internationalisation per content type and per field. Locales come from a list of over 500 ISO locales, and editors switch locale in the content manager, with a button to copy values from another locale. The REST API, GraphQL API and Document Service all accept a locale. The feature is free; AI translation needs a paid plan. The docs we read did not describe a fallback. See Strapi.

Best for: self-hosted sites with custom front ends. Skip if: you need built-in locale fallback.

Payload

Payload localises at field level with localized: true. You define locales and a default, and fallback is on by default and can be turned off per request. REST takes ?locale=, GraphQL takes locale and fallbackLocale arguments, and all returns every locale at once. Changing a field to localised on existing data can lose data, so plan a migration. Per-locale publish status is experimental. See Payload.

Best for: TypeScript teams who want locales in code. Skip if: editors need independent publishing per locale today.

Directus

Directus models translations with a translations field on the source collection, a hidden junction collection holding the translated fields, and a languages collection. A wizard can generate this. It is explicit and works well when you already have relational data. Locale fallback is not covered in the docs we read. See Directus.

Best for: teams with SQL data and several languages. Skip if: you want a one-click locale switch.

Sanity

Sanity supports field-level localisation, with an array of language values in one document, and document-level localisation, with one document per language linked by metadata. Plugins add the editor interface, and GROQ’s coalesce() provides fallback. Connectors exist for Transifex and Smartling. The free plan has unlimited locales, as of October 2026. See Sanity.

Best for: teams that want to choose their translation model. Skip if: you want a ready translation UI without plugins.

Hygraph

Hygraph supports localised fields, and its pricing ties locales to the plan: 2 on Hobby, 3 on Growth, up to 80 on Enterprise, as of October 2026. Webhook payloads include a localisations array. We did not reach its localisation guide. See Hygraph.

Best for: localised GraphQL projects. Skip if: you expect many locales on a mid-size budget.

DatoCMS

DatoCMS lists 5 locales on its free plan and charges 19 euros a month for each extra locale on Professional, as of October 2026. That is clear pricing for multi-market sites. We could not open its localisation docs, so fallback behaviour is unverified. We have no separate DatoCMS page.

Best for: several markets on a small budget. Skip if: content volume exceeds the free record limit.

Prismic

Prismic stores a separate document per locale, using codes like en-us, with alternate_languages linking the versions. Request a locale with the lang parameter, or * for all. The free plan has 2 locales and Medium has 5, as of October 2026. See Prismic.

Best for: marketing sites with independent per-locale pages. Skip if: you want one entry with many language fields.

Drupal

Drupal has multilingual modules in core for content, interface and configuration translation, and a long track record on sites with many languages and complex permissions. The docs index we opened did not list module names, so confirm the current set. See Drupal.

Best for: large organisations with many languages and strict governance. Skip if: you want a light, API-only CMS.

Translation and TMS integrations

Most teams do not translate inside the CMS. Copy goes out to a translation management system (TMS) such as Lokalise, Phrase, Crowdin, Smartling or Transifex, or through a machine translation API such as DeepL, and comes back as locale values. The connector decides how painful that loop is, so check it before you pick the CMS.

We looked in each vendor’s app directory and in the TMS catalogs in November 2026. A missing name in the table means we did not find a listed integration, not that one cannot be built. Every platform here has an API, so a custom sync is always possible; it is just code you then maintain.

  • Contentful’s marketplace lists Lokalise, Crowdin, Smartling, Transifex and Phrase. Hygraph’s marketplace lists Lokalise, Crowdin, Smartling and a DeepL app. Storyblok has apps for Lokalise and Smartling, and Phrase and Crowdin publish their own Storyblok connectors.
  • Sanity has official plugins for Transifex and Smartling, a Phrase plugin from the community, and a Crowdin connector built by a partner agency.
  • DatoCMS offers a Crowdin plugin and an AI Translations plugin that can call DeepL. The DeepL route needs a small proxy because of browser CORS rules.
  • Strapi ships AI translations as a Growth plan feature, off by default and billed in Strapi AI credits. Crowdin and a DeepL provider for the Translate plugin come from the community, so check who maintains them.
  • Payload and Directus rely on community work. Payload’s content translation plugins and its Crowdin sync are third-party; Directus lists DeepL extensions and a Crowdin connector in beta that does not sync multilingual collections.
  • Prismic connects to Crowdin through Crowdin’s store; we found nothing listed for the other TMS tools.
  • Drupal uses the Translation Management Tool (TMGMT) module family, with providers for DeepL, Lokalise, Smartling and Phrase.

Ask two questions about any connector. Does it send only changed fields, or the whole entry every time? And when a translator edits text in the TMS after an editor changed the source, which version wins?

Building a multilingual site with Next.js and a headless CMS

The CMS stores the translations. The front end decides how visitors reach them. On a React front end with Next.js, four parts do the work.

Locale routing. Keep the locale in the path, for example /de/pricing/, rather than in a cookie, so every language version has its own crawlable URL. In the App Router that is a [locale] route segment, with a check that sends visitors without a locale to a default one. The Pages Router still has a built-in i18n block in next.config.js for the same job.

Fetching by locale. Pass the route’s locale into every CMS query: ?locale=de for Payload’s REST API, a locale argument in Hygraph or Payload GraphQL, lang for Prismic. Use generateStaticParams to build each page once per locale.

Fallback. Decide what a missing translation returns. Payload falls back to the default locale unless you turn it off, Sanity needs coalesce() in GROQ, and Strapi and Directus need code on your side. A silent fallback shows English on a German URL, which is fine for a menu label and wrong for legal text.

hreflang. Every language version should list all the others. In the App Router, the alternates.languages field of the metadata API writes those link rel="alternate" tags, and the sitemap can carry the same pairs. Leave out locales whose page has no translation yet, or Google will index a fallback copy as a duplicate.

UI strings such as button labels usually live in the code, managed with a library like next-intl, while page content lives in the CMS. Keep the two locale lists in one config file so they cannot drift apart.

How to choose

Decide first whether markets share a page structure. If they do, field-level translation in Payload, Sanity or Storyblok keeps content aligned. If markets diverge, prefer document or folder level, as in Prismic, Sanity or Storyblok.

Then price the locale count you will have in two years, not today. SaaS plans cap locales; open source platforms do not, but you carry the hosting. If you want help with the model or the translation workflow, our headless CMS agency team can run it. Moving existing locales off a legacy CMS is a job for our headless CMS migration services.

Browse all headless CMS platforms

Global-ready solutions with multilingual and localization support

Filter the full directory by type, licence and hosting. The multilingual filter is selected by default.

Loading CMS systems...

Strapi

68,886 stars
8,724 forks
970 issues

Strapi is the leading open-source headless CMS. It's 100% Javascript, fully customizable, support TypeScript and developer-first. It saves API development time through a beautiful admin panel anyone can use.

API DrivenOpen SourceSelf Hosted+9

Ghost

50,059 stars
10,675 forks
51 issues

A fiercely independent platform for professional publishers. Headless Node.js REST API for developers, beautiful Ember.js admin client for editors. Used by Apple, NASA, Sky News, OpenAI & many more.

API DrivenOpen SourceSelf Hosted+4

Payload

36,650 stars
2,733 forks
381 issues

Payload is a free and open-source headless CMS aimed sharply at providing the best, developer-first experience possible to build out APIs and admin UI.

API DrivenOpen SourceSelf Hosted+3

Multilingual headless CMS FAQ

What makes a headless CMS good for multilingual sites?

Look for locale-aware content modelling, fallback rules when a translation is missing, a locale parameter in the API, and a workflow for translators. Field-level translation keeps structure shared, while document-level translation lets each market diverge. A good platform supports both, or lets you choose per content type.

Field-level or document-level translation?

Use field-level when every market shows the same page structure and only the text changes. Use document-level or folder-level when markets differ in layout, legal text or sections. Sanity and Storyblok support both approaches, and many teams mix them inside one project.

Which multilingual headless CMS is free?

As of October 2026, Sanity's free plan has unlimited locales, DatoCMS's free plan allows 5, and Hygraph's Hobby plan, Storyblok's Starter plan and Prismic's free plan each allow 2. Strapi, Payload and Directus are open source and set no locale cap in their docs, but you pay for hosting.

Which headless CMS integrates best with translation APIs?

Contentful and Hygraph list the most translation apps in their own marketplaces: Contentful has Lokalise, Crowdin, Smartling, Transifex and Phrase, and Hygraph has Lokalise, Crowdin, Smartling and DeepL. Storyblok has Lokalise, Smartling, Phrase and Crowdin. For self-hosted tools, Drupal's TMGMT module family covers DeepL, Lokalise, Smartling and Phrase.

How do I build a multilingual site with a React frontend and headless CMS?

Put the locale in the URL, such as /de/pricing, and pass it to every CMS query. In the Next.js App Router that means a [locale] route segment, a redirect for visitors without a locale, generateStaticParams for each locale, and hreflang links through the metadata alternates field. Decide in the CMS what a missing translation returns.

Does machine translation replace translators in a CMS?

No. Strapi, Sanity and others offer AI-assisted translation, which speeds up first drafts. Legal, product and brand copy still needs human review. With Strapi's AI translations the default locale becomes the source of truth, and saving it can overwrite manual edits in other locales, so set review rules first.

Testimonials

What our clients say

Direct feedback from teams we've shipped with.

HTML CSS Hugo +5

Alpina tech did a good job during the discovery phase of our project

4.9 / 5
J
John C. Delivery Manager Headless CMS rebuild and frontend integration
Strapi Next.js React +9

I had the opportunity to work with Alpina Tech and the experience was very positive. He successfully achieved the goals set, demonstrating talent and commitment at every stage of the work. Moreover, he was always attentive to my instructions and consistently available, which greatly facilitated communication and the de...

5.0 / 5
M
Michael A. Delivery Manager Rebuild Strapi Cloud CMS, migrate content, and integrate with Next.js frontend (Render)
Next.js React JavaScript +5

Alpina Tech is not only a very talented dev, but he's a fantastic partner who has a rich business acumen and is quick to complete anything you throw at him. He knocked out work in a single day that I wasn't expecting for a week. Will definitely work with him again.

5.0 / 5
D
David R. Technical Project Manager Fix Netlify Functions & Assessment Tool for Next.js Website
React Native React Node.js +7

Alpina Tech always responded promptly and got a lot done in the limited environment we had. If things weren’t clear, he’d message and make sure he has the scope right. I highly recommend him for full stack development.

5.0 / 5
J
James K. Technical Project Manager React Native + Node.js Developer for Collectibles App with GPT-4 Integration
UX/UI Design Figma Landing Pages +4

I had the opportunity to work with Alpina Tech on the design of several landing pages and a UI kit, and I couldn’t be happier with the results. He managed to deliver high-quality designs in a very short time. The landing pages were beautifully crafted, and the UI kit was exactly what we needed to streamline the project...

5.0 / 5
R
Robert N. Delivery Manager UX/UI design for landing + UI kit
React.js React Next.js +12

Working with Alpina Tech on a headless CMS project built with Strapi, Node.js, and Next.js was a great experience. His deep understanding of modern frontend frameworks, API development, and server-side rendering (SSR) ensured a smooth and efficient development process. Alpina Tech showcased excellent React.js and Next....

5.0 / 5
W
William P. Project Manager React Developer Needed for Headless CMS with Strapi, Shadcn, and TypeScript
Swift SwiftUI UIKit +8

We worked with Alpina Tech, a top-tier Apple ecosystem developer specializing in Swift, SwiftUI, UIKit, and Combine. Delivered a seamless, high-performance app with Core Data, iCloud Sync, AVKit, MapKit, and Push Notifications. Optimized for iOS, watchOS, and macOS, ensuring smooth performance and App Store compliance....

5.0 / 5
D
Daniel O. Delivery Manager Develop iOS mobile app
JAMstack Hugo Next.js +10

I hired Alpina Tech to build a custom Hugo website. He was a pleasure to work with. He took the time to understand exactly what I wanted at the beginning of the project, and he then proposed a much better way of achieving that. He communicated regularly, provided clear and timely updates, offered ongoing support with m...

5.0 / 5
M
Matthew M. Project Manager Installing a custom theme for Hugo website
Next.js React Sanity +7

Alpina Tech was incredibly helpful and a pleasure to work with! He not only assisted with improving the SEO of my startup but also fixed a challenging Sanity bug with great patience and professionalism. His expertise and attention to detail were invaluable, and he did an excellent job overall. Highly recommended!

4.9 / 5
A
Anthony L. Technical Project Manager SEO Technical Expert for Next.js & Sanity.io Blog Integration
UI/UX Design Figma Web Design +3

I had the pleasure of working with Alpina Tech on the UI/UX design for my public website, and I am extremely impressed with his work. He significantly expanded and improved upon the original design I already had, seamlessly integrating enhancements that perfectly matched the existing style. His ability to develop great...

5.0 / 5
B
Brian D. Delivery Manager UI/UX Designer for AI Startup
Jekyll JAMstack HTML +5

Working with Alpina Tech was a great experience. He is knowledgeable and delivers high-quality work. The agency boasts a wide range of talent, making it a good choice for various projects. Communication was consistently excellent, and Alpina Tech ensured that every aspect of the project worked as expected. The work was...

5.0 / 5
K
Kevin F. Project Manager Web Developer Needed to Convert Figma Landing Page Design to Jekyll Static Site
UI/UX Design Figma Landing Pages +4

Alpina Tech and the team have completed the design quickly and it looks great. They are very responsive and were able to quickly make adjustments that I have requested.

5.0 / 5
L
Lauren E. Delivery Manager Landing page and public site pages design
iOS Swift SwiftUI +3

Alpina Tech is awesome, he fixed a complicated bug on VPN iOS app in two hours.

5.0 / 5
R
Rachel Y. Technical Project Manager ASAP iOS Developer Swift/SwiftUI (Fix VPN Mobile App)
Hugo JAMstack HTML +3

Alpina Tech did an excellent job guiding us through the process and helping us achieve our project goals.

5.0 / 5
B
Brandon A. Project Manager hugo site work
GitHub Pages HTML CSS +4

Alpina Tech helped us launch a research project website. Thank you for being available on short notice!

5.0 / 5
E
Eric B. Delivery Manager Fix github.io page issue
Technical SEO Web Strategy Management

I had the pleasure of working with Alpina Tech on leadership and technical projects. The team is highly motivated, strategically minded, and has exceptional technical SEO expertise. Their approach significantly boosted our digital presence. I highly recommend Alpina Tech for engineering and leadership-driven projects –...

5.0 / 5
S
Steven T. CEO AT CLAWBUSTER GAME PROVIDER Leadership & Technical SEO Optimization
HTML CSS JavaScript +4

Alpina Tech demonstrates all the right qualities of a strong development team – deep frontend expertise, great communication, and a proactive work attitude. A reliable partner for any technical project.

5.0 / 5
S
Scott M. Delivery Manager Frontend Development & Collaboration
Web Development Frontend HTML +3

Alpina Tech is a very professional and reliable team. Working together on web projects was extremely successful. The team showed strong technical knowledge and excellent organizational skills.

5.0 / 5
J
Jonathan N. Business Analyst - Playtech Web Development Collaboration

Keep exploring

More on Headless CMS

Our team

The team you'll actually work with

We pair deep technical expertise with the kind of ownership you'd expect from your own in-house crew.

  • Same team from discovery to launch
  • Daily standups, Slack, and full transparency
  • Senior-only engineering, design, and QA
  • Long-term collaboration, not staffing
10+ years in the field
EU-based UTC+0 → UTC+3
Senior-only no juniors
Alpina Tech Team

Book a session

Let's just
{ Make it together! }

Learn how our services can improve your business processes, customer experience, and drive growth.

Schedule a meeting

Get a lightning-fast, SEO-optimized, high-performance web app for:

  • SaaS platforms
  • Marketplaces
  • Marketing websites
  • News portals
  • Catalogs & listings

Meeting agenda

  1. 01 Define goals & product scope
  2. 02 Quick technical SEO check-up
  3. 03 Outline your development roadmap
30 min
Web conferencing details provided upon confirmation.

Meet our team

Team member 1Team member 2Team member 3Team member 4Team member 5Team member 6

Success!

Form was sent to our team. We will contact you soon.

Get Your Estimate

Tell us about your project and we'll get back to you with an estimate.

Your Name
Solutions
Contact Email
Estimated Budget
Attach File