W35 Product Update: Translate your Payload CMS content

You can now translate your Payload CMS content from Lingo.dev.

The Payload CMS integration connects your Payload instance to a localization engine you host on Lingo.dev. Choose the collections and globals to cover, and Lingo.dev translates their localized fields into your target languages, then writes each translation back to Payload under that locale. Rich text translates as a Lexical tree, so formatting, links, uploads, and block structure survive the round trip and only the text inside is replaced.

Setup is one plugin. Install lingo.dev/payloadcms, add it to your Payload config, and redeploy. Scope, locales, and engine live in the dashboard, so you can change them without touching your config again.

You choose how translation runs. Add the webhook URL from the dashboard to the plugin and it runs automatically: every change you publish in your source locale is sent to Lingo.dev on its own, and only what changed is translated. Leave the webhook URL out and it runs manually: nothing translates until you start it from the dashboard. Automatic runs cover what you publish after connecting, so the dashboard has two buttons for the rest: Sync catches up on the content that was already in Payload, a locale you add later, or a failed run, and Retranslate rebuilds everything in scope from scratch after an engine change.

Every run goes through the full localization pipeline configured on your localization engine, the same stages that run when you localize from code or CI. Whatever you have enabled applies to your Payload content: pre-edit, your glossary, brand voice, and rules, AI review, rephrase, back-translation, and human review by your own team in the dashboard or an external professional translator.

Check out the guide to set it up.

Full changelog: lingo.dev/changelog