Veronica Prilutskaya

The new Lingo.dev is here, and it is live for every organization.

Lingo.dev is completely redesigned around the way you work, so everything now has a clear place, across five areas:

• Home  your starting point: a quick read on recent activity.

• Infrastructure  where you build your localization engines: the models, glossaries, rulesets, and brand voices you configure once and reuse everywhere.

• Studio  where localization connects to the tools you already use: the GitHub App, a Zendesk Help Center, a Payload CMS, plus the CLI and the API.

• Queue  one inbox for everything that needs a person: human review, localization engine suggestions, and triage, in a single list you filter and save as views.

• Observability  where you see whether the output is good, even in languages you cannot read: reports, AI reviewers, and a log of every review beside the translation it scored.

This is the foundation for everything we build next, and the new home for your localization work.

You can now retranslate specific pieces of your content, down to a single key.

The Lingo.dev CLI command lingo push retranslates only the source text you edited. But some changes happen in your localization engine, not your files: you switch the model, add glossary terms, or edit your rules. Your source stays identical, so lingo push finds nothing to redo. Now you can retranslate the exact pieces you want, from a single key to a whole language.

Run lingo push messages/en.json --key auth.login and Lingo.dev retranslates only the keys you list. A key is its path in the file, so you can pick one value, a whole subtree, or several keys at once. Everything else stays the same. If you are not sure which keys to list, your AI coding assistant can read the file and write the command for you.

If a change affects more than a few strings, retranslate whole files. Run lingo push src/en/**/*.json --force and Lingo.dev retranslates every string in the files you list. And if one language needs redoing, run lingo purge --locale fr to delete the French files, then lingo push --backfill-missing to translate them again. Your other languages stay the same.

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.