App Icon Sizes for iOS, Android and the Web: The Complete 2026 Reference

The short answer: design one 1024 × 1024 pixel square, with no transparency for iOS, and scale it down for everything else. iOS needs sizes from 20 to 1024 pixels, Android launchers need 48 to 192 pixels plus a 512 pixel Play Store image, and the web needs 16, 32, 48, 180, 192 and 512 pixels. This reference explains where each number comes from, so you can check them against your own project instead of trusting a random list.

Why there are so many sizes

Screens differ in pixel density. A "point" on iOS or a "dp" on Android is an abstract unit, and the real pixel count is the point size multiplied by the screen's scale factor. A 60-point iPhone icon is 120 pixels on a 2x screen and 180 pixels on a 3x screen. Android groups screens into density buckets named mdpi, hdpi, xhdpi, xxhdpi and xxxhdpi, with scale factors of 1, 1.5, 2, 3 and 4. A 48 dp launcher icon therefore becomes 48, 72, 96, 144 or 192 pixels. Once you know the base unit and the multiplier, the whole table is just arithmetic.

iOS and iPadOS icon sizes

Apple's App Store icon is 1024 × 1024 pixels in PNG format. It must be square, must not contain transparency, and must not include rounded corners, because the system applies its own corner mask everywhere the icon appears. Submitting a picture that already has rounded corners produces dark or white wedges in the corners once the system rounds it again. An alpha channel, even a fully opaque one in some export settings, is the single most common reason App Store Connect refuses an icon, which is why the generator on this site always flattens iOS icons onto a solid colour.

The on-device sizes, in pixels, are derived from the point sizes:

• iPhone home screen: 60 pt, which is 120 pixels at 2x and 180 pixels at 3x.
• iPad home screen: 76 pt, which is 76 pixels at 1x and 152 pixels at 2x. The iPad Pro 12.9 and 11 inch models use an 83.5 pt icon, which is 167 pixels at 2x.
• Spotlight search: 40 pt, giving 40, 80 and 120 pixels.
• Settings: 29 pt, giving 29, 58 and 87 pixels.
• Notifications: 20 pt, giving 20, 40 and 60 pixels.

Recent versions of Xcode let you supply a single 1024 pixel image in the asset catalog and generate the rest at build time. That is the simplest path for a native app. You still need the individual files if you work in a cross-platform framework that copies assets directly, if you maintain an older project, or if a tool such as a CI pipeline validates files by name. Newer iOS releases also support dark and tinted icon appearances, which are extra 1024 pixel variants in the same asset slot; the generator creates the standard appearance only, and you can reuse the same settings for each variant.

Android launcher icon sizes

Android's baseline launcher icon is 48 × 48 dp. In pixels that is 48 for mdpi, 72 for hdpi, 96 for xhdpi, 144 for xxhdpi and 192 for xxxhdpi. These legacy PNGs live in folders named mipmap-mdpi through mipmap-xxxhdpi and are used by devices running Android 7.1 and earlier, and as a fallback by launchers that ignore adaptive icons. Put launcher icons in mipmap folders, not drawable, because the system may need the higher density versions for large home screens or for launcher animations even on a lower-density device.

Google Play wants a separate 512 × 512 pixel, 32-bit PNG of no more than 1024 KB for the store listing. Google applies its own mask and shadow in the store, so provide a full-bleed square rather than a pre-rounded shape. This image is not the same file as the one inside your app package, and keeping the two visually consistent matters more than keeping them byte-identical.

Since Android 8.0, modern launchers prefer adaptive icons, which are built from a foreground and a background layer, each 108 × 108 dp. The foreground layer in pixels is 108, 162, 216, 324 and 432 for the five density buckets. The next article, safe zones for adaptive and maskable icons, explains why only the middle part of those layers survives masking.

Web icons: favicons, Apple touch icons and PWA manifests

The web has the loosest rules and the longest history. A practical modern set is a 32 × 32 favicon (with 16 × 16 and 48 × 48 as optional companions), a 180 × 180 Apple touch icon, and 192 × 192 and 512 × 512 icons declared in the web app manifest. Chrome uses the 192 pixel icon for the home-screen shortcut and the 512 pixel icon for splash screens, and it will downscale from 512 if needed. Safari ignores the manifest icons for "Add to Home Screen" on many versions and looks for apple-touch-icon, which must be opaque for the same reason iOS app icons must be.

If you want the installed PWA icon to fill a circle or squircle on Android, add a separate icon with "purpose": "maskable" and keep the artwork inside the central 80 percent of the canvas. Do not mark an ordinary icon as both any and maskable in one entry, because a picture designed for the first purpose usually gets clipped under the second.

A minimal head snippet looks like this: a link rel="icon" pointing at the 32 pixel PNG, a link rel="apple-touch-icon" pointing at the 180 pixel PNG, and a link rel="manifest" pointing at your manifest file, whose icons array lists the 192, 512 and maskable 512 images with their sizes and type fields.

The mistakes that get icons rejected or look wrong

1. Transparency in an iOS icon. Flatten onto a solid colour before export.
2. Pre-rounded corners. Supply square art and let each platform mask it.
3. Text too small to read. At 29 or 20 pixels any lettering is mush; use one bold shape or letter.
4. Upscaling a small source. A 256 pixel image stretched to 1024 will always look soft. Re-export the original vector or large raster instead.
5. Art that touches the edge. Masks, rounded corners and drop shadows eat the outer few percent. A little padding keeps the symbol intact.
6. Mismatched versions. If the store icon and the in-app icon differ noticeably, users may suspect a fake listing.

A simple workflow

Draw the icon once as a vector or at 1024 pixels with the main shape comfortably inside the centre. Export a square PNG. Open the app icon generator, drop the file in, pick a background colour that matches your brand, adjust the padding until the preview looks right under all three masks, and download the ZIP. Copy the ios files into your asset catalog, the android folders into res, and the web files next to your HTML. Check one real device before submitting, because masks and launchers differ.

Platform requirements change over time, so confirm the current numbers in Apple's Human Interface Guidelines, the Android developer documentation and the Play Console help pages before a store submission. The values above reflect the long-standing rules those documents describe.