Web browsers do not discover this asset automatically. It must be declared inside a JSON configuration file known as the (typically named manifest.json or manifest.webmanifest ).
: This icon is defined within the manifest.json or manifest.webmanifest file. Browsers use this manifest to understand how the app should look and behave when "installed". icon-192x192.png
While favicons historically were tiny (16x16 or 32x32), the 192x192 pixel size is the standard baseline for mobile devices. It is high-resolution enough to look crisp on most Android and iOS devices without carrying a massive file weight. Chrome, for instance, requires at least a 192x192 icon to trigger the "Add to Home Screen" install prompt. Implementing icon-192x192.png in a PWA Web browsers do not discover this asset automatically
As devices evolve to foldable screens and ultra-high DPIs (960 DPI+), Google may bump the requirement to icon-384x384.png or support SVG icons natively. However, as of 2025, the Android compatibility definition document (CDD) still mandates that launchers support 192px icons. Browsers use this manifest to understand how the
The string is one of the most critical filenames in modern web development. It serves as the definitive standard asset size required to build an installable Progressive Web App (PWA). Without this explicitly dimensioned image, browsers like Google Chrome and Microsoft Edge will refuse to trigger the native app installation prompt for mobile users. What is icon-192x192.png?
Android Oreo (8.0+) introduced adaptive icons that can be masked into circles, squiggles, etc. If your icon has critical elements near the edges, they may get cut off. To test:
To enable this icon, it must be declared in your manifest.json file. The file should be placed in your project structure, commonly within an assets or icons folder.