Shipshot guide
How to localize an app screenshot story without losing the message
Translating a screenshot set word by word usually produces captions that are correct and unpersuasive. What has to survive the crossing is the argument — the claim, the emphasis, and the reason it matters to that reader. That sometimes requires different words than a literal rendering would give you.
Translate the claim, not the sentence
Caption copy is compressed marketing language, and compression is where literal translation breaks. A phrase that lands in English may be a meaningless idiom elsewhere, or may make a promise the market reads as exaggerated. Give the translator the claim behind the sentence and the frame it sits on, and let them reach it in their own language.
- Write the underlying claim of each caption in plain language for the translator.
- Say which word carries the emphasis and why.
- Accept a caption that differs in wording if it delivers the same claim better.
Check the claim is still true in that market
This is the accuracy problem that literal translation hides. A feature may be unavailable in a region, a payment method may not exist there, a comparison may reference a competitor nobody has heard of, and a legal or regulatory phrase may carry a specific meaning. A perfectly translated caption can still be wrong.
- List claims that depend on availability, pricing, or a named third party.
- Confirm each one holds in the market before translating it.
- Replace market-specific comparisons with something locally meaningful.
Do not let the interface contradict the caption
If the caption is in Japanese and the product screen behind it is in English, the frame quietly tells the visitor the app is not localized. Sometimes that is the honest position, and the caption should not imply otherwise. Where the app itself is localized, capture the interface in that language so the frame is internally consistent.
- Capture product screens in the interface language wherever the app supports it.
- Where the app is not localized, avoid captions implying it is.
- Keep product names, marks, and identifiers consistent across every language.
Give length room before it becomes a design emergency
Some languages need considerably more room than English for the same idea, and others need much less. Design the caption area with slack from the start rather than discovering at review that German needs a third line and Japanese leaves an awkward gap. Shrinking type until the longest translation fits is how a localized set becomes unreadable.
- Design the caption area to hold more text than the English version needs.
- Review the longest translation in place before approving the layout.
- Adjust line breaks and spacing per language rather than reducing the type size.
Review checklist
Questions to ask before handoff
Should a localized caption match the English wording closely?
It should match the claim. Wording that differs but lands the same point is usually better than a literal rendering of a compressed English phrase.
What if the app interface is only in English?
Keep the frame honest. Localizing the surrounding caption can still help, but nothing in the set should imply the interface is translated when it is not.
How much extra room should the caption area have?
Enough for your longest expected translation on its own terms. Design for that from the start rather than compressing type at review time.
