Android app icon sizes: launcher, Play Store, and adaptive icons

Distinguish launcher and store artwork

The launcher icon is packaged with the app and rendered by the device; the Play listing uses a separate 512 × 512 pixel store icon. Check the current Android developer and Play Console specifications for the required formats and dimensions.

Design adaptive icon layers

Android adaptive icon layers are 108 × 108 dp, with a centered 66 × 66 dp safe zone for key artwork. Provide foreground and background layers, and add a monochrome layer when supporting themed icons.

Avoid clipping at the edge

Do not place a wordmark or important detail where a circular or squircle mask can remove it. Test the icon at small sizes on both light and dark backgrounds before generating the final set.

Validate the project assets

Use Android Studio or the asset-generation workflow for your project to check density variants and manifest references. Recheck requirements when changing target SDKs or preparing a new Play listing.

Understand dp, pixels, and density

Android adaptive icon artwork is defined on a 108 × 108 dp canvas, with important foreground content kept within the centered 66 × 66 dp safe zone. These are density-independent design dimensions; the generated raster resources contain different pixel counts for device densities.

The Google Play listing icon is a separate 512 × 512 pixel upload asset. Keep it visually related to the launcher icon, but validate each destination independently because the Play image and adaptive layers have different delivery and rendering rules.

Check themed icon behavior

For themed icons, Android uses a monochrome layer when the user, launcher, and OS support the feature. Android 13 introduced themed icons for supported launchers, and Android 16 QPR 2 can automatically theme icons that do not provide their own layer; verify the behavior on the OS versions you target.

Preview foreground, background, and monochrome layers on multiple masks and wallpaper tints. A design that relies on its original colors may lose its distinguishing shape when the launcher applies a single tint.

Package the icon through Android Studio

Use the current Image Asset Studio or the project’s documented asset-generation workflow to create launcher resources and adaptive layers. Check the generated manifest references and resource folders rather than hand-copying a single bitmap into every density directory.

Keep the separate Play Store icon export in the listing asset folder. Confirm its dimensions and file constraints in Play Console before upload; launcher resource generation does not create or validate the store listing image.

Preview masks, effects, and monochrome

Inspect the icon against circular and squircle masks and check whether foreground elements are clipped during launcher motion effects. The outer canvas can support those effects, so keep essential detail within the documented safe area.

For themed icons, review the monochrome layer on several tint colors. A filled silhouette with clear negative space usually survives tinting better than a multicolor mark that depends on hue alone.

A reliable Android icon workflow

Keep the foreground, background, and monochrome source layers in the project, generate launcher resources with Android Studio or the chosen build tool, and verify the resulting adaptive icon XML and manifest reference.

Export the Play listing icon separately and track it with the store graphics. This avoids mixing the listing’s upload image with density resources intended for the installed app.

Check more than one launcher

OEM launchers can apply different icon masks and effects. Preview the design under several shapes where possible, and test that the safe-zone mark remains balanced rather than appearing unusually small or clipped.

For Android themed icons, review the monochrome layer with several wallpaper tints and keep a color fallback for launchers or system versions that do not use the themed asset.

Understand the adaptive icon safe zone

Android’s adaptive icon canvas is 108 × 108 dp, with a centered 66 × 66 dp region that remains visible through the supported mask. Keep the important mark inside that area; use the outer region for background and effects that can be clipped.

These dp measurements describe the design canvas, not the pixel dimensions of every generated PNG. Android Studio’s asset tools create density-specific output; validate the generated resources rather than converting dp to one guessed bitmap size.

Add the monochrome layer deliberately

Android themed icons use a monochrome layer when the OS and launcher support the feature. Android 13 introduced themed icons for supported launchers; Android 16 QPR 2 can automatically theme icons that do not provide their own monochrome layer.

The automatic behavior is not a reason to skip testing. Inspect the app on the supported versions, verify your own monochrome result where provided, and check the color fallback when the user or launcher does not use a themed icon.