Android App Icon Sizes: The Complete 2026 Guide

Why Android App Icon Sizes Are More Complex Than You Think

Android icon sizing is not a single-number affair. Unlike iOS, where Apple dictates a fixed set of pixel sizes for a uniform device lineup, Android runs on thousands of devices with varying screen densities, launcher styles, and shape masks. Getting your icon sizes wrong means blurry icons on some devices, clipped graphics on others, or outright rejection from the Google Play Store.

This guide covers every icon size you need to ship a polished Android app in 2026, including the adaptive icon system, mipmap resource folders, Play Store asset requirements, and the practical question of whether to use SVG or PNG for your source artwork. Bookmark this page — it is the only reference you will need.

Understanding Android Screen Densities

Android categorizes screens into density buckets measured in dots per inch (dpi). Every icon size you provide maps to one of these buckets. The system selects the closest match for the user's device, scaling up or down if an exact match is unavailable.

Density Bucket	Qualifier	Approximate DPI	Scale Factor
Medium	mdpi	160	1x (baseline)
High	hdpi	240	1.5x
Extra-high	xhdpi	320	2x
Extra-extra-high	xxhdpi	480	3x
Extra-extra-extra-high	xxxhdpi	640	4x

In 2026, the vast majority of active Android devices fall in the xhdpi to xxxhdpi range. However, you should still provide assets for hdpi and mdpi to cover older devices, Android TV, and Wear OS.

The Mipmap Folder System

Android uses mipmap resource folders for launcher icons, not the generic drawable folders used for other image assets. The distinction matters: when a user installs your app, the system may strip out drawable resources for non-matching densities to save space, but mipmap resources for all densities are always retained. This ensures that launchers requesting a higher-density icon (some launchers display icons 25% larger than standard) can find one without upscaling a low-resolution version.

Required Mipmap Folder Sizes

Place your launcher icon PNGs in the following folders inside your project's res directory:

Folder	Icon Size (px)	Use Case
mipmap-mdpi	48 x 48	Baseline density devices
mipmap-hdpi	72 x 72	High density devices
mipmap-xhdpi	96 x 96	Most modern mid-range phones
mipmap-xxhdpi	144 x 144	Most modern flagships
mipmap-xxxhdpi	192 x 192	Highest density flagships

These are the legacy (non-adaptive) sizes. If you are only providing a single-layer icon, these are the PNGs you need. However, in 2026, you should almost certainly be using adaptive icons, which require a different approach.

Adaptive Icons: How They Work

Google introduced adaptive icons in Android 8.0 (API 26) and they are now the standard. An adaptive icon consists of two separate layers — a foreground and a background — each sized at 108 x 108 dp. The system composites these layers and applies a device-specific mask (circle, rounded square, squircle, or teardrop) to produce the final icon shape.

The critical concept is the safe zone. Although each layer is 108 x 108 dp, only the inner 72 x 72 dp area (a centered circle with a 36 dp radius) is guaranteed to be visible after masking. Any important graphic elements — your logo, symbol, or text — must fit within this safe zone. The outer 18 dp on each side can be clipped by any mask shape.

Adaptive Icon Pixel Sizes Per Density

Density	Full Layer Size (px)	Visible Safe Zone (px)
mdpi	108 x 108	72 x 72
hdpi	162 x 162	108 x 108
xhdpi	216 x 216	144 x 144
xxhdpi	324 x 324	216 x 216
xxxhdpi	432 x 432	288 x 288

You provide two images per density bucket — one for the foreground layer, one for the background layer — or you can use a vector drawable (XML-based) that scales automatically. The vector approach is increasingly preferred because it eliminates the need to produce PNGs for every density.

Defining Adaptive Icons in Your Manifest

In your AndroidManifest.xml, reference an adaptive icon XML file:

res/mipmap-anydpi-v26/ic_launcher.xml:

This XML file defines two layers — a drawable for the foreground and a drawable for the background. Android composites them at runtime and applies the device's chosen mask shape.

The foreground layer should contain your icon's main symbol or logo. The background layer is typically a solid color, gradient, or pattern. Keep the background simple — it exists to provide visual padding and to enable animations (like the parallax effect some launchers apply when you tilt the device).

Google Play Store Icon Requirements

The Play Store listing requires a separate high-resolution icon that is not pulled from your APK or AAB. You upload it directly through the Play Console.

Size: 512 x 512 pixels
Format: 32-bit PNG (with alpha)
Max file size: 1024 KB
Shape: Google applies its own rounded-corner mask, so upload a full-bleed square image without baked-in rounding
Content: Must match your in-app icon closely — users expect consistency between the store listing and what appears on their home screen

Additionally, Google requires a feature graphic (1024 x 500 pixels) for your store listing, though this is not an icon. Do not confuse the two.

SVG vs PNG: Which Format Should You Use?

This is one of the most common questions developers ask about Android icons. The answer depends on your workflow and your icon's complexity.

PNG (Raster)

