One source for every target
Generate Xcode AppIcon, App Store 1024, Google Play 512, and Android mipmap assets in one pass.
App icon resizer
Upload one source icon and generate store plus brand icon ZIPs locally.
What the App Icon Resizer gives you
Organized sizes and folders
Group, name, and package files by Apple, Google Play, or both so design and engineering get the right assets.
Local generation with review
Keep the source in your browser, inspect crops, edges, transparency, and file-size risks, then download PNGs or a ZIP.
Turn one source icon into a complete package
App icon resizing usually fails when sizes, folders, and filenames get mixed. This tool groups iOS AppIcon.appiconset, App Store 1024, Google Play 512, and Android mipmap outputs into clear folders.
Your source icon is read locally in the browser. After generation, download the full ZIP or filter by platform and inspect individual PNG files.
Choose platform scope without mixing file roles
Apple, Google Play, and Android brand resources are not the same file. Apple assets belong in Xcode, Google Play needs a 512 x 512 listing icon, and Android launcher assets are grouped by density.
Once you choose a package scope, the result panel can filter by platform so design, engineering, and ASO teammates can take the right files.
Preview before download to avoid release-week fixes
The result grid previews each PNG on a transparency checkerboard, so transparent pixels are not mistaken for a gray background. Non-square sources are center-cropped, and undersized sources are blocked.
The downloaded README explains where each folder is used and reminds you to review corners, shadows, adaptive icons, copyright, and the latest platform rules.
App icon resizing workflow
Export square full-bleed artwork from the design source when possible. Apple or dual-platform packages need at least 1024px on the shortest side.
FAQ
These answers help you decide whether your source icon is ready, how the files should be used, and which platform rules still need manual review.
Are uploaded app icons stored on a server?
No. This tool reads the image, renders canvas outputs, and builds the PNG ZIP locally in the browser. Refreshing the page clears the file state, and the source icon is not uploaded to a server.
Can I upload the generated files directly to App Store and Google Play?
GooglePlay/app-icon-512.png targets the Play Console App icon upload requirement. For Apple, the more accurate path is to place AppIcon.appiconset in Xcode and submit it with your build to App Store Connect.
What size and format should the source icon be?
Use a 1024 x 1024 or larger square PNG when possible. JPG and WebP are supported, but final handoff is safest when you export full-bleed square artwork from the design source.
Why does the tool not add rounded corners or shadows?
Stores and operating systems apply their own masks, corners, or shadows. Pre-rounding the artwork can cause double clipping, uneven edges, or platform rejection.
What if my source image is not square?
The tool center-crops it to a square without stretching. For final delivery, export square full-bleed artwork from the design source to avoid shifted subjects or clipped edges.
How are transparent icons handled?
Transparency is preserved, and the result preview uses a transparency grid. Before final submission, review the icon on light, dark, and platform-masked backgrounds.
Does this generate Android adaptive icons?
No. It exports Google Play 512 and legacy launcher mipmap PNGs, but it does not generate adaptive icon foreground/background XML pairs.
What happens if the image is too small?
Apple or dual-platform packages require 1024px or larger on the shortest side. Google Play / Android packages require at least 512px. The tool also warns when the Google Play 512 PNG exceeds 1024KB.