PlayTools

App Icon Generator

Generate iOS and Android app icons from one image: AppIcon sizes including 1024×1024, mipmap densities, and a 512 Play Store asset. Nothing is uploaded.

Runs in your browser — nothing you enter is uploaded

Drop an image here, or click to browse

JPEG, PNG, WebP, GIF or SVG. Stays in your browser.

Where the files go
iOS — drop the ios/ PNGs into an AppIcon.appiconset (or assign by size in Xcode).
Android — copy mipmap-* files into res/, and upload play-store-512.png to Play Console.
PWA — android-chrome 192 and 512 also work as web app manifest icons.

Sizes are generated from your original. A source of at least 1024×1024 stays sharp on the App Store asset.

iOS AppIcon sizes (including 1024×1024 for App Store Connect) and Android mipmap densities plus a 512 Play Store asset. Use a 1024×1024 master for a sharp store listing. Nothing is uploaded.

Advertisement

One master image, every store and launcher size

App Store Connect wants a 1024×1024 PNG. Xcode’s AppIcon set wants a ladder of @2x/@3x sizes. Android wants mipmap-mdpi through xxxhdpi plus a 512 high-res icon for Play Console. Exporting them by hand in a design tool is slow and easy to misname.

This generator writes the iOS filenames Xcode recognises (20@2x through 1024) and Android mipmap files into folders in a ZIP. 40@3x and 60@2x are both 120 pixels; you get two copies with the two names the asset catalog expects.

iOS applies a squircle mask; Android launchers apply adaptive-icon layers. Keep important detail inside a centre safe zone — roughly 20% inset — so glyphs are not clipped. This tool does not emit Android adaptive XML; it gives you the legacy/square PNGs most projects still ship as ic_launcher.

Use a 1024 master. Upscaling a 180-pixel App Store icon to 1024 looks soft and can be rejected. Fill crops a rectangle to square; Fit pads. Transparent padding is useful for glyphs on a coloured system background, but App Store 1024 should usually be opaque.

Website favicons and Chrome extension toolbar icons are different size sets on different pages. Processing is local; large 1024 encodes can take a second on a phone.

These free tools pair well with this page — open them in a new tab to finish your workflow.

Advertisement

Frequently Asked Questions

Which platforms are included?

iOS AppIcon sizes used by Xcode (20@2x through 1024 App Store) and Android launcher densities mdpi–xxxhdpi plus a 512 Play Store graphic. Files are grouped in ios/ and android/ folders in the ZIP.

What about 40@3x and 60@2x? They are both 120px.

They are the same pixel size, so you get two copies with the names Xcode expects: AppIcon-40@3x.png and AppIcon-60@2x.png.

How do I add these in Xcode?

Create or open an AppIcon.appiconset and drop each PNG onto the slot that matches its filename, or assign by pixel size. Upload ios/AppIcon-1024.png in App Store Connect.

Where do Android files go?

Copy each mipmap-*-ic_launcher.png into the matching res/mipmap-* folder. Upload android/play-store-512.png as the high-res icon in Play Console.

Should the source be square?

Yes if you can. Fill mode centre-crops a rectangle; Fit pads it. A 1024×1024 master with safe margin around the glyph looks best on masks (iOS squircle, Android adaptive).

Does this make a favicon or extension icons?

No. This tool is only native app store/launcher icons. Favicon Generator and Chrome Extension Icon Generator are separate pages with those size sets.

Is anything uploaded?

No. Every size is drawn in the browser. A 1024 export from a large photo can take a moment on a phone; wait for the ZIP button to enable.