Launching an app usually requires more than one icon file. This checklist helps designers and developers plan the right master artwork, platform variants, dimensions, formats, safe areas, names, and tests for iOS, Android, Windows, progressive web apps, and browser launch surfaces.
Overview
App icon requirements are easy to underestimate because each platform treats an icon differently. iOS commonly applies a rounded mask to a square source image. Android adaptive icons separate the foreground from the background so the system can apply different shapes and effects. Windows may use several tile and shortcut treatments. A progressive web app relies on manifest entries, while browser launch assets can include favicons and touch icons with their own conventions.
The most reliable approach is to create one carefully designed master icon, then produce controlled variants for each delivery system. Do not simply resize a single PNG and assume every platform will render it correctly. A logo that looks balanced at 1024 pixels may become indistinct at 16, 32, or 48 pixels. Likewise, artwork that looks correct on a transparent canvas may disappear against a system-generated mask or a dark browser interface.
Use the table below as a planning baseline, not as a substitute for the current platform documentation or store submission screen. Platform specifications can change, and app projects often have additional requirements based on the SDK, packaging method, operating-system version, or distribution channel.
| Platform or surface | Useful baseline assets | Format and transparency guidance | Safe-area and delivery notes |
|---|---|---|---|
| iOS and iPadOS app icon | 1024 × 1024 px master for store or project workflows; platform-generated smaller sizes may be required in the asset catalog | Use a square PNG workflow unless the current Apple tooling specifies otherwise. Do not rely on a manually rounded corner. | Keep important artwork inside a generous central safe area. The system may apply the corner mask. Confirm the asset catalog and store upload requirements for the release. |
| Android adaptive icon | Separate foreground and background layers; prepare high-resolution source artwork and test the required launcher and store assets | Use the adaptive-icon structure rather than flattening everything into one image. Avoid placing critical details near the mask boundary. | Android launchers can use different masks. Account for the visible, safe, and potentially masked regions. Configure the icon in the application resources and verify the Play listing asset separately. |
| Windows app and tiles | Prepare square icon artwork plus the tile or visual assets requested by the packaging and distribution workflow | Use the formats accepted by the selected Windows packaging tools. Preserve transparency only where the target surface supports it. | Tile layouts and scaling can vary. Check manifest visual-asset entries, shortcut behavior, light and dark backgrounds, and the packaged installation result. |
| Progressive web app | Common manifest candidates include 192 × 192 and 512 × 512 icons, plus any additional sizes required by the target browsers or install flows | PNG is a practical default for broad support. Include a maskable purpose variant when the install experience calls for it, and design its safe zone deliberately. | Declare icons in the web app manifest with accurate src, sizes, and type values. Test installation from the browsers and operating systems you support. |
| Browser and launch assets | Favicon candidates such as 16 × 16, 32 × 32, and a larger source; an Apple touch icon is often prepared at 180 × 180 | Use ICO, PNG, or SVG only where the browser and implementation support it. Avoid assuming SVG favicon support is identical across environments. | Connect each file with the correct HTML link or manifest entry. Test tabs, bookmarks, pinned shortcuts, mobile home screens, and dark browser UI. |
For related browser assets, use the website favicon setup guide. If the same project includes product screenshots, the product screenshot mockup guide can help keep store presentation assets consistent with the icon system.
How to estimate
Treat icon production as an asset-planning exercise. Before opening an export dialog, count the surfaces you actually need and separate source files from delivery files.
- List the destinations. Record whether the release includes iOS, Android, Windows, a PWA, browser tabs, mobile shortcuts, or all of them.
- Count the icon systems. A flattened iOS icon, an Android adaptive icon, a Windows tile set, and a PWA manifest icon are different deliverables even when they share the same visual concept.
- Estimate variants. For each system, note normal, dark-background, light-background, maskable, monochrome, or high-contrast variants that your supported workflow may need.
- Add test exports. Include at least one small-size render for each major family. A visual review at 16, 32, 48, and 64 pixels often reveals problems that are invisible in the master artwork.
- Reserve review time. Add a separate check for packaging, manifest paths, store previews, installed shortcuts, and real devices. Exporting files is not the same as delivering a working icon.
A simple planning formula is:
Total planned deliverables = platform families + visual variants + test renders + documentation files.
For example, a project supporting iOS, Android, and a PWA might have three platform families, one Android layer pair, one maskable PWA variant, several raster sizes, and a short handoff document. The formula does not predict a store’s exact upload count; it prevents the team from budgeting only for the master artwork.
Inputs and assumptions
Gather these inputs before finalizing the icon:
- Brand constraints: approved colors, logo rules, minimum clear space, and whether the mark can be simplified.
- Supported surfaces: operating systems, browsers, device categories, store listings, desktop shortcuts, and installed web-app experiences.
- Mask behavior: whether the platform applies a circle, squircle, rounded square, tile crop, or another system treatment.
- Layer requirements: whether the destination needs a flattened image, separate adaptive layers, a monochrome mark, or a maskable icon.
- Background assumptions: light, dark, transparent, branded, and system-controlled backgrounds.
- Technical handoff: file names, folder structure, color profile, pixel dimensions, manifest paths, and the person responsible for implementation.
Use a square master canvas, but do not fill every available pixel with important detail. Keep the focal mark visually centered and leave room for system masks. If the icon contains type, test whether the text remains recognizable at the smallest intended size; in many cases, a symbol-only variant is more effective.
Export raster files at the exact requested pixel dimensions rather than relying on a browser or operating system to perform the final resize. Keep a lossless master and an editable source file separate from delivery assets. For broader guidance on choosing PNG, SVG, WebP, and other formats, see the web image format comparison.
Worked examples
Example 1: A native iOS and Android launch
Start with a 1024 × 1024 master containing a simplified symbol and a solid background. For iOS, place the square artwork in the project’s icon asset workflow and let the supported tooling generate or request the required sizes. For Android, decide whether the artwork benefits from an adaptive foreground and background. If it does, separate the layers and test them under more than one launcher mask. Then inspect both icons on a light home screen and a dark home screen.
The quality decision is not simply whether the files export successfully. Check whether the symbol has enough contrast, whether the visual weight remains centered after masking, and whether the Android foreground appears too large or too small when the launcher applies its crop.
Example 2: A PWA with browser launch support
Prepare a standard manifest icon set and a maskable version if the install experience requires one. Declare each file with an accurate size and MIME type, then verify that the manifest path is correct from the deployed site rather than only from a local design folder. Add browser favicon links and a mobile touch icon where appropriate. Test installation, a browser tab, a bookmark, and a home-screen shortcut.
In this case, the most common failure is not poor artwork but incomplete connection: a correctly exported PNG that is missing from the manifest, has an incorrect path, or is labeled with the wrong dimensions may not be selected by the browser.
Example 3: A rebrand with a small-size problem
Suppose the new logo includes a thin outline and a narrow wordmark. At full size it looks clear, but the 32-pixel and 16-pixel renders lose the outline and turn the wordmark into noise. Create a compact symbol variant, increase its stroke weight, simplify interior gaps, and compare it against the old icon at actual display size. Document the exception so the compact mark is not mistakenly treated as a separate brand logo.
For accessibility and legibility checks across related interface graphics, review the design asset accessibility checklist. An icon should not carry essential meaning through color alone when it is used with labels or controls.
When to recalculate
Revisit this checklist before every app launch, rebrand, major operating-system update, packaging change, or store submission. Also recalculate when the project adds a new platform, changes its browser support policy, introduces dark mode, or moves from a website shortcut to an installable PWA.
At the start of each release, confirm the current platform documentation, store upload fields, manifest guidance, and packaging-tool behavior. Treat the dimensions in this article as planning references, not permanent contractual requirements. A quarterly review is a practical maintenance habit, with an additional review after a major platform release.
Before handoff, complete this final action list:
- Open every master and delivery file at 100% zoom and at its smallest target size.
- Preview icons on both light and dark backgrounds.
- Test system masks, adaptive layers, and maskable safe zones.
- Confirm exact pixel dimensions, file formats, color treatment, and transparent areas.
- Verify manifest entries, HTML links, package resources, and store-upload fields.
- Install the app or PWA on representative devices and inspect tabs, shortcuts, launchers, and settings screens.
- Record the source file, export date, platform targets, and the next review trigger in the handoff notes.
A disciplined icon checklist reduces last-minute resizing and makes future releases easier. Keep the master artwork editable, keep platform variants clearly named, and repeat the visual and technical checks whenever the surrounding platform changes.