Internationalization plugins for Payload CMS 29

Translate localized fields in Payload CMS with OpenAI, DeepL or Google. Sync content with Crowdin and keep slugs and interface strings per locale.

Translates default-locale content into secondary locales with OpenAI or a custom provider

Translates localized content fields with an AI provider from the admin panel

Sends localized Payload fields to Crowdin and writes translations back

Generates and stores URL slugs per locale for localized Payload collections

Transcribes audio uploads, then translates and reads transcripts aloud

Restyles the Payload admin panel from one accent color, with a dashboard and command palette

Keeps Payload content translated into every configured locale, as it changes

Translates localized Payload fields into each locale with General Translation

Translates Payload collections and globals with DeepL, Google, OpenAI or copy resolvers

Localized SEO group field with meta tags, Open Graph fields and length checks

Translates Payload documents into other locales with LibreTranslate in the background

Walks Payload field schemas to pick localized fields and rebuild document updates

Moves frontend translation keys into the Payload database for editors to manage

Translates localized fields in Payload with AI, leaving hand-edited text alone

Stops localized blocks and arrays from being wiped when saving another locale

Translates Payload content between locales in the admin panel using AI or custom resolvers

On-page SEO scoring in the editor, site audit dashboard, sitemaps and JSON-LD

Sends localized Payload content to Reversia for translation and writes results back

Locale-aware SEO fields, metadata resolution, robots, redirects and sitemaps

Localized UI strings global with per-scope admin tabs and fallback translations

About these packages

Payload localizes content on its own. You list the locales in the localization config and mark fields as localized. These plugins build on that setup. Some fill other locales by machine translation, and others sync content with a service such as Crowdin.

What these plugins cover

  • Translator plugins that fill localized fields with OpenAI, DeepL or Google
  • Background and on-publish translation with Auto Translate and Polyglot
  • Crowdin Sync, General Translation and Reversia for translation services
  • Localized Slugs for a separate slug and path per locale
  • Per-locale field tabs and protection for other locales' blocks on save
  • Frontend UI strings managed in Payload with Dictionary and Intl

Choosing an i18n plugin

Turn on localization in payload.config first, because translator plugins only fill localized fields. Then choose by workflow. Translator and Content Translator suit editors who translate from the admin. Auto Translate and Polyglot translate when a document is saved or published. If your translators already work in Crowdin, use Crowdin Sync. Machine translation calls a paid API such as DeepL, so review the output before you publish. For button labels and other frontend strings, Dictionary and Intl keep the copy in Payload.

Frequently asked questions

How do I translate content automatically in Payload CMS?

Enable localization, mark the fields as localized and add a translator plugin. Translator fills other locales with Google, OpenAI or a plain copy, and a fork of it adds DeepL. Auto Translate and Polyglot translate in the background.

What is the difference between localization and i18n in Payload?

The localization option in payload.config stores field values per locale. The i18n option translates the admin panel interface. Neither translates your content, which is what the plugins in this category add.

Can I have different slugs per language in Payload?

Yes. Make the slug field localized. Localized Slugs goes further and keeps a separate slug and full path for each locale.