Free App Store & Google Play screenshot downloader

Every App Store and Google Play listing is built from artwork the developer uploaded at a fixed, high resolution: screenshots at the native pixel size of the device they were captured on, an icon at 1024 × 1024, and on Play a 1024 × 500 feature graphic. None of that is what your browser loads. Both stores serve artwork through a resizing CDN, and a store page only ever requests a preview a few hundred pixels wide, because that is all it needs to draw a carousel.

That is why right-clicking a screenshot and choosing Save image gives you something blurry and unusable. The full-resolution original is sitting on the same CDN the whole time; the page simply never asks for it. This downloader asks for it.

What you get from a listing

Paste one link and the entire public creative set comes back, grouped by where it appears in the store:

• Screenshots, split by device. iPhone and iPad sets arrive separately, along with Apple TV, Watch and Vision sets on listings that carry them. On Play, phone, tablet and Chromebook sets come back separately when the developer uploaded dedicated ones.
• The app icon at 1024 × 1024, square and unmasked, without the rounded corners the stores apply on display.
• The feature graphic at 1024 × 500 on Google Play. This is the banner Play shows above the listing and in editorial placements; it has no App Store equivalent.

Nothing is re-encoded on the way through. The files are byte-for-byte what the store serves, with no watermark, no recompression and no resizing.

How to download App Store screenshots

Four steps, about fifteen seconds, no account:

1. Copy the listing link. Open the app on the App Store or Google Play and copy the URL from the address bar. A share link from the mobile app works too.
2. Paste it into the downloader. Drop the link into the box above and press Rip. The listing is read in a few seconds; nothing is downloaded to your machine yet.
3. Pick the assets you want. Screenshots are grouped by device: iPhone, iPad, and any Apple TV, Watch or Vision sets the listing carries. Select individual images or take a whole group.
4. Download at full resolution. Take a single image, or download the selection as a ZIP with every file named by device, dimensions and source id.

Any App Store URL works, the full canonical link, a share link from the iOS App Store app, or a bare id URL such as apps.apple.com/app/id447188370. If the link names a storefront, that is the storefront that gets read.

How to download Google Play screenshots

Identical flow, different plumbing underneath. Play builds its listing page from embedded JSON blobs rather than server-rendered markup, and its images live on play-lh.googleusercontent.com with a per-image id. Appending =s0 to one of those URLs asks the CDN for the untouched original, which is how full-resolution Play assets come back.

Play listings return two things the App Store has no equivalent for: the 512 × 512 icon and the 1024 × 500 feature graphic. If you are auditing your own listing, the feature graphic is the asset most often left stale, it is easy to forget it exists.

Why store pages don't show full resolution

Both stores use a templated image CDN. Apple's artwork URLs end in a size template that looks like this:

https://is1-ssl.mzstatic.com/image/thumb/…/source/{w}x{h}bb.{f}

The page fills in whatever size it needs for the layout, often 300 or 400 pixels wide, and the CDN renders that on the fly. The embedded page data, though, also carries each artwork's real width and height. Fill the template with those numbers instead and the CDN returns the original the developer uploaded. Google Play works the same way with a different syntax.

This matters for a practical reason: a screenshot scaled down to carousel size and back up again is worthless for judging typography, crop, or how a competitor handled a device-specific safe area. You need the original pixels.

What resolution you actually get

Whatever the developer uploaded. Store requirements change over time and listings often carry sets captured on older devices, so the exact numbers vary, but these are the common ones:

Screenshots come back in the orientation they were uploaded in. A landscape set from a game will stay landscape rather than being padded into a portrait frame.

Downloading a different country's storefront

A listing is not one page, it is one page per storefront, and the creative frequently differs between them. Localised screenshots, a different feature graphic for a regional campaign, sometimes an entirely different icon. If you compare your listing against a competitor's without matching storefronts, you may be comparing two unrelated sets of creative.

Point the downloader at the storefront you want by using that storefront's URL:

• App Store, the country is the two-letter code in the path: apps.apple.com/de/app/… for Germany, apps.apple.com/jp/app/… for Japan. A link with no country is served from the US storefront.
• Google Play, the country is the gl query parameter: &gl=de. Without it, Play decides from where the request appears to come, which is not something you want to leave to chance.

Custom Product Pages and Custom Store Listings

Both stores let developers run alternate versions of a listing for ad campaigns: Apple calls them Custom Product Pages, identified by a ppid parameter, and Google calls them Custom Store Listings, identified by a listing parameter. These carry different screenshots from the default page and are usually the sharpest signal you can get about what a competitor is testing, because they are built to convert traffic from a specific campaign.

