App icon sizes for iOS and Android (2026)

The good news, if you've come here braced for a spreadsheet of forty sizes, is that both platforms have spent years collapsing that table. On iOS you now supply a single master. On Android you supply two layers and let the system do the rest. This page covers what you actually produce, and where each mark can get clipped if you're careless.

iOS: one 1024 master, and Apple generates the rest

The App Store marketing icon is 1024 × 1024 pixels, PNG, square, with no alpha channel and no transparency. You do not round the corners yourself. Apple applies the rounded mask at render time, at every size it shows the icon. Supply a pre-rounded icon and you get a double-rounded result with artefacts in the corners.

Modern Xcode takes that single 1024 source and generates the smaller sizes it needs, so in day-to-day work the 1024 master is the only asset you hand-produce. The smaller sizes still exist under the hood: historically the home screen icon renders at 180 px on the @3x iPhone class and 120 px at @2x, with iPad around 167 px on Pro and 152 px otherwise, plus the smaller Spotlight, Settings and Notification variants. You rarely touch those numbers directly any more, but they explain why a mark that looks fine at 1024 can turn to mud at 40 px: fine detail simply does not survive the downscale.

Design it to survive shrinking

Because the same artwork is scaled across that whole range, keep the mark simple and centred. Text you need to read at small sizes is a mistake. If the icon has to carry a word, it should be a single bold glyph, not a tagline.

Android: 512 for the listing, layers for the device

Android splits the job in two, and the split trips people up constantly.

The listing icon is what the Play Store serves in search and at the top of your page: 512 × 512, 32-bit PNG with alpha. Google applies its own rounded corners and drop shadow to this one, so, as with Apple, you don't bake those in.

The adaptive icon is what a device shows in the launcher. It is built from two 108 × 108 dp layers, a foreground and a background, exported at 432 × 432 px for the highest-density (xxxhdpi) screens. The background layer must be fully opaque; the foreground may use transparency.

The safe zone is the part that matters

Here's the catch. Of that 108 × 108 dp canvas, only the centre is guaranteed to be visible. The outer band, roughly 18 dp on each side, is reserved: different launchers mask the icon into circles, squircles or rounded squares, and they crop into that outer band by different amounts. That leaves a safe zone of about 72 dp in the middle. Keep every meaningful part of the mark, and certainly any text, inside a centred circle within that zone. Push a logo to the edge and some device, somewhere, will slice it.

A useful way to think about it: the background layer fills the whole tile and is always partly hidden; the foreground is your actual mark and lives safely in the middle. Design the foreground assuming the corners will be eaten, because they will be.

Two masks, one habit

Both platforms have converged on the same instruction: supply the icon square and flat, and let the system round it. Bake in your own corners or shadows and you fight the platform for no benefit. Centre the mark, keep it legible small, and give it room inside the safe area on Android.

Pulling a live icon

If you want an existing icon rather than to build one, the app icon downloader pulls an App Store or Play listing icon at native resolution, and the free ripper returns the icon alongside the full screenshot set. For the dimensions of the rest of a listing, see App Store screenshot sizes and Google Play asset specs.