Home Articles Icon Design Android Adaptive Icon Size and Safe Zone (108dp / 66dp)

Table of contents

  • Quick nav

Was this helpful?

Share it with someone who needs it.

Android Adaptive Icon Size and Safe Zone (108dp / 66dp)

A
AppShot Maker
10/23/2026
Android Adaptive Icon Size and Safe Zone (108dp / 66dp)

Why launchers “eat” your logo

Since Android 8, adaptive icons split art into foreground + background layers (plus optional monochrome). OEMs mask them as circles, rounded squares, and more, and may parallax the layers. If the mark sits in the corners, a circular launcher will clip it — that is what the safe zone is for.

This article is the size / safe-zone checklist for design and release. Broader dual-platform specs: iOS / Android icon guidelines. HarmonyOS layered icons: HarmonyOS layered icon guide.

Three numbers to memorize

ConceptValueMeaning
Layer canvas108 × 108 dpFull size of each foreground / background layer
Safe zoneCentered ~66 × 66 dpKeep critical art here; outer ring may be masked away
Mask inset~18 dp per sideHalf of (108 − 66), reserved for shaped masks

Common 4× raster exports:

AssetTypical pixelsNotes
Foreground / background432 × 432 px108dp × 4
Safe-zone guide~264 × 264 px66dp × 4
Google Play store icon512 × 512 pxSeparate: 32-bit PNG, full square; Play adds mask/shadow — do not reuse adaptive layers as-is

Foreground vs background

LayerDoDon’t
BackgroundFull-bleed color, soft gradient, or simple textureBrand type in corners; busy photos
ForegroundCentered mark inside the 66dp safe zoneHairlines on the edge; shapes that only read with corners
TransparencyForeground alpha reveals backgroundHollow foreground that leaves odd masked holes

Parallax can shift the foreground slightly — another reason not to hug the edges.

Do not confuse with Play’s 512 icon

UseSpecCorners
Launcher adaptive icon108dp FG + BG layersLauncher / system mask
Play store listing icon512×512, ≤1024KB, sRGBYou ship a square; Play applies mask + shadow

Classic failure: circular-cropped 512 dropped into the adaptive foreground, or adaptive export with baked round alpha used as the store icon. Screenshot alpha rules are different again — see transparent screenshot rejected.

Export / engineering notes

  1. Build a 108dp (or 432px) two-layer template; hide safe-zone guides before export.
  2. Foreground as transparent PNG; background usually opaque.
  3. Generate mipmap-anydpi-v26 adaptive XML via Android Studio Image Asset (or equivalent) and verify foreground / background drawables.
  4. Install on Pixel (circle), Samsung (squircle), and one odd OEM mask.
  5. Provide monochrome where required so notification trays stay legible.

Self-check

  • Critical art inside ~66dp safe zone
  • Both layers are 108dp logical (or 432px equivalent)
  • No OEM-specific circle baked into adaptive layers
  • Play 512 is a sharp full square without hand-drawn corners/shadows
  • Still recognizable at notification size
  • No iOS preview radius pasted onto Android FG (iOS corner mask guide)

Practical split: one logo → three deliveries

Most teams have a single mark but need launcher layers, Play’s 512, and small tray icons:

  1. Compose inside the 66dp guide on a 108dp canvas; verify under a circular crop.
  2. Design the background layer separately — patterns baked into the foreground tear under parallax.
  3. Derive Play 512 from a centered adaptive foreground, then re-check bleed while keeping orthogonal corners.
  4. Export a flat small size for notifications and confirm monochrome/legibility.

Have QA install on at least two OEM launchers plus Pixel and paste failed crops back onto the safe-zone guide.

Symptom → fix table

SymptomLikely causeFix
Transparent ring on launcherFG not covering / hollow BGFull-bleed BG; transparency only around the mark
Pale edge outside round maskPre-cropped circle used as layerRe-export orthogonal layers
Muddy Play iconHand-drawn shadow + Play shadowRemove baked shadows
Adaptive XML ignoredBad anydpi-v26 wiringRegenerate via Image Asset and diff

Vector vs raster layers

Prefer vector foregrounds when the mark is simple geometry — they scale cleanly into mipmaps. Use raster when you need soft illustration, but author at 432px (or higher) and keep the safe zone honest. Do not upscale a 192px legacy icon into 432px and hope launchers forgive blur; redraw or export from the vector source.

Takeaway

Android adaptive icons are not “draw a circle once.” They are 108dp layered canvases with a 66dp safe zone, plus a separate 512 Play store icon. Keep the safe zone honest and the two pipelines apart, and launcher masks stop surprising you in review builds.

Ready to design your store screenshots?

Try AppShotMaker and turn raw captures into store-ready screenshots in minutes.

On this page

About 13 min read0%

AppShot Maker

App screenshot design tools

  • Ready-made layout templates
  • App Store, Google Play & Android sizes
  • Fast, simple PNG zip export