Brand voice survives translation only when each market gets its own short voice guide, written or reviewed by a native speaker. Translating your English guide word for word keeps the words and loses the voice. Humor, formality and even punctuation carry different weight in each language, so the fix is a one-page guide per market, plus a review step before anything publishes.
TLDR: Keep one core brand idea, then write a one-page voice guide for each language: formality, humor, emoji, terms never translated and three example posts. Use AI to draft in each language, and have a native reviewer approve before publishing.
Split the voice into what travels and what does not
Start by sorting your English guidelines into two lists.
| Travels across languages | Must be rewritten per market |
|---|---|
| Brand values and the core promise | Formality level and forms of address |
| What you never say or claim | Humor, idioms and cultural references |
| Visual identity | Emoji and punctuation habits |
| Product names and key terms | Sentence length and rhythm |
Your core promise should read the same everywhere. The way you say it should not.
The one-page guide for each market
For every language, write these seven lines:
- Formality: for example, formal "you" or informal. Languages like German, French, Japanese and Korean force the choice.
- Humor: allowed, light or avoid.
- Emoji and punctuation: how many, which ones.
- Never translate: product names, slogans, hashtags.
- Always translate: the call to action.
- Banned words: terms that sound wrong or carry other meanings locally.
- Three example posts: real posts from that market that sound right.
The examples matter most. They show your AI tool and your reviewer what "right" sounds like.
Draft with AI, but in the local language
An AI tool that translates your English caption gives you an English post in another language. A better method is to give it the local guide plus the local brief and ask it to write in that language directly. Then compare the two versions: if the translated one sounds stiff next to the direct one, use the direct one.
Our guide to repurposing content across brands and regions covers the workflow, and localizing captions shows which parts are worth testing.
Put a native reviewer in the approval flow
Nobody on an English-speaking team can judge a Vietnamese or Portuguese caption. Name one native reviewer per language and send every post to them before publishing.
In Mydrop, you can give each market its own space with workspaces and brands, invite the local reviewer with a limited role, and route posts through approvals so nothing goes live unreviewed. The calendar shows all markets in one view.
Settle terminology once
Terms cause more embarrassment than grammar. Keep one shared glossary per language with your product names, feature names and any phrase the market uses differently from the dictionary. When the AI tool or a freelancer picks a different word for the same feature, the glossary settles it without a debate, and the reviewer has something concrete to check against.
Check for drift every month
Once a month, pick five posts per language and ask the reviewer one question: does this still sound like us, and like a local? Update the guide with whatever they flag. Voice drift in a second language is slower to notice, so a regular check matters more than a perfect first guide.
One caution on length rules. Mydrop's data shows very short captions underperforming, but we have not split that result by language, and 80 characters means different things in Chinese and in German. Test caption length per market instead of copying a number.
Write your first market guide today
Pick your largest non-English market and fill in the seven lines with a native speaker in about 30 minutes. Publish three posts from it and compare them to your median. If you run several brands or markets, start free with Mydrop to keep each market's voice, people and approvals separate. For voice prompts, see the reusable brand voice prompt template.
Google review
Trustpilot review
Product Hunt comment
