Favicon Preview

Load a PNG, JPG, WebP, SVG, or ICO locally and inspect how the artwork reads at small favicon and larger app-icon sizes.

Choose icon image

Choose an imageSmall-size previews help reveal thin lines, tiny text, and low-contrast artwork that may disappear in a browser tab.

Favicon source-size & downsample checklist

Inspect the loaded image dimensions and show whether it can supply common 16, 32, 48, 180, 192 and 512-pixel targets without upscaling.

—Source pixels

—Sizes without upscale

—Largest safe square

Load a favicon image first.

Before shipping the icons

Create from artwork, inspect tiny sizes, generate platform assets, then audit the local package and manifest declarations before deployment.

Local checks are not deployment checks

These tools do not fetch your live site, verify HTTP headers, confirm browser cache refresh, test service workers, or certify installability across every platform.

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.