Generate iOS and Android app icons in all required sizes from a single image.
Upload one square image and the tool scales it down to every pixel dimension Xcode and Android Studio expect for launcher icons and App Store/Play Store listings, then hands back the set for you to drop into your project. It only scales down, never up, so results stay sharp only if your source is already large. The most common surprise: a source image with transparency produces an iOS App Store icon with unwanted see-through corners or a flattened fill, since Apple's icon slot does not composite alpha the way in-app icons do.
A concrete input and expected output from the current implementation.
Input
A single 1024x1024 PNG square logo with no transparency
Expected output
iOS icons at 1024, 180, 167, 152, 120, 87, 80, 76, 60, 58, 40, 29, and 20 px; Android launcher icons at 512, 192, 144, 96, 72, and 48 px
These are the standard pixel sizes Apple's icon size table (points times 1x/2x/3x scale, including the 76px iPad 1x icon and the 1024 App Store icon) and Android's mdpi-xxxhdpi density buckets require; a 1024x1024 source is large enough to cover every target without upscaling.
The generator resizes your source image down to each target dimension; it does not enlarge a smaller source. If you upload something under 1024x1024, the largest outputs (the 1024 App Store icon, the 512 Play Store icon) will be capped at your source resolution rather than upscaled, so image quality degrades at the top end first.
Rather than asking what device or density you're targeting, the tool always resizes to the full iOS set (notification through App Store, 20px to 1024px) and the full Android launcher set (mdpi through xxxhdpi, plus the 512px Play Store listing icon), then packages every file for you to place into the matching asset slots.
No - it produces flat, single-layer PNGs at the legacy launcher sizes. Android 8.0+ adaptive icons need separate foreground/background layers and an XML definition, which this tool does not build; you'd create those separately and use the flat sizes as a fallback or reference.
No. The resizing happens locally in your browser and your source image is never uploaded anywhere. That's distinct from the page itself, which may still load its own scripts, styles, or other resources over the network - it's just your image that stays local.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.