Overview
Takes one uploaded image and produces what a Google Play listing and an Android launcher need: the 512×512 store listing icon, a 1024×500 feature graphic, adaptive foreground and background layers at all five densities, and legacy round launcher icons.
How It Works
Upload one image through the file input — 512×512 or larger is recommended — and download the package. It follows a fixed layout: playstore/ holds icon-512.png and feature-graphic-1024x500.png, while android/mipmap-*/ holds the launcher layers for mdpi through xxxhdpi.
Step-by-Step Usage Guide
- Upload your master image — one image drives every output, so pick one that reads well square and under a launcher mask.
- Download the package and note the split: playstore/ for listing assets, android/mipmap-*/ for launcher layers.
- Upload icon-512.png and feature-graphic-1024x500.png in Play Console as the listing icon and feature graphic.
- Copy the mipmap folders into your app and reference them from your own adaptive-icon XML.
Technical Specifications & Standards
Adaptive launcher icons are split into two layers per density, rendered at 108, 162, 216, 324, and 432 px. The foreground is drawn with 25% padding applied at render time so your art stays inside the adaptive safe zone (the 66/108 rule the tool's footnote cites). The background layer is a plain solid white square — your image is not drawn into it, and you do not choose the colour. Foreground PNGs and the 512 listing icon keep source transparency, while only the feature graphic (on near-black) and the background layer are opaque. Legacy round icons at 48 to 192 px, circle-clipped, cover launchers that predate adaptive icons.
Targeted Use Cases
- Creating a Play Console listing: the 512×512 icon and 1024×500 feature graphic both derive from the single upload.
- Filling mipmap folders: foreground and background layers at all five densities, generated in one pass.
- Supporting older devices: legacy round icons from 48 to 192 px keep pre-adaptive launchers rendering a circle.
- Safe-zone planning: with 25% padding enforced at render, full-bleed art survives the launcher mask without losing the subject.
Notes & Gotchas
- Plan to wire the XML yourself: no ic_launcher.xml or adaptive-icon XML is generated — reference the produced foreground and background drawables in your own resources.
- There is no safe-zone overlay preview. The 25% padding is enforced at render, so verify the masked result on a device or emulator.
- Remember which files keep alpha: the foreground PNGs, the 512 listing icon and the legacy round icons do; the feature graphic is flattened on near-black and the background layer is a solid white square.
- Upload is a plain file input with no drag-and-drop, and the feature graphic is letterboxed on near-black — choose a master that survives both treatments.
Frequently Asked Questions
Does it generate ic_launcher.xml?
No. Only PNG layers are produced. Write the adaptive-icon XML in your project and point it at the generated foreground and background drawables.
Why is my feature graphic letterboxed?
The 1024×500 canvas rarely matches your image's aspect ratio, so art is letterboxed on a near-black background rather than stretched or cropped.
What does the 25% foreground padding do?
Adaptive icons mask the outer region, so the foreground is padded to keep art inside the safe zone — the 66/108 rule.
Which outputs keep transparency?
The foreground PNGs, the 512×512 listing icon and the legacy round icons. The 1024×500 feature graphic is flattened on near-black, and the background layer is a solid white fill with no artwork.