Image to Android App Icon Generator
Turn an existing logo, illustration or photo into a complete Android icon set — the five launcher densities plus the 512×512 Google Play listing icon, as one ZIP. Runs entirely in your browser.
The Free App Maker Image to Android App Icon Generator turns one square image — a logo, an illustration or a photo — into the six PNG files an Android app needs: 48, 72, 96, 144 and 192 pixels for the five launcher densities, plus a 512×512 Google Play listing icon. It runs in your browser, so the image stays on your device. Free, no account.
—
Step by step
How to convert an image into an Android icon set
The mechanical part takes about two minutes. The part that decides whether the icon actually looks good happens before you upload anything.
- Crop your image to a squareCrop the logo, illustration or photo to a 1:1 ratio at 512×512 pixels or larger before you upload it. The generator scales the image into each square canvas, so a rectangular source is distorted rather than cropped. This is the single most common thing people get wrong here — a wide logo lockup arrives on the home screen squashed.
- Leave room inside the safe zoneKeep the important part of the artwork away from the edges. Launchers and Google Play both mask the icon into a rounded shape, so artwork pushed into the corners can be clipped. If your logo currently sits edge to edge on a transparent background, add padding around it first.
- Upload the image to the generatorDrop the file onto the upload area above or browse for it. PNG, JPG and WebP are accepted. The file is read into browser memory and is not sent to a server.
- Generate all six sizesSelect Generate All Icon Sizes. The tool renders your image into six square PNG canvases: 48, 72, 96, 144 and 192 pixels for the five launcher densities, plus 512×512 for the Google Play listing icon.
- Check the small previews before downloadingLook at the 48 and 72 pixel previews, not the big one. If the shape is unreadable or the fine detail has turned to mush at that size, simplify the artwork and generate again rather than shipping it. Nearly every bad app icon is a good logo that was never checked small.
- Download the ZIP and place the filesDownload the ZIP. Place each launcher PNG in the matching
res/mipmapdensity directory of an Android Studio project, or simply upload the 512×512 file when you build with Free App Maker.
res/mipmap, not res/drawable
Android's own documentation places launcher icons in res/mipmap-<density>/ directories and references them from the manifest as @mipmap/ic_launcher. The practical reason: mipmap resources are kept for all densities rather than stripped to the one the device needs, because a launcher may display an icon at a higher density than the device itself uses.
Source: Android Developers — Create app icons, checked 26 Aug 2026.
Android icon size reference
All required icon sizes for Android and Google Play
Android does not have one icon size. It has five launcher density buckets, and Google Play asks for a separate listing icon on top of them. The five launcher sizes are not arbitrary numbers — they are the 3:4:6:8:12:16 scaling ratio applied to a 48×48 pixel baseline, where the baseline density (mdpi) is 160 dpi and pixels are calculated as px = dp × (dpi ÷ 160). A 48 dp launcher icon is therefore 48 px at mdpi and 192 px at xxxhdpi.
| Size | Density | Use | Included |
|---|---|---|---|
| 512×512 | — | Google Play store listing icon (32-bit PNG, sRGB, up to 1024 KB) | ✓ Yes |
| 192×192 | xxxhdpi | Launcher icon at 4.0× the baseline (~640 dpi screens) | ✓ Yes |
| 144×144 | xxhdpi | Launcher icon at 3.0× the baseline (~480 dpi screens) | ✓ Yes |
| 96×96 | xhdpi | Launcher icon at 2.0× the baseline (~320 dpi screens) | ✓ Yes |
| 72×72 | hdpi | Launcher icon at 1.5× the baseline (~240 dpi screens) | ✓ Yes |
| 48×48 | mdpi | Launcher icon at the 1.0× baseline (~160 dpi screens) | ✓ Yes |
| 36×36 | ldpi | Legacy low-density bucket, 0.75× — rarely targeted today | Not included |
| 1024×1024 | — | iOS App Store listing (not used by Android) | Not included |
Sources: Android Developers — Support different pixel densities and Google Play Console Help — Add preview assets, both checked 26 Aug 2026.
What each of the six files is actually for
People often assume the six files are six copies of the same thing at different resolutions, and that Android picks whichever fits. That is roughly true of the five launcher files and completely untrue of the sixth.
The five launcher files (48 → 192)
These are the icon your app wears on the device: home screen, app drawer, recents, share sheets. Android picks the file matching the screen's density bucket. Ship only one size and the system scales it — up, if the device is denser than your file, which is where soft, slightly blurry icons come from. Shipping all five means every device gets pixels that were rendered for it rather than stretched into place.
The buckets are approximate, not exact hardware specs: a device is sorted into the nearest bucket rather than matching a precise dpi. That is why you supply a ladder rather than a file per phone.
The sixth file (512×512)
This one never ships inside your app. It is the store listing icon, uploaded in Play Console, and it is what people see in search results, top charts and your listing page. Google Play's spec is a 512×512 32-bit PNG in the sRGB colour space, up to 1024 KB. Because it is a marketing asset rather than a device resource, it follows the store's design rules — covered below — and not the launcher's.
What makes an image work at 48 pixels
The hard constraint on an app icon is not the 512 version. It is the 48. At 48×48 pixels — smaller than most favicons — you have room for one idea, and every decision follows from that.
What survives the shrink
- One dominant shape. A single letterform, a simple mark, a bold silhouette. If a viewer has to resolve two things to understand the icon, one of them is wasted.
- High contrast between subject and background. Mid-tone artwork on a mid-tone background disappears at small sizes and against real wallpapers, which you do not control.
- Thick strokes. A 2-pixel stroke at 512 is a quarter of a pixel at 48. It will not render as a line; it will render as a faint smudge, or vanish.
- Generous internal spacing. Gaps close up as the image shrinks. Elements that look separate at full size merge into a blob.
What reliably fails
- Photographs. A photo is thousands of small tonal differences, and small tonal differences are exactly what downscaling averages away. Photos can work as icons only when reduced to a single high-contrast subject filling the frame.
- Wordmarks and taglines. Text under roughly four characters is unreadable at 48 pixels. Your company name is not an icon; its first letter might be.
- A full logo lockup. The horizontal logo with the symbol, the name and the strapline is designed for a letterhead. Use the symbol alone.
- Thin outline styles and fine gradients. Both rely on detail the small sizes cannot hold.
A practical test costs nothing: generate the set, then look only at the 48 and 72 previews at arm's length. If you cannot tell what it is, neither can anyone scrolling their app drawer. Simplify and run it again — the tool is free and there is no limit on attempts.
Adaptive icons and the safe zone
Since Android 8.0, the launcher icon format is the adaptive icon: instead of one flat square, you supply separate layers — a foreground and a background — and the device applies its own mask shape over them. That is why the same app appears as a circle on one phone and a rounded square on another. Android 13 added an optional monochrome layer, used for themed icons that follow the user's wallpaper colours.
The geometry is specific, and it is where most icons get clipped:
- Each layer is 108×108 dp.
- The outer 18 dp on each of the four sides is reserved for masking and for visual effects such as parallax or pulsing.
- That leaves a 66×66 dp safe zone — the area that is never clipped by a mask defined by a device manufacturer.
- Android recommends the logo itself sit between 48×48 dp and 66×66 dp.
In proportional terms, the guaranteed-visible area is roughly the central 61% of the canvas, and the logo should occupy somewhere between 44% and 61% of the width. The practical instruction for anyone converting an existing image: do not fill the frame. Artwork that runs to the edge is artwork you have volunteered for clipping.
Source: Android Developers — Adaptive icons, checked 26 Aug 2026.
PNG, JPG, WebP and vector: what to upload
PNG is the right source format. It is lossless, so nothing is degraded before the tool scales it, and it carries an alpha channel for transparency. Upload at 512×512 or larger — 1024×1024 is better still, because downscaling is reliable and upscaling is guesswork.
JPG works but costs you two things. There is no alpha channel, so anything transparent in the original arrives as solid white. And JPG compression leaves artefacts around hard edges and flat colour — the exact content most logos are made of. Those artefacts get baked into all six outputs.
WebP is accepted and is fine as a source when it is the lossless variety.
Vector files (SVG, AI, EPS) are not accepted here — this tool reads raster images. If your logo exists as a vector, that is the best possible starting point: export it from your design tool at 1024×1024 as a PNG and upload that. You will get a sharper result than anyone starting from a screenshot.
Worth knowing: Android launcher icons are shipped as raster PNGs in the res/mipmap density directories regardless. Vector drawables have their place elsewhere in an Android project, and Google Play wants a PNG for the listing icon, so exporting to PNG is not a compromise — it is the destination format.
Transparency: where it helps and where it hurts
Transparency is genuinely useful in the launcher files, where a transparent background lets the mask and the device's own styling do their work.
For the 512×512 Play Store listing icon, it is a different story — and the widely repeated claim that transparency is banned is not quite right. Google Play's upload spec accepts a 32-bit PNG with alpha, so a transparent file is not rejected outright. The problem is what it looks like: Google Play states that transparent assets display the background colour of the Google Play interface. Your icon then changes appearance depending on the surface behind it and on light or dark mode, which is not a look you chose. Google Play's guidance is to pick a background colour appropriate for your brand rather than leaving it transparent.
The safe rule: give the 512×512 file an opaque background. Not because the uploader will refuse it, but because a transparent one is a design decision made for you by whatever is behind it.
Sources: Android Developers — Google Play icon design specifications and Google Play Console Help — Add preview assets, both checked 26 Aug 2026.
Do not pre-round the corners or add a drop shadow
A common instinct when preparing a store icon is to round the corners and drop a soft shadow underneath, so it looks like it does on a home screen. Both are mistakes, because Google Play does them for you.
Google Play's icon design specification asks for a full square asset, then dynamically applies the rounded mask and the shadow after upload so that every icon in the store is consistent. The mask uses a corner radius of 30% of the icon size — about 154 pixels on a 512×512 asset. If you round your own corners first, you get a rounded shape inside a rounded mask, with awkward gaps at the edges. If you add your own outer shadow, it gets masked and shadowed again.
- Do supply a full square with an opaque background.
- Do not add rounded corners to the asset itself.
- Do not add an outer drop shadow — shadows and lighting inside the artwork are fine.
- Do keep key artwork off the corners, since that is what the 30% radius eats.
Source: Android Developers — Google Play icon design specifications, checked 26 Aug 2026.
Icon problems that can hold up a Play Store listing
Most icon trouble is cosmetic. Some of it is policy. Google Play's Store Listing and Promotional Content policy governs icons and store graphics directly, and these are the icon-specific rules worth knowing before you upload:
- Misleading symbols. Not allowed. The example Google gives is a new-message dot indicator when there are no new messages — a badge designed to make people tap.
- Ranking or store-performance claims. Images or text such as App of the year, #1, or Best of Play 20XX are prohibited in the icon.
- Price and promotional text. Things like 10% off, $50 cash back or free for a limited time only do not belong in the icon.
- Sexually suggestive imagery. Called out explicitly, including suggestive imagery of fetishized anatomy.
- Graphic violence prominently depicted in app icons, promotional images or videos.
- Metadata that misrepresents the app. Your listing has to accurately reflect what the app actually does — an icon implying functionality the app lacks is a metadata problem.
Alongside the policy rules, the practical upload failures are ordinary: a file that is not 512×512, a file over the 1024 KB limit, or a non-PNG. Those are caught at upload rather than in review.
Source: Google Play Console Help — Store listing and promotional content policy, checked 26 Aug 2026.
Policies change and enforcement is Google's call, so treat this as a summary to check against the source rather than a guarantee of approval. We walk through the wider set of causes in why Google Play rejected your app, and how to fix it.
Where this fits in building the app
An icon set is one asset among several. If you are taking an existing site to Android, the icon is usually the third thing you need, after a package name and a privacy policy. Everything below is free to use, with no account:
These tool pages are free with no catch — no account, no watermark, nothing held back. On the main website to APK converter, building and previewing your app is free too; downloading the finished signed APK is a one-time unlock, priced by country and always shown to you before checkout.
FAQ
App icon questions
Written and fact-checked by My Mind Studio. Published 26 August 2026 · Last verified 26 August 2026 against Android and Google Play documentation.
Icons ready? Build your Android app.
Use the website to APK converter to turn your site into an Android app in about 60 seconds — upload your new 512×512 icon during the build. Building and previewing are free.
Build My App — Free →