Translating
End-to-end guides for producing translations and moving them in and out of a Messagevisor project. Each guide stitches together the CLI, the export and import round trip, and an external tool to get the job done.
Available guides#
Translating with a tool or service:
- Google Sheets: export a CSV, translate cells with
GOOGLETRANSLATE, import the result back through the CLI. - DeepL: translate a CSV through the DeepL API, with ICU placeholder preservation and glossary support.
- AI translations: use an AI coding agent like Claude Code to drive the export, translate the CSV, and run the import for you.
Working with humans:
- Translator handoff: send a CSV to a freelance or agency translator and bring their work back, without a hosted translation platform.
Getting copy into the project:
- Figma: extract UI copy from a Figma design into a Messagevisor CSV before translating it.
- Framer: extract canvas text or CMS entries from a Framer project into a Messagevisor CSV before translating it.
Automating the loop:
- Auto-translating new keys in CI: run machine translation in GitHub Actions and open a follow-up pull request for review.
When you might want a different doc#
- For the CLI flag reference behind these guides, see Export and import.
- For the conceptual framing, see Translations as code and Localization (l10n).
- For the broader deployment story, see Deployment and Cloud Native.

