StudioApp StoreDesign

App Store Screenshots in 10 Languages From One Base Design

Ridvay · November 16, 2026 · 7 min read

App Store Screenshots in 10 Languages From One Base Design

Three App Store screenshots. Ten languages. That's thirty images before you've added a second device size, and every one of them has to change the next time marketing rewrites a headline.

Most teams handle localized App Store screenshots the hard way: one design file per language, copied from the English one, edited by hand. It works exactly once. The day the brand colour changes, or a headline gets rewritten, someone opens ten files and makes the same edit ten times, and one of them always gets missed. Multiply by every device size and campaign, and you end up maintaining hundreds of near-identical templates.

There's a better setup: one base design, and every other language as a translation of it. You change the base. Every language catches up with one click. Here's the whole workflow on a real example, with real screenshots.

The example: a photo-sharing app in 10 languages

I built a screenshot set for Lumo, a made-up photo-sharing app in the familiar social-feed style (Lumo isn't a real app and isn't affiliated with any). Three portrait screenshots at 1290×2796, a size App Store Connect accepts for iPhone, each with a headline over a realistic phone:

  1. "Share the moments that matter": the home feed, with a stories row, a photo post, likes and a caption
  2. "See your friends' stories first": a full-screen story with a text sticker and a reply box
  3. "Find people who love what you love": the explore grid, search bar and a suggested account

The detail that makes the rest of this post work: the app UI inside the phone is built from real text layers, not a pasted screenshot. "Liked by tom_runs and 1,284 others", "Send message", "Search", "Follow": all text, so all of it gets translated along with the headline. A flat screenshot of your app can't be translated by anyone.

Then I added nine languages from the Languages row in Ridvay Studio: Spanish, German, French, Portuguese, Italian, Dutch, Japanese, Korean and Chinese. Each took about four seconds.

The first Lumo App Store screenshot in English, Spanish and Japanese: the same home feed on a realistic iPhone, with the headline, story names, likes line and caption translated

Look at the small things, because that's where localized screenshots usually go wrong. "Your story" became "Tu historia" and "あなたのストーリー". The likes line follows each language's own grammar and number format: "Le gusta a tom_runs y a 1.284 personas más", "tom_runs 他1,284人が「いいね!」しました". The usernames (lena.cooks, ana.travels) stay as written, because handles are never translated. In the story screenshot, even the "2h" timestamp became "2 Std." in German and "2時間前" in Japanese.

Where a translation ran longer than its box (the German explore headline became "Finde Leute, die deine Leidenschaft teilen"), Studio set that whole text box slightly smaller so it still fits on the same lines.

Change the base once, update every language

This is the part that makes the setup worth it. After making all ten languages, I changed only the English base:

Here's the first screenshot in all ten languages before the change:

The first screenshot in ten languages before the change: coral accent on a peach background

The moment the base changed, all nine translations were marked out of date: a dot on each language chip and an ↻ Update button. I pressed Update on each of the nine. Each one translated the new base again, with the new colours and the new headline, in about four seconds. All nine took 34 seconds.

The same screenshot in all ten languages after one edit to the English base: every language now blue with the new headline

Read the new headlines: "Comparte momentos con tu gente", "Teile deine Momente mit deinen Leuten", "Partagez vos moments avec vos proches", "大切な瞬間を、大切な人とシェアしよう". Nobody retyped them, and no colour was changed by hand in any language. Update rebuilds each language from the base as it is now.

The story and explore screenshots updated in the same pass:

The story screenshot in ten languages: the sticker, reply box and timestamp translated in each

The explore screenshot in ten languages: search bar, suggestions and Follow button translated in each

So instead of thirty files to keep in step, you have one design with nine translations hanging off it. Add a fourth screenshot to the base and every language gets it on its next Update. That's what "keep one base, keep adding translations" means in practice: you never maintain a translation's layout, you only maintain the base.

Building it in Ridvay Studio

Start with the base set. Type something like this into Studio:

Three App Store screenshots for a photo-sharing app called Lumo, 1290×2796, on a soft peach background: a bold two-line headline on each, and below it a realistic iPhone showing the app — a home feed with a stories row and a photo post, a full-screen story, and an explore photo grid. Build the app's buttons and labels as real text.

What comes back is an editable design with one page per screenshot. Before you translate:

  1. Make every word in the phone a text layer. Labels, buttons, captions, the likes line. If it's text, it translates; if it's part of a picture, it stays in English forever.
  2. Keep headlines short. Two lines of three or four words leave room for German and French, which usually run longer than English.
  3. Leave room in every text box. A box only as wide as the English word forces the translation smaller.

Then add the languages:

  1. At the bottom of the editor, right above the page chips, find the row called Languages.
  2. Click + Language and pick one. Each language is listed by its own name: Español, Deutsch, 日本語, 한국어, 中文.
  3. Studio translates every page and opens the copy, with its own chip and preview in the row. Repeat for each storefront.

Make an App Store screenshot set like this in Studio →

When you change the base later, open the design. Each language that's out of date shows a dot and ↻ Update. Update asks first, because it resets that language's layout to the base's. That's what you want here: the layout belongs to the base. Version history keeps the previous copy if you ever need it back.

Each language is its own design, so you download it on its own: open the Japanese copy, download the three PNGs, and upload them to the Japanese localization in App Store Connect.

The rules that keep 10 languages in sync

Edit only the base. If you fix a word in the Spanish copy by hand, the next Update replaces it. Put changes in the base, or redo the fix after each update.

Get each language read once. Machine translation does well with short app copy, but a native speaker catches what it can't: a word that's correct but isn't what your category calls it. Fix it, and if the cause is in the base, fix the base so the fix survives updates.

Keep handles, links and numbers in the base. Handles, links, email addresses and prices are never sent for translation. Numbers inside a sentence stay the same number, though a language may write it its own way (1,284 became 1.284 in German).

Don't put words inside images. Text baked into a photo or a pasted UI screenshot stays in English in every language.

For what makes a single screenshot convert in the first place (the first-screenshot hook, contrast, readable captions), read how to make App Store screenshots that get downloads. For the same workflow applied to social posts, see franchise social posts in every language. The step-by-step reference with screenshots of every control is in the help centre: Translate a design into another language.

One base, ten storefronts

The win isn't the first set of translations. It's the tenth headline change, when the whole set is current in under a minute instead of an afternoon of copy-paste across thirty files.

Build your base set once, add each language from the Languages row, and let every storefront follow it.

Start your App Store screenshots in Ridvay Studio →

Try Ridvay — the free AI design tool

Describe a poster, social post, flyer or slide and Ridvay generates a complete, editable design in seconds.

Open Ridvay Studio   ← All posts