Explicit icon-tool scope
The auditor checks manifest JSON declarations only; it never fetches icon files or tests PWA installation.
Browser-local processing
Inspect icon declarations for sizes, type, purpose and duplicate entries before deployment. Artwork and selected files remain in this browser session.
Icon files are only part of the browser decision
Browsers and installed web apps choose among favicon, Apple touch icon, and manifest candidates using size, type, purpose, platform policy, and cache state. A file that exists and decodes correctly can still be ignored if the HTML or manifest does not reference it as expected, its declared dimensions are wrong, or the browser prefers a previously cached icon.
Verify the complete package
Check actual pixel dimensions, MIME type, transparency, manifest icons entries, sizes, and purpose values such as maskable. Test a clean browser profile or cache-cleared install path before judging a deployment. Automated checks can catch missing or inconsistent assets, but they cannot predict every launcher crop, dark-mode treatment, pinned-tab behavior, or platform-specific icon mask.