Pros: Universal compatibility, pixel-perfect control, supports complex textures and photorealistic elements, no rendering inconsistencies across devices.
Cons: You must export a separate file for every density bucket. File sizes add up. Any design change requires re-exporting all sizes.
Best for: Icons with complex gradients, textures, subtle shadows, or photographic elements.

SVG / Vector Drawable (XML)

Pros: A single file scales perfectly to any density. Smaller APK size. Easier to maintain — change colors or shapes by editing XML.
Cons: Not all SVG features translate cleanly to Android's VectorDrawable format. Complex illustrations with many paths can cause rendering performance issues. Gradients and effects may render differently across devices.
Best for: Simple, geometric icons with flat colors or simple gradients.

Recommendation for 2026: Use a vector drawable for your adaptive icon layers whenever possible. If your icon is too complex for vectors, use PNGs at all five density buckets. Many teams design in SVG (in tools like Figma or Illustrator), then export to both vector drawable XML and density-specific PNGs as a fallback.

Notification Icons

Notification icons are separate from your launcher icon and have their own size requirements. They must be monochrome — white on transparent — because Android applies the system accent color at display time.

Density	Size (px)
mdpi	24 x 24
hdpi	36 x 36
xhdpi	48 x 48
xxhdpi	72 x 72
xxxhdpi	96 x 96

Place these in drawable folders (not mipmap). A common mistake is using the full-color launcher icon as the notification icon, which results in a solid white or colored blob in the notification shade. Always create a dedicated silhouette version.

Themed Icons (Material You)

Starting with Android 13 and continuing into 2026, Material You themed icons allow the system to apply the user's dynamic color palette to your app icon. To support this, you provide a third adaptive icon layer — a monochrome vector drawable — alongside your foreground and background.

When the user enables themed icons in their device settings, Android replaces your icon's colors with tints derived from the wallpaper. The monochrome layer defines the shape that gets tinted. If you do not provide a monochrome layer, your icon appears unchanged while others on the home screen adapt, making your app look out of place.

Monochrome Layer Guidelines

Same 108 x 108 dp canvas as other adaptive icon layers
Same safe zone rules (keep graphics within the center 72 x 72 dp)
Should be a simplified silhouette of your foreground element
Use a single color (typically black) — the system replaces it with the theme tint

Complete Size Cheat Sheet

Here is every icon asset an Android developer needs in 2026, consolidated into one reference table:

Asset	mdpi	hdpi	xhdpi	xxhdpi	xxxhdpi
Launcher (legacy)	48	72	96	144	192
Adaptive layer (full)	108	162	216	324	432
Adaptive safe zone	72	108	144	216	288
Notification	24	36	48	72	96
Play Store	512 x 512 (single upload)

Common Mistakes to Avoid

After reviewing thousands of Android app icon implementations, these are the errors we see most frequently:

Baking rounded corners into the icon: The system applies the mask. If you round the corners yourself, you end up with a double-rounded effect that looks broken on devices using non-rounded masks.
Ignoring the safe zone: Critical elements placed outside the 72 x 72 dp safe area get clipped on devices using circular masks. Always test with a circle overlay.
Using drawable instead of mipmap: Launcher icons belong in mipmap folders. Using drawable means the system may strip higher-density versions, causing blurriness.
Forgetting the monochrome layer: With themed icons becoming the default on many devices, skipping this layer makes your app look inconsistent on the home screen.
Identical foreground and Play Store icons: The Play Store icon is displayed at 512 x 512 and can include slightly more detail than the small launcher icon. Optimize each for its display context.

Testing Your Icons Across Devices

Before publishing, verify your icons on multiple configurations:

Android Emulator: Test at mdpi, xxhdpi, and xxxhdpi. Switch launcher mask shapes in Developer Options to see circle, squircle, rounded square, and teardrop.
Physical devices: Test on at least one Samsung device (which uses its own launcher and icon shapes), one Pixel (stock Android), and one budget device.
Themed icons: Enable Material You themed icons and confirm your monochrome layer renders correctly.
Dark mode: Ensure your icon looks good on both light and dark home screen wallpapers.

Generating All Sizes with Appilot

Manually exporting icons for five density buckets, two adaptive layers, a monochrome layer, a notification icon, and a Play Store upload is tedious and error-prone. Appilot's icon generator automates the entire process. Design or generate your icon once, and Appilot exports every Android-required asset — correctly sized, correctly named, and organized into the right mipmap folder structure. It also generates the adaptive icon XML and monochrome layer, so you can drop the output directly into your project's res directory.

Final Checklist

Before you submit your next Android app update, run through this list:

Adaptive icon with foreground, background, and monochrome layers provided
All five density buckets populated in mipmap folders
Safe zone respected — critical elements within the inner 72 x 72 dp
512 x 512 PNG uploaded to Play Console (full-bleed, no baked corners)
Notification icon is monochrome white-on-transparent in drawable folders
Tested on circle, squircle, and rounded square masks
Themed icon renders correctly with Material You enabled

Android icon sizing has more moving parts than iOS, but once you understand the system — densities, mipmap folders, adaptive layers, and safe zones — it becomes a repeatable process. Get it right once, and your app will look sharp on every Android device in 2026 and beyond.