ClientSideTools Privacy-First Browser Tools

Favicon & App Icon Matrix Checker

A complete icon setup spans favicons, Apple touch icons, Android PWA icons, Windows tiles, and Safari pinned tabs. Missing sizes cause ugly fallbacks and can block PWA installation. Paste your head tags and manifest to see exactly what's covered and what's missing.

Technical SEO & Metadata Local processing Your markup is parsed locally. Nothing is uploaded.

Tool interface

Introduction

Icon requirements are scattered across HTML link tags, the web app manifest, and platform-specific meta tags. It's easy to ship with gaps that only surface as blurry home-screen icons or a missing install prompt. This checker audits the entire matrix in one pass.

How It Works

  • All icon <link> tags are extracted via DOMParser.
  • The manifest icons array is parsed from pasted JSON.
  • Found sizes are mapped against a 12-slot required matrix across 5 platforms.
  • Missing sizes generate copy-ready HTML and manifest snippets.

Privacy

Your markup and manifest are parsed entirely in your browser. No content is transmitted, and no icon files are fetched. No API calls, no tracking.

Limitations

  • Cannot fetch icon files to verify actual dimensions or image quality.
  • Cannot fetch a live manifest URL; paste the manifest JSON directly.
  • Does not validate iOS splash screens (startup images).

FAQ

What sizes does Chrome need for PWA install?

Chrome requires a manifest with both 192×192 and 512×512 icons. Both must be present for the install prompt to appear.

Do I still need an .ico file?

Modern browsers support PNG and SVG favicons via link tags, but keeping a fallback favicon.ico at the root helps older browsers and some tools.

Is my markup uploaded?

No. Everything is parsed locally in your browser. Nothing is transmitted.

Related Tools

Version and changelog

  • Version: 1.0.0
  • Last updated: August 12, 2026
  • Changelog: Initial production release.