Now · pairs to your phone over WebRTC Issue 04 · 2026 Free to design · from €9.99 one-time to ship
Screenshotify
Help · Translation

Translating screenshots.

TL;DR. Enable your target locales in the language switcher. Write captions in your source language. Click "Translate all" — every text layer fills its content[locale] map for every enabled locale. Switch the active language in the header to review per locale; edits per-locale stick.

The 39-locale list

Screenshotify supports every locale Apple's App Store Connect accepts: Arabic, Catalan, both Chinese variants, Croatian, Czech, Danish, Dutch, 4 English regions, Finnish, 2 French, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Norwegian, Polish, 2 Portuguese, Romanian, Russian, Slovak, 2 Spanish, Swedish, Thai, Turkish, Ukrainian, Vietnamese. See the feature page for the full list.

The flow

  1. Open the language picker in the header (flag icon dropdown). Check the locales you want shipped.
  2. Set source language if it isn't English. Defaults to en-US. The source-language captions are what the AI translates from.
  3. Write captions in the source language. Each text layer accepts multiline; the source content is stored as plain text.
  4. Click "Translate all" in the header. Every text layer's content map fills with translated strings for each enabled locale.
  5. Switch active language via the header dropdown. The whole canvas swaps to that locale's text. Edit anything that needs a human fix — your edits write to content[locale] only, leaving other locales untouched.
  6. Export — the ZIP organizes by locale, each folder named with the canonical App Store code (en-US/, pt-BR/, zh-Hans/).

Where auto-translate falls short

Auto-translate uses Anthropic’s Claude. It's competent for short marketing copy but not perfect. Things to always review by hand:

  • Brand names and product nouns — auto-translate sometimes localizes "Inbox Zero" into the locale's word for "inbox" + "zero". Lock these in source.
  • App store CTAs like "Tap to start" — locale-specific imperative forms vary; review Japanese, Korean, Russian, Polish carefully.
  • Plurals — "3 tasks" in Polish, Russian, Arabic depends on the count. Generic translation often picks the wrong plural form.
  • Gendered language — German, French, Spanish, Italian guess gender. "Welcome, user" can land as masculine when your audience is mostly female.

Translation is free

AI translation is free — "Translate all" works for everyone, no purchase needed. You only pay once when you export the finished design watermark-free (Single €9.99 or Pro €29.99); a watermarked preview is free too. See pricing.

Common questions

Can I use my own translation API?

Not yet — the editor wires directly to Anthropic Claude. We're considering DeepL and OpenAI as alternatives for users with higher quality requirements.

What happens to translations when I edit the source?

The source-locale string updates immediately; other locales keep their existing translated text. Click "Translate all" again to overwrite the now-stale translations.

Can I leave some locales blank?

Yes — only enabled locales get translated. App Store Connect lets you submit screenshots in a subset of locales and falls back to your default for the rest. Honest tier: hand-review the top 5 markets, skip locales you can't review at all.

Open the editor → Localization guide