Blurry app store screenshots: why they happen and the fix

Why do exported app store screenshots look blurry and how do I keep @2x and @3x crisp?

The blur almost never comes from the store. It comes from the moment you exported. A screenshot that looks crisp on your design canvas can lose half its pixels by the time it lands on the storefront if any of three things go wrong: the source capture was too small, the export multiplier did not match the device class, or a lossy format softened the UI text on its way out. Fix the export and the store listing follows.

The rest of this guide walks through each of those four root causes in order, explains the pixel math behind @1x, @2x, and @3x so you can pick the right one for every device class, and ends with format and color-profile rules so the file survives the upload pipeline intact.

The resolution math behind app store screenshots

@2x vs @3x app store screenshots. Apple's design tooling thinks in points. A 430 by 932 point iPhone canvas at @3x renders to 1290 by 2796 pixels — the exact 6.9-inch store size. At @2x it renders to 860 by 1864, which is too small for the 6.9-inch shelf and gets upscaled on the listing. At @1x it renders to 430 by 932, which Apple rejects. The multiplier is not a quality knob; it is the pixel-density rule the store enforces.

Native pixel counts for every accepted device. iPhone 6.9-inch is 1290 by 2796. iPhone 6.5-inch is either 1242 by 2688 or 1284 by 2778 depending on the device class submitted. iPad 13-inch is 2064 by 2752. iPad 12.9-inch is 2048 by 2732. Google Play phone screenshots accept any pixel size between 320 and 3840 per side with a max 2 to 1 aspect ratio. Microsoft Store accepts 1366 by 768, 1920 by 1080, 2160 by 2160, or 3840 by 2160. Hit one of these grids at capture time and you are done.

How upscaling and resampling algorithms destroy sharpness

Bilinear, bicubic, and Lanczos compared. Nearest-neighbour copies the closest pixel and produces visibly jagged blocks at any scale above 1.5x. Bilinear averages four neighbours and softens edges to hide the guess. Bicubic samples 16 neighbours and looks smoother but still adds a faint blur. Lanczos uses a windowed sinc filter that preserves edge contrast better, with the tradeoff of mild ringing near very high contrast transitions. For UI text and thin lines, Lanczos is the safest pick; for photographic backgrounds, bicubic.

Why downscaling preserves text and upscaling cannot. Shrinking averages information you already have. Even a naive bilinear downscale keeps text legible because every output pixel sees more than one input pixel. Enlarging is the opposite: you ask the algorithm to fabricate detail that was never captured, and every algorithm has to guess. The practical rule is one direction only: capture at or above the largest target dimension and let your tool downscale to the smaller device classes in a single pass.

Figma, Sketch, and Photoshop export settings that keep pixels sharp

Figma. Set the frame to the exact native pixel size — for example 1290 by 2796 for the iPhone 6.9-inch shelf — and export at 1x as PNG. Avoid the temptation to keep a smaller design frame and export at 2x or 3x; that path works in theory but routinely produces files that are a single pixel off the spec and get rejected on upload. Turn on Pixel Preview to spot softness on the canvas before exporting.

Sketch. In the Export panel, untick Trim, fix the slice to the native dimension, set Format to PNG, and Size to 1x. Sketch snaps to the pixel grid by default, so the only common failure mode is exporting a sub-frame instead of the full canvas.

Photoshop. Enable Snap Vectors To Pixel Grid under Preferences → General. Use File → Export → Export As, pick PNG-24, and confirm the canvas matches the target store size before saving. PNG-24 is the right choice for UI work; PNG-8 quantizes colors and softens gradients, and "Save for Web (Legacy)" defaults to 72 PPI metadata which can occasionally trip App Store Connect validation.

Fix blurry iOS screenshot upload before you press submit

Walk through these checks in order before submitting. Stopping at the first one that fails saves a rejection cycle.

App store screenshot resolution requirements by device and store

The full per-device pixel table lives in the App Store screenshot sizes 2026 reference. The table below summarizes the cross-store format and dimension rules so you can plan the export before opening Apple's docs.

Windows-friendly screenshot workflows without Mac-only tools

Why Mac-only workflows fail Windows devs. The standard recommendation — Xcode Simulator, Cmd+S — assumes you have a Mac under your desk. Cross-platform indies who build on Windows are left choosing between renting a Mac in the cloud, uploading raw UI to a browser-based generator, or wrestling with image editors that do not know Apple's current spec. None of those produce pixel-sharp output reliably.

The local capture path. For Android, connect a device and use Android Studio Emulator or scrcpy at native resolution to capture flat PNGs. For iOS-only apps from Windows, TestFlight on a borrowed device plus a cloud iOS simulator that supports image export is the lowest-friction route. In both cases, the raw capture never leaves your machine.

The local processing path. A native desktop app that ships current store presets exports each frame at the exact integer dimension Apple requires, flattens to 8-bit sRGB PNG with no alpha channel, and applies the correct file format — every export is upload-ready by default. No subscription, and the unreleased UI never crosses a third-party server. If App Store Connect still rejects a sharp file, the App Store Connect screenshot rejected guide walks through the metadata and format causes.