Turn one finished app icon into a precise, organized PNG size set.
Upload existing artwork, preserve its proportions with Fit or deliberately crop it with Fill, then export Xcode All Sizes compatibility presets, Android launcher densities, and a separate 512px store preset. No image leaves your browser.
Start with a finished square icon whenever possible. SVG is ideal for clean reduction; a 1024px or larger raster source keeps the largest export from being upscaled.
PNG · JPG · WEBP · SVG / MAX 10 MB / 1024×1024 RECOMMENDED
A size list with honest labels
The presets cover a modern 1024px Apple master, Xcode All Sizes compatibility pixel variants, all six Android legacy launcher densities, and a separate 512px store-size export.
These are flat PNG size presets, not a claim that every file is required by every current project. Modern Xcode can generate smaller variants from one 1024×1024 icon. Android adaptive icons need separate foreground, background, and optional monochrome layers.
The 1024px file follows the modern single-size Xcode path. The remaining unique pixel values mirror Xcode All Sizes compatibility slots, but do not replace their asset-catalog metadata or Icon Composer layers.
The legacy launcher sequence starts at 36px ldpi and ends at 192px xxxhdpi. The 512px file is listed separately because it is a store-size preset, not an Android density bucket.
Legacy launcher densities
Separate store-size preset
One source, controlled reduction
The resizer makes each image from the same settings, so the platform groups stay visually consistent.
Choose PNG, JPG, WebP, or SVG. Use a square 1024×1024 source or larger when possible; the file is read only inside your browser.
Fit keeps the complete artwork and never changes its proportions. Fill crops a non-square source from the center. Preview both platform outputs before rendering.
Generate the size set once, inspect the resulting files, then download individual PNGs, an iOS ZIP, an Android ZIP, or the organized combined package.
Choose the right workflow
Both tools start with artwork, but they solve different jobs. Use this page when the design is finished and pixel dimensions are the only missing piece.
| Scope | App Icon Resizer | App Icon Generator |
|---|---|---|
| Best starting point | A finished app icon that only needs more pixel sizes | Artwork that needs platform packaging and configuration |
| Primary output | Flat, clearly named PNG files grouped by platform | Xcode asset catalog and Android resource package |
| Packaged and adaptive assets | Not generated; a single flat image cannot preserve layer semantics | Creates an Xcode appiconset and Android adaptive resources; it does not create an Apple Icon Composer file |
| When to use it | Quick size conversion, handoff, compatibility, or QA | Initial mobile app asset setup |
Reduction quality, not just dimensions
A large master gives the browser enough pixel information to make clean smaller files while keeping every output aligned to one visual decision.
The browser uses high-quality canvas smoothing and a lossless-first PNG policy, protecting gradients in the 1024px master instead of forcing a 256-color palette.
Image reading, SVG sanitization, resizing, PNG encoding, previews, and ZIP packaging happen locally. The selected artwork is never uploaded to LogoFoundry.
Every PNG is validated by its output dimensions. Store submission rules such as color space, file-weight limits, layering, and device appearance still need platform-specific review.
The labels and caveats on this page were reviewed against current Apple and Android documentation so Xcode All Sizes exports are not confused with modern layered workflows.
Answers about source size, image quality, transparency, Xcode, Android density, and store submissions.
Use a square 1024×1024 image or a larger square master. SVG can also reduce cleanly at every preset. Smaller raster files still work, but the 1024px result must be enlarged and cannot gain detail that was absent from the source.
No. Fit preserves the complete source and its aspect ratio, adding the selected background around it when necessary. Fill also preserves proportions but center-crops the source until the square canvas is covered.
No. Modern Xcode supports a single 1024×1024 app icon and can derive smaller variants. The additional pixel values mirror Xcode All Sizes compatibility slots for teams that still need separately tuned or handed-off flat files.
A 48dp legacy launcher icon maps to 36px at ldpi, then 48, 72, 96, 144, and 192px through the higher density buckets. The separate 512px file is a store-size preset rather than another launcher density.
It has the correct pixel dimensions, but size alone is not enough. Before uploading, also verify the current Play Console requirements for sRGB, PNG format, file weight, full-square artwork, and system-added rounding and shadows.
No. It creates flat PNG size variants. Android adaptive icons require foreground, background, and optionally monochrome layers; Apple's current Icon Composer workflow also preserves layers and appearances that a flat resizer cannot reconstruct.
Yes for this flat PNG export when Preserve Android transparency is enabled. That setting also affects the 512px file; Google Play permits alpha but recommends an opaque background when possible so the icon does not reveal the Play UI background. iOS outputs are always flattened onto the selected opaque color.
No. The source is decoded, sanitized when it is SVG, resized, encoded, previewed, and packaged entirely in your browser. LogoFoundry does not receive or store the image.