Guide · mobile
Android adaptive icons: foreground, background, safe zone
October 23, 2026 · 11 min read
Adaptive icons are two layers under a launcher-defined mask. Design for the safe zone, not for a single shape preview on your phone. A logo that looks perfect as a circle on a Pixel can still clip on a squircle OEM skin if the foreground is too large.
Foreground vs background
Foreground holds the logo, usually a transparent PNG sized to the adaptive canvas. Background is a solid color or a simple bitmap. Launchers may apply subtle parallax between layers, so busy backgrounds fight the mark.
Keep brand gradients on the background layer when you can; put the symbol alone on the foreground so masks crop predictable empty margin.
Safe zone about 66%
Important content should stay inside roughly the central two-thirds of the adaptive canvas. Outside that, masks and animations may cover edges. Preview at least circle and squircle before you freeze the asset.
This is stricter than PWA maskable's about 80% web safe zone. If you share one master between web maskable and Android adaptive, design to the tighter Android constraint or export two paddings.
Mipmaps and legacy launchers
Ship density-specific ic_launcher.png (and round variants if you support them) alongside anydpi adaptive XML for older platforms. Play's high-res icon (512) is a separate store listing asset. Do not confuse it with the adaptive pair inside the APK.
- ic_launcher_foreground / background (adaptive)
- Legacy mipmap densities as needed
- Play Store 512×512 high-res icon for the listing
Common visual failures
Foreground too large: clipped ears on circles. Foreground too small: tiny mark on shelves. Background that matches the launcher wallpaper: icon disappears. Fix with contrast. Avoid drop shadows baked into the foreground; shadows get masked oddly.