Reference
February 23, 2026
4 min read
0 views
PWA Icon Size Requirements 2026: Complete Guide
Every PWA icon size you need in 2026 for iOS, Android, and desktop. Complete reference for developers deploying Progressive Web Apps.
By Imagcon Team
Quick Answer:
## Quick Answer At minimum, a PWA needs valid 192x192 and 512x512 manifest icons. In practice, production apps should include multiple standard icons, maskable icons, favicons, and Apple touch icons for full iOS, Android, and desktop coverage.
## Quick Answer At minimum, a PWA needs valid 192x192 and 512x512 manifest icons. In practice, production apps should include multiple standard icons, maskable icons, favicons, and Apple touch icons for full iOS, Android, and desktop coverage. ## Introduction Building a Progressive Web App in 2026 requires meeting strict, continuously evolving criteria to ensure your app is genuinely installable and looks professional across a wildly fragmented ecosystem of devices. While creating a basic web app manifest is straightforward, getting the icon sizes perfectly right is often a headache for developers. Different operating systems (Android, iOS, Windows, macOS) all have vastly different expectations and rendering behaviors. This complete, up-to-date guide outlines exactly which icon sizes you need for a production-ready PWA today. ## The Absolute Minimum Requirements If you just want the browser to stop yelling at you with console errors and simply allow basic installation, the PWA specification strictly requires two specific icon sizes defined in your `manifest.json`: 1. **192x192 pixels:** Used primarily for mobile home screen icons and smaller UI contexts. 2. **512x512 pixels:** Used for generated splash screens, desktop installation dialogs, and scaling down intelligently for various high-density displays. Both absolutely should be in PNG format. ## The "Production-Ready" Manifest Icons For an application that actually looks good everywhere, relying solely on two sizes is highly risky. Browsers try to aggressively scale your 512x512 icon down to fit smaller spaces, which frequently leads to blurry, unreadable, or artifact-heavy results. A robust, fully complete `manifest.json` should include: * `72x72`, `96x96`, `128x128`, `144x144`, `152x152`: These perfectly cover various Android pixel densities and older legacy devices. * `192x192` (Strictly Required) * `384x384`: Often used by Android for the splash screen on ultra-high-density mobile screens. * `512x512` (Strictly Required) ## Android and Maskable Icons In modern Android OS environments, icons are "adaptive." The OS aggressively crops icons into perfect circles, rounded squares, or squircles depending purely on the user's system theme. To fully support this without your icon looking broken, you must provide **Maskable Icons**. These are heavily specific icons designed with a "safe zone" in the center, allowing the edges to be safely cropped off. * **Required Maskable Sizes:** You should provide at least a robust `512x512` maskable icon. * In your manifest, this icon must explicitly include the property `"purpose": "maskable"`. ## iOS and Apple Touch Icons Despite massive improvements to standard PWA support on iOS recently, Safari still heavily relies on the older, proprietary Apple Touch Icon for the "Add to Home Screen" feature. These are completely NOT defined in the manifest, but rather directly in the HTML `<head>`. * **Required Size:** Exactly `180x180` pixels. * **Important Caveat:** Apple touch icons *cannot* have transparent backgrounds. If they do, iOS will aggressively render the transparency as pure, solid black. Always provide an icon with a solid background color for iOS users. ## The Classic Favicon Don't forget the browser tab itself! You absolutely still need traditional favicons for users who don't install the app. * `favicon.ico`: A legacy bundle file containing 16x16 and 32x32 sizes for older browsers. * `favicon.svg`: A modern, highly scalable vector icon for browsers that support it. * `icon-32x32.png` and `icon-16x16.png`: For modern browsers that strongly prefer PNG favicons. ## Conclusion While the "192x192 and 512x512" rule is technically true for just barely passing automated Lighthouse audits, a true 2026 PWA strategy requires a much more comprehensive package. By including a full spread of manifest sizes, a dedicated maskable icon for Android, a solid-background Apple Touch Icon for iOS, and standard tab favicons, you guarantee a flawless native app feel on absolutely any device on the market.