Translate App Store Screenshots to Spanish

Neither console offers a bare "es" listing. Apple treats Spanish (Mexico) and Spanish (Spain) as separate localizations (opens in a new tab), while Google Play splits the language into Spain, Latin America and United States variants (opens in a new tab).

The audience is large enough to justify the extra step. The Instituto Cervantes 2025 yearbook (opens in a new tab) counts 520 million people with native command of Spanish and more than 630 million potential speakers worldwide.

If you fill only es-ES, shoppers in Mexico, Colombia or Argentina may land on whichever fallback the store chooses. Filling es-MX on iOS and es-419 on Android puts Spanish screenshots in front of Latin American shoppers directly.

StoreLocale has a single Spanish target with the code es. It detects the English text in each screenshot, translates it, and repaints the localized image. The export ZIP puts those PNGs in folders such as App Store (iOS)/es/ followed by a size folder.

The output is one generic Spanish set with no regional steering, so you decide where it goes. Review it for your main market first, usually es-MX and es-419 for Latin America, and fix any Spain-only words. If Spain matters, keep that first ZIP, then edit the Spanish text for Spain and export again for es-ES; only slides whose text changed are repainted and charged again.

Short strings expand the most. W3C quotes IBM guidance that English text up to 10 characters can grow by 200–300% (opens in a new tab) in European languages, while strings over 70 characters grow by about 130%. W3C gives no ratio specific to Spanish, so treat these as planning ranges.

A two-word label is where this bites. W3C notes that the three-letter "FAQ" becomes a two-word, 20-character phrase in Spanish. By the same logic, a punchy 17-character headline like "Track every habit" can become a Spanish sentence of more than 35 characters.

• Leave spare width in caption boxes rather than setting type edge to edge.
• Prefer a shorter rewrite to a smaller font size; small type is hard to read in store thumbnails.
• On Google Play, keep marketing taglines under 20% of the image area (opens in a new tab), which gets harder as Spanish text grows.

• Opening marks ¿ and ¡. Questions and exclamations need an opening mark as well as a closing one. Check that the font has both and that a translation did not drop them.
• Accented capitals. Á, É, Í, Ó, Ú and Ñ reach above the cap height. Tight line height in all-caps headlines can clip the accent or collide with the line above.
• The letter ñ. It changes meaning, so a font that silently substitutes n is a real bug, not a cosmetic one.
• Number and price formats. Spain writes 12.999,99 € while Mexico writes $12,999.99, so a price baked into a screenshot rarely suits both markets.

AI repaint is generative, so every slide needs a human pass before upload. Use the side-by-side compare view to check each localized slide against its English original.

1. Pick one form of address (informal or formal) and use it on every slide.
2. Flag Spain-only vocabulary, such as the words Spain uses for "computer" and "mobile phone", when the set targets Latin America, and the reverse for es-ES.
3. Confirm that every question and exclamation opens with ¿ or ¡.
4. Read the in-app UI text in the repainted image, not only the caption; look for duplicated or truncated words.
5. Check that brand names, feature names and acronyms were left untranslated where intended.
6. Look at the accents on capital letters at the smallest export size.
7. Verify prices, dates and decimal separators against the target market.