Paste a campaign URL and you get that variant's creative rather than the default listing's. It is worth collecting both and putting them side by side.

How the files are named

Downloads arrive named for what they are, so a folder of them stays legible weeks later rather than becoming twenty files called image.png:

iphone-01_1290x2796_a3f9c2e1.png
iphone-02_1290x2796_b7d14e08.png
ipad-01_2048x2732_c9012fab.png
icon-01_1024x1024_d4e8b331.png

Device group, position within that group, the actual pixel dimensions, and a short id taken from the source URL. Taking a whole selection gives you a ZIP with that structure intact.

What you can and can't do with these assets

Reading a public store page is no different from visiting it in a browser, and pulling a competitor's creative for research, benchmarking or an internal teardown is ordinary competitive analysis. Agencies and ASO teams do it constantly, and it is the entire basis of a creative audit.

What you download stays the copyright of whoever published it. So:

• Reasonable: competitive research, creative audits, internal benchmark decks, spec-checking your own listing, archiving your own assets when the source files have gone missing.
• Not reasonable: republishing another company's creative, using it in your own store listing or advertising, passing it off as your own work, or redistributing it as a stock asset.

Downloading your own listing's assets is a legitimate recovery route when the originals are lost, a designer left, an agency contract ended, or the working files went with an old laptop. The store has been holding a full-resolution copy the entire time.

What this tool won't do

Being clear about the edges, so you do not waste time:

• Video previews are not included. App previews and Play promo videos are delivered as streaming manifests rather than single files, and are not part of what comes back.
• It reads public listings only. Unreleased apps, TestFlight builds and anything behind a store login are not visible to it.
• It is a snapshot, not a history. You get the creative that is live right now. Knowing what a listing looked like last month, and what changed since, is what the tracking side of AppSnapify exists for.

What people use it for

Competitive and category research

Pull the top ten apps in a category, put their first three screenshots side by side, and the shared conventions become obvious quickly, which message leads, whether device frames are used, how much copy sits on the first slide. That is the fastest read available on what a category has converged on.

Auditing your own listing

What is actually live is often not what you think shipped. Pulling your own assets at full resolution surfaces the stale iPad set nobody updated, the feature graphic still advertising last year's promotion, or a screenshot uploaded at the wrong size and quietly upscaled by the store.

Recovering lost source assets

When the original files are gone, the store copy is the best remaining version, the full-resolution image the developer uploaded, not a compressed re-share.

Tracking creative changes over time

Downloading is a point-in-time answer. If the question is what changed, and when, that needs something re-checking the listing on a schedule and comparing each snapshot against the last.

Frequently asked questions

Is the App Store screenshot downloader free?

Yes, and there is no account. Paste a link, take the assets, close the tab. The paid product is the monitoring side, which re-checks listings on a schedule and alerts you when a competitor's creative changes.

What resolution do the screenshots come out at?

The original resolution the developer uploaded, typically 1290x2796 or 1242x2688 for recent iPhone sets and 2048x2732 for iPad. Both stores serve artwork through a resizing CDN and a browser only ever loads a small preview, so saving from the page gives you a downscaled copy. This tool reads each image's real dimensions from the page data and requests exactly those, which returns the untouched original.

Can I download the app icon on its own?

Yes. The icon is pulled separately from the screenshot sets and comes back at 1024x1024, which is the size Apple and Google require developers to supply. It arrives square and unmasked, without the rounded corners the stores apply when displaying it.

Does it work with Google Play as well as the App Store?

Both. Play listings also return the 512x512 icon and the 1024x500 feature graphic, which have no App Store equivalent. Phone, tablet and Chromebook screenshot sets come back separately when a developer has uploaded them.

Are the images watermarked or compressed?

No. The files are byte-for-byte what the store serves, straight from the same CDN your browser would use. Nothing is re-encoded, resized or stamped on the way through.

Do you store the listings I paste in?

No. The free downloader parses on request and streams the result back to you. Listings are only kept when you deliberately add one to a tracking account, which is what builds the change history.

Can I download screenshots from a different country's store?

Yes, and you often should. Listings are localised per storefront and the creative frequently differs. Use the URL for the storefront you want: the country sits in the path on the App Store (apps.apple.com/de/app/...) and in the gl parameter on Google Play (&gl=de).

Is it legal to download a competitor's screenshots?

Reading a public store page is no different from visiting it in a browser, and downloading assets for research, benchmarking or internal reference is ordinary competitive analysis. The artwork stays the copyright of whoever published it, so do not republish it, pass it off as your own, or use it in your own store listing or advertising.