App Icon Size Guide

The App Icon Size Guide is a static cheat sheet listing the most commonly needed icon pixel sizes for iOS and Android apps, along with what each is used for, so you can check it while preparing your icon assets. It's reference material only. The page has no upload, resizing or automatic multi-size generation, and it doesn't check whether your image meets the requirements. You'll export these sizes yourself from a design tool or a development tool.

How to read and use it

1. The page has two tables: 'iOS App Icon Sizes' and 'Android App Icon Sizes'. Each row shows the pixel size on the left (for example 1024×1024) and its purpose on the right.
2. Decide which platform you're shipping to. For iOS use the first table, for Android the second, and if you're building for both, check both.
3. Export a PNG at each pixel size from your design software. It helps to draw one high-resolution master at 1024×1024 or larger and scale down for each size, which stays much sharper than enlarging small images.
4. In the iOS table, the parentheses give the point size and scale, so 60pt @3x means 180×180 pixels. In Xcode's asset catalog, you provide an image of the matching pixel size for each slot.
5. Before submitting to the app stores, follow the reminder at the bottom of the page and check Apple's Human Interface Guidelines and Google's Material Design documentation for the latest standards.

Where the numbers come from

iOS sizes are points multiplied by scale. An iPhone home screen icon is 60pt, so on an @3x screen it's 60×3 = 180 pixels and on an @2x screen 120 pixels. The iPad Pro's 83.5pt @2x is 167 pixels, Spotlight at 40pt @2x is 80 pixels, and Settings at 29pt is 87 pixels @3x or 58 pixels @2x. The 1024×1024 icon is for the App Store listing, and the page notes it can't contain transparency. The Android sizes map to screen density buckets: mdpi 48, hdpi 72, xhdpi 96, xxhdpi 144 and xxxhdpi 192 pixels, while the Google Play listing icon is 512×512. The Adaptive Icon foreground and background layers are 432×432, and the page says the visible area is usually about the central 66%, so keep important content near the middle where different device masks won't crop it.

Supported range and known limits

• It's a static reference table. It doesn't read your files, generate icons or offer a download button.
• The iOS table lists 8 sizes and the Android table 7 entries. That is not every spec Apple or Google requires. Notification icons, smaller iPad icons, other legacy Android specs and newer themed icons are not covered. The page positions itself as a 'core, commonly used' subset.
• Apple and Google adjust their requirements with OS versions. The page carries no last-updated date, so don't treat it as the newest official spec; confirm in the official documentation before submitting.
• It gives pixel sizes and purposes only, nothing about corner radii, safe areas, file format or color space. The system normally applies rounded corners itself, so don't pre-round your artwork.
• The Android part lists the traditional mipmap density buckets, the store icon and the adaptive-icon layer size only; other icons such as small notification icons are not included.
• It doesn't distinguish between native development, Flutter, React Native or other frameworks, each of which may have its own icon tooling and naming conventions.

FAQ: Why can't the App Store icon have transparency?

The page notes that the 1024×1024 listing icon cannot contain transparency. In practice that means exporting with an opaque background that fills the whole image instead of leaving transparent corners. The system handles rounding, so don't draw rounded corners onto the artwork yourself.

FAQ: Why does the 432×432 Android adaptive icon need margins?

An adaptive icon stacks a foreground and a background layer, and the system crops them with a mask whose shape varies (circle, rounded square and so on). The page says the visible area is about the central 66%, so the important part of your logo should sit within that center region because edges may be cut off.

FAQ: Do I have to export every size by hand?

Not necessarily. Modern tooling can often generate the sizes from one large master image, for example Xcode's asset catalog and Android Studio's image asset wizard. This page tells you what each size is for, so nothing gets missed when you do need to prepare them manually. Which sizes you must supply ultimately depends on your toolchain.

FAQ: How does this relate to the Screen Resolution Reference?

It doesn't directly. The sizes here are icon pixel specifications, while the screen resolution reference covers display resolution standards. They serve different purposes.

Privacy and processing

This page has no input fields and doesn't process any files. It simply displays a static table built into the page, makes no network requests, and collects or uploads no data.