Use Cases
Translate App Store screenshots into 80+ languages in one workflow. One master design, every locale, every required Apple App Store and Google Play size per market — without duplicating Figma files for each language.
%2FOlivia%20Rhye.webp&w=64&q=75){kind=small}
%2FPhoenix%20Baker.webp&w=64&q=75){kind=small}
%2FLana%20Steiner.webp&w=64&q=75){kind=small}
%2FDemi%20Wilkinson.webp&w=64&q=75){kind=small}
%2FDrew%20Cano.webp&w=64&q=75){kind=small}
Loved by 2,000+ creators
Apple has publicly reported that localized App Store listings can drive a 2-3x install lift in non-English markets. The same pattern holds on Google Play. Yet most indie and small-team apps ship one set of English screenshots and leave the lift on the table.
The reason is tooling, not translation cost. Translating 5-8 captions per language costs $20-50 with a freelance translator. Rebuilding the screenshot set per locale in Figma — duplicating frames, replacing text across dozens of artboards, exporting at every required Apple and Google size for each language — costs hours and often gets skipped under deadline pressure. Screenhance is the workflow tool that closes that gap: one master, swap captions, export every size per locale.
Read the full strategy guide: App Store Screenshot Localization →
Pick a template, upload your screenshots, and export every size Apple and Google require. Each template has multiple slides ready to customize.
No credit card required
Not every locale earns the effort. Start with these eight before expanding. Each has either market size, willingness to pay, or both.
Japanese (ja)
Second-largest app market globally. Highest single-locale ROI in most categories.
German (de)
Largest European market. Captions can run 30-40% longer than English — design for overflow.
French (fr)
Covers France, Belgium, Switzerland, and parts of Canada. Similar overflow profile to German.
Simplified Chinese (zh-Hans)
App Store only — Google Play not available in mainland China. CJK glyph density needs slightly different sizing.
Korean (ko)
High-engagement mobile audience. Pairs well with Japanese in single localization passes.
Spanish (es)
One translation covers Spain plus most of Latin America. Mexico-specific Spanish converts marginally better in MX.
Portuguese (pt-BR)
Largest Latin American market. Translate from English source rather than European Portuguese.
Arabic (ar)
RTL — capture in-app screenshots from your app's RTL mode rather than mirroring the LTR set.
Create professional mockups in three simple steps. No design skills required.
Drag and drop or select any screenshot, design, or image from your device.
Pick from iPhone, iPad, MacBook, browser frames and beautiful gradient backgrounds.
Download as PNG, WebP, JPEG, GIF, or video. Ready for marketing in seconds.
Two capabilities that separate Screenhance from every other mockup tool in 2026: animated exports and App Store screenshot localization.
Template-driven motion — float, reveal, parallax. Export animated mockups at Product Hunt, landing-page, and Twitter/X dimensions. Most mockup tools are static-only.
One master design, per-locale captions, every required Apple and Google Play size per language. RTL and CJK support. Apple reports localized listings drive 2-3x install lifts.
iPhone 17 Pro Max (1320×2868), iPhone Air (1260×2736), iPad Pro M4 (2064×2752), and the full Google Play set — exported from one design in a single pass.
Pick a template, drop in your screenshot, export. No Figma, no Photoshop, no learning curve. Free tier covers 3 exports a month; $6 Week Pass unlocks unlimited for a launch.
Build one master, not five. The mistake that kills localization projects is duplicating the design intent five times — once per language — and trying to keep all five in sync as the brand evolves. The correct pattern is one master per surface (App Store iPhone set, App Store iPad set, Google Play phone set), with locales as variants that swap only the text layers. When the brand updates, you edit one master and re-export every locale.
Plan for text expansion. German runs 30-40% longer than English. French and Russian similarly. Hindi and Thai vary widely. Design caption text areas with extra breathing room from day one — assume the longest target locale will set the layout constraint, not the source English.
Capture in-app screenshots in each locale. If your app is localized, switch the simulator or device to each target locale and capture fresh screenshots so dates, currency, and any in-app text match. If the app is not yet localized, use English screenshots and localize only the marketing overlays — but flag that as technical debt.
Translate as a batch, not as a stream. Send all captions for all locales in one translator brief. Per-language streaming costs 2-3x more and forces context-switching that hurts quality. Most freelance translators turn around 5-8 captions per locale in 24-48 hours.
Export once per locale, all sizes at once. For each locale variant, Screenhance exports every required Apple and Google Play dimension in one pass. Eight locales × five required sizes = 40 deliverables, produced in minutes instead of hours.
Track conversion by locale. App Store Connect and Google Play Console both report install conversion per locale. The locales where localized screenshots lift conversion 20%+ over English are the ones to invest in deeper (richer overlays, locale-specific imagery). The locales where lift is marginal can stay on the lighter pass.
Most mockup and screenshot tools have no per-locale workflow at all. The closest alternatives require manual duplication per language.
| Feature | Screenhance | Figma + plugin | Smartmockups |
|---|---|---|---|
| One master, swap captions per locale | Yes | Manual duplicate per locale | No localization workflow |
| Apple + Google Play sizes per language | One-pass export | Manual artboard setup per size per locale | No App Store sets |
| Right-to-left language support | Yes (Unicode + RTL typography) | Yes (manual) | Limited |
| CJK glyph sizing per locale | Per-locale font size | Per-locale manual adjustment | Limited |
| Animated exports (per-locale GIF/WebM) | Yes | No | No |
| Free tier | 3 exports/month | Free tier | Watermarked |
| Paid pricing | $6 Week Pass or $8/month | $15/month per editor | $19/month |
Design one master screenshot set, then duplicate it per locale, swap the captions, and export. The device frame, background, layout, and screenshot composition stay identical across languages — only the text overlays change. Each locale gets exported at every required Apple and Google Play dimension in one pass.
No, and we recommend against it. Machine-translated App Store captions consistently underperform human-reviewed translations in real conversion tests. Screenhance gives you fast per-locale caption editing and batch export so a human translator's output is one paste-and-export away from a complete localized screenshot set.
80+ languages are supported, covering every locale App Store Connect and Google Play accept for store listing uploads — including English, Spanish, Portuguese (Brazil and Portugal), French, German, Italian, Dutch, Japanese, Simplified and Traditional Chinese, Korean, Russian, Arabic, Hebrew, Turkish, Hindi, Thai, Vietnamese, Indonesian, Polish, and Nordic languages. Captions accept Unicode for any script, with proper typography for CJK, Arabic, Hebrew, Cyrillic, and Devanagari.
Yes. Text overlays accept RTL Unicode strings and render with correct typography. The standard practice is to also capture in-app screenshots from your app's RTL mode rather than mirror LTR screenshots, which keeps the UI itself authentically RTL.
Yes. The master template defines text areas with overflow-safe sizing, so longer translations stay within the layout. You can also adjust font size per locale without rebuilding the composition — useful for Japanese and Korean where the optical density of CJK glyphs needs slightly different scaling.
Free plan: 3 exports/month — enough to validate the workflow for one or two locales. Week Pass: $6 one-time for unlimited exports over 7 days — built for the week you ship 5+ localized sets. Pro: $8/month for ongoing unlimited exports. Templates, device frames, and the localization workflow are unlocked on every tier.
Explore more ways to create stunning visuals with Screenhance.
Samsung Galaxy and Pixel device mockups
Try it freeAdd Chrome, Safari, and Firefox frames
Try it freeCreate iOS and Android store visuals
Try it freeGenerate compliant App Store screenshots
Try it freePolish app screenshots for any store
Try it freeAndroid-ready Google Play visuals
Try it freeOne master design, every locale. Build the workflow once and re-export every market when the brand updates.
