The formats are not interchangeable: an iOS app icon, Google Play listing artwork, Android adaptive icon layers, and web favicons serve different purposes. Identify the destination before exporting. Iconise offers a PNG, SVG vectorization, and a ZIP of favicons; those outputs are not a store submission pack for every platform.
Keep four deliverables separate
| Destination | Documented requirement or format | What to prepare |
|---|---|---|
| iOS/iPadOS/macOS app icon | Apple: square 1024 × 1024 px layout. The HIG describes layered design and system-applied masking. | Source artwork and assets needed for appearances and the Xcode project. An export service does not guarantee acceptance. |
| Google Play listing | 512 × 512 px; 32-bit PNG, sRGB, up to 1024 KB. Square image; Google Play applies the mask and shadow. | A listing asset without rounded corners or an added edge shadow. |
| Android adaptive launcher | Two color layers at 108 × 108 dp; keep the logo between 48 and 66 dp. A monochrome layer can support themed icons. | Foreground/background resources and, if needed, a monochrome resource declared in the Android project. |
| Web favicon | Resources declared with `link rel="icon"` and their actual sizes. The browser chooses an appropriate resource; there is no equivalent single mobile app file. | Website files, `link` elements, and, depending on the project, a web manifest. |
What Iconise prepares
The final Iconise screen can download the artwork as PNG, request an SVG version through vectorization, and create a ZIP of web favicons. The pack contains `favicon.ico` (16, 32, and 48 px), PNGs at 16 and 32 px, `apple-touch-icon.png` (180 px), Android Chrome icons (192 and 512 px), and `site.webmanifest`.
Prepare source files and check the exports
- Write down the platform, placement (launcher, store listing, or website), and intended appearances.
- Check that platform’s official documentation for dimensions, masks, and required structure.
- Keep a clean master, then prepare the layers or exports specific to each destination.
- Check the filename, format, dimensions, transparency, compression, and rendered result after integration.
- Test it in the actual project and release flow. An export alone does not show that a store will accept it.
The special case of web favicons
For a website, a browser can choose from multiple `rel="icon"` links based on the declared type and sizes. The Iconise ZIP supplies these resources and a manifest; you still need to add the files to the site and check the paths and rendering. Apple Touch Icons for web clips are separate from iOS app icon requirements.
Common mistakes
- Uploading a favicon PNG as though an Android project has adaptive layers.
- Confusing the Google Play listing asset with the launcher icon installed on a device.
- Drawing rounded corners or a shadow when the platform adds them.
- Treating an SVG vectorization as a hand-built and checked vector master.
- Assuming that one format or dimension guarantees store acceptance.
Once you have listed the destinations, return to the comparison guide and choose artwork that stays legible in those contexts.