Does Easy App Screens cover every App Store and Google Play screenshot size and language?

Updated

Yes, based on the site's own claims. Easy App Screens says it renders one screenshot design across 15 screenshot sizes covering both the App Store and Google Play, in every language you ship, and checks each exported file against the sizes, formats and limits Apple and Google publish. The site states those checks were verified on 2026-09-12. The exact size list is not reproduced on the page — it points to a separate sizes page.

What "cover both stores" means here

The core promise is one design set that fans out to every size each store requires, rather than you rebuilding artboards per store.

Claim Detail given
Stores covered App Store + Google Play
Screenshot sizes 15
Verification date 2026-09-12
Languages Every language you ship
Compliance check Each file checked against sizes, formats and limits Apple and Google publish
Output A ZIP already foldered for upload

Two things are worth separating:

  • Size coverage is a fixed, countable claim (15 sizes). You can confirm it against the sizes page before committing.
  • Language coverage is not a fixed list — it follows whatever languages your listing ships in. The page's example scenario is five languages, but that is an illustration of workload, not a cap.

The multi-language part is the real differentiator

The page makes a specific point about localisation: Apple asks you to localise the screenshots, not just the words. That is the requirement most manual workflows quietly skip, because translating and re-laying-out five screens across five languages is where the four-to-six-hour estimate comes from.

The stated behaviour is that copy stays where you wrote it, in the language you wrote it in. So the design (device position, type, background) propagates across the whole set, while text does not get propagated across languages — you supply each language's copy once.

What the workflow actually involves

The page describes three steps, with only the middle one being yours:

  1. Drop in your captures.
  2. Pick a preset and write the copy once (this is the step you do).
  3. The tool renders every size and language, checks each file, and hands you a foldered ZIP.

The practical consequence: the next release is a capture swap rather than a re-layout, since the design and copy persist.

Before you rely on it

  • Check the sizes page yourself. The 15-size claim and the 2026-09-12 verification date are the site's own; store requirements change, so confirm the current list matches what App Store Connect and Google Play Console are asking for at your submission time.
  • Confirm your language set is supported. The page frames language coverage as "every language you ship," which is a broad claim rather than an enumerated list.
  • Pricing and access: the page states it is free to start with no card and no trial clock — you can build the whole set and export one real file at full resolution without a watermark before deciding. It then states a one-time $149, not a subscription. Treat these as the site's stated terms at the time of writing.

If your listing is a single language and a single device class, the multi-size, multi-language machinery is doing less for you. The value concentrates in listings that ship several languages or both stores, where the per-release layout cost is the thing being removed.