Favicon Package Auditor

Coverage checks are practical packaging checks, not a guarantee of browser/platform behavior or correct deployed HTML.

Select favicon/app-icon package files

0Files

0/6Core checks

—Square images

NoManifest file

File	Kind	Dimensions	Bytes

Choose local filesNo files are uploaded. The audit reads only the selected package files in this browser.

Local icon package matrix & missing-file checklist

Inspect selected icon files locally, record raster dimensions and file sizes, detect duplicate dimensions, and surface common package files that are absent.

Icon package files

—Files

—Raster decoded

—Duplicate dimensions

—Common names missing

Ready.

File	Type	Bytes	Dimensions	Issue

Explicit icon-tool scope

The package audit inspects user-selected local files, names and dimensions. It is intentionally not a remote favicon checker.

Browser-local processing

Inspect actual local files and dimensions before uploading a favicon/app-icon package. 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.