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
| Platform | How translation works | Translation integrations found | Hosting | Free tier | Best for |
|---|---|---|---|---|---|
| Storyblok | Field-level, folder-level or space-level | Lokalise, Smartling, Phrase, Crowdin | SaaS | Yes, 2 locales | Marketing teams with several markets |
| Contentful | Locales per space with field-level values | Lokalise, Crowdin, Smartling, Transifex, Phrase | SaaS | Yes | Enterprise multi-site setups |
| Strapi | Locales per content type or field | Built-in AI translation (Growth); Crowdin and DeepL via community | Self-host or cloud | Open source | Node.js teams |
| Payload | Per-field with fallback | Community plugins only, Crowdin among them | Self-host | Open source | Next.js teams |
| Directus | Translations junction collection | DeepL and Crowdin (beta) via extensions | Self-host or cloud | Open source | Relational data with translations |
| Sanity | Field-level arrays or document-level | Transifex, Smartling, Phrase, Crowdin | SaaS | Yes, unlimited locales | Flexible modelling |
| Hygraph | Field-level locales | Lokalise, Crowdin, Smartling, DeepL | SaaS | Yes, 2 locales | Localised GraphQL queries |
| DatoCMS | Localised fields | Crowdin, AI Translations plugin with DeepL | SaaS | Yes, 5 locales | Multi-market sites on a budget |
| Prismic | One document per locale | Crowdin | SaaS | Yes, 2 locales | Marketing sites |
| Drupal | Built-in multilingual modules | TMGMT providers: DeepL, Lokalise, Smartling, Phrase | Self-host | Open source | Large, 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.