App Icon Sizes for iOS, Android, and PWAs

Every platform asks for app icons in slightly different sizes. Submit the wrong dimension and you block a release. Export too few sizes and your PWA install banner or favicon looks soft on high-density screens.

This guide explains the sizes you actually need and how to produce them from one master image.

The core idea: one master, many outputs

Modern workflows start with a single square logo at 1024 pixels or larger. From that master, you derive smaller PNGs for store listings, install prompts, and browser tabs.

You do not need to manually resize in Photoshop for each platform. A browser-based App Icon Generator can export the full ladder locally, with filenames that include the pixel size for easy sorting.

iOS icon sizes

Apple's App Store Connect requires a 1024 by 1024 pixel PNG for the marketing icon shown on the store. This file should be square and should not include transparency for the primary store asset.

Beyond the store icon, iOS apps use many internal sizes through Xcode asset catalogs. Those are often generated inside Xcode from a single source. Still, teams frequently need standalone PNGs for:

• TestFlight release notes
• Press kits and landing pages
• Support documentation

Export 1024px, 256px, and 128px from your master when marketing and product teams need matching assets outside Xcode.

Android icon sizes

Google Play listing icons are commonly submitted at 512 by 512 pixels. Adaptive icons combine foreground and background layers in Android Studio, but the Play Console still expects a high-resolution square PNG for the store listing.

Useful companion exports for Android projects:

If you are building adaptive icons, upload foreground artwork with padding inside the safe zone, then map square exports into Android Studio rather than relying on a single flattened icon everywhere.

PWA and web icon sizes

Progressive web apps declare icons in manifest.json. The Web App Manifest spec recommends at least 512px and 192px entries so install prompts and home-screen shortcuts stay sharp.

Example manifest snippet:

"icons": [
  { "src": "/icons/MyApp-512px.png", "sizes": "512x512", "type": "image/png" },
  { "src": "/icons/MyApp-256px.png", "sizes": "256x256", "type": "image/png" }
]

Pair manifest icons with favicons for browser tabs:

• 32px is the classic favicon size
• 16px still appears on some older UI surfaces
• Apple touch icons often use 180px, which you can approximate with a 256px export scaled in HTML if needed

Keeping favicons and manifest icons visually consistent prevents a polished PWA from showing a blurry tab icon.

Favicon sizes in practice

Favicons do not need a dozen files, but providing multiple sizes improves clarity on retina displays:

• 32px for standard tabs
• 16px for legacy contexts
• 24px and 20px when your design system or embedded web views specify them

Generate the small sizes from the same master logo and verify legibility. Icons with thin lines or small text often need a simplified variant for 16px and 24px exports.

How to export the full set efficiently

1. Prepare a 1024px or larger square PNG
2. Open the App Icon Generator and upload the file
3. Select all required sizes (or trim to your platform checklist)
4. Generate once and download the ZIP
5. Rename or move files into your iOS, Android, or web project folders

Because Vidsembly's generator runs in the browser, your logo stays on your device. That is helpful when icons represent unreleased products or client brands under NDA.

For a walkthrough of each step, see How to Generate App Icon Sizes from One Image.

Common mistakes to avoid

Using a rectangular logo without checking the crop. Center important marks before upload, or export a square artboard from your design tool.

Skipping small-size review. Always open the 16px and 32px exports. If details vanish, simplify the artwork and regenerate.

Mixing different source files across platforms. One master image keeps colors and padding consistent between iOS, Android, and your PWA.

Uploading icons to random online converters. For confidential work, prefer local browser processing over cloud upload tools with unclear retention policies.

Summary

One well-prepared master image plus a consistent export workflow saves hours across every release. Generate the ladder once, verify small sizes, and ship with confidence.