App Icon Generator

One image in, every iOS and Android icon size out — including proper adaptive icon layers. Free, and nothing is uploaded.

Every icon generator on the first page of Google does the same three things: it takes your artwork, uploads it to somebody's server, and hands back a zip. That is a strange thing to accept for the single most recognisable piece of branding your product has, usually months before you have announced it. This one never sends the file anywhere — the resizing and the PNG encoding both happen inside your own tab, and you can pull the network cable out after the page loads and it will still work.

The other thing generators get wrong is Android. A launcher icon is not one square any more. Since Android 8 the system wants an adaptive icon: two layers, each 108 dp square, of which the launcher only ever shows the middle 72 dp — and only the inner 66 dp is guaranteed to survive, because every phone manufacturer ships a different mask shape. Ignore that and your logo gets its edges shaved off on a Pixel and again, differently, on a Samsung. This tool exports the two layers at all five densities, keeps your artwork inside the safe zone, and shows you a live mask preview so you can see what actually survives.

On the iOS side there is a trap worth knowing about: a browser canvas is always RGBA, so anything that writes a PNG with canvas.toBlob produces a file with an alpha channel in it, even when every pixel is opaque. Apple rejects that. So the PNG files here are written by hand rather than by the canvas — the iOS set comes out as 24-bit RGB with no alpha channel in the file at all.

Your artwork never leaves this device. Every size is drawn and encoded by your own browser — nothing is uploaded, nothing is stored, there is no queue, no watermark and no signup. The PNG files are written here in the page, which is how the iOS set can be guaranteed to carry no alpha channel at all.

Drop your icon artwork here

PNG, JPG, WebP or SVG. Square works best, and 1024×1024 or larger is what you want.

01Transparency

iOS icons cannot contain an alpha channel. Apple's guidance lists transparency as “No” for iOS and iPadOS app icons, and App Store Connect rejects an upload with an alpha channel (error ITMS-90717). Every iOS file below is written as a 24-bit RGB PNG with no alpha channel in the file at all.

02Artwork size inside the icon
100%
40% · lots of padding100% · edge to edge

Full-bleed is normal for an app icon — the system draws the shape around it. Pull this back if your artwork is a logo that needs breathing room.

03Mask preview

Preview only — every file exports square. Both platforms apply their own mask. If you round the corners yourself you get a double-rounded icon with a pale halo where your rounding and the system's disagree. Android device makers each ship a different mask shape, which is exactly why adaptive icons exist.

04What to export
05Filenames

Watch: how to use this tool

How to use it

  1. Drop in your artwork, or click Choose an image. PNG, JPG, WebP and SVG all work. Use something at least 1024 × 1024 and square — the tool tells you plainly if it is smaller, because upscaling an icon looks bad and no amount of clever resampling fixes it.
  2. Pick what happens to transparency. iOS icons may not contain an alpha channel at all, so those files are always flattened onto the colour you choose. Android launcher icons, the Play icon and favicons can keep their transparency if you want.
  3. Set how much of the square your artwork fills. Full bleed is the normal choice for an app icon; pull it back if your mark is a logo that needs air around it.
  4. Switch the mask preview between circle, squircle, rounded square and square. This is a preview only — every exported file is square, because both platforms apply their own mask and rounding the corners yourself gives you a double-rounded icon.
  5. Check the preview strip. It draws your icon at 180, 120, 87, 60 and 40 real pixels. If the mark turns to mush at 40 px, that is what people will see in Settings and in notifications.
  6. Tick the sets you need. A brand-new Xcode project wants the single 1024 file; an older project, or a Cordova / Flutter / React Native template, wants the full legacy set. Android needs the launcher icons and the adaptive layers, and the Play listing needs its own 512.
  7. Click Generate every size, then download files one at a time or all at once. Each row shows the exact filename and the folder it belongs in, and tells you whether that file carries an alpha channel.

Questions

What size should my source image be?
At least 1024 × 1024 pixels and square. 1024 is the largest size either store asks for, so if your source is that big every other file is a downscale and nothing is invented. If your source is smaller, the 1024 store icon has to be enlarged, and an upscaled icon is visibly soft next to the ones around it on a Home Screen — no resampling filter rescues detail that was never captured. If you have the original vector, export a fresh 1024 PNG from it rather than blowing up a 512. An SVG works directly here too, as long as it carries width and height attributes so the browser can rasterise it.
Do I still need every iOS icon size?
Probably not, and this is the single most confusing thing about iOS icons. Since Xcode 14 a new project's asset catalog has one slot — a single 1024 × 1024 image — and Xcode produces every smaller variant at build time. If you are starting fresh, that one file is the whole job. The full set of 15 explicit sizes still exists in older asset catalogs, and in the templates that Cordova, Flutter, React Native and various CI scripts still generate, so it has not gone away. That is why this tool offers both and labels which is which. If in doubt, open your AppIcon.appiconset and look: if it lists one image, you need one file.
What is an Android adaptive icon and why are there two layers?
Android device makers do not agree on icon shape — one launcher renders circles, another squircles, another rounded squares. Rather than shipping a different icon per manufacturer, Android takes two layers from you, a background and a foreground, each 108 dp square, and applies the device's own mask to them. The two layers also let the launcher animate them independently: parallax as you drag the icon, a gentle pulse when you tap. The masked viewport is the middle 72 dp of the 108 dp canvas, so the outer 18 dp on every side is drawn but never guaranteed to be shown. Android's guidance goes further and says keep your logo inside the inner 66 dp, because that is the region no OEM mask clips.
Why can't my iOS icon have transparency?
Apple's guidance lists transparency as "No" for iOS and iPadOS app icons, and App Store Connect enforces it: an upload with an alpha channel comes back as error ITMS-90717, "Invalid App Store Icon". The system draws the icon's shape and its shadow itself and assumes an opaque square underneath. The awkward part is that a browser canvas is always RGBA, so any tool that writes PNGs the easy way — canvas.toBlob — ships an alpha channel even when every pixel in it is fully opaque, and you find out from a rejection email. This tool writes the PNG bytes itself and emits the iOS files as 24-bit RGB, colour type 2, with no alpha channel present in the file.
Should I round the corners of my icon myself?
No. Export a full square. iOS applies its own rounded-square mask, Android applies whatever mask the device maker chose, and the web applies none. If you round the corners in your artwork as well, the system mask cuts inside your rounding on some devices and outside it on others, leaving a pale halo or a visible double edge. It is one of the most common icon mistakes and it looks amateurish in a way that is hard to name until you see it side by side. The mask preview in this tool exists exactly so you can check your composition against the shapes without baking any of them into the file.
Is anything uploaded or stored?
No. The image is decoded, resized and PNG-encoded entirely inside your browser tab, and each finished file is handed to your downloads folder straight from memory. There is no server that could receive it, nothing is written to storage, and no account is involved. That matters here more than for most converters: an app icon is usually finished long before launch, so uploading it to a free web service means putting your unannounced branding on somebody else's infrastructure, under whatever terms their footer happens to link to.

Built by US APP Team

Need more than a free tool?

We build custom mobile apps for founders and small businesses — idea to live on the App Store and Google Play. Fixed price, no surprises, and you own the code.

Start your app brief Takes about 3 minutes · or book a free intro call