Free Online Tool

Favicon Checker & PWA Audit

Instantly scan any website to audit its favicons, Apple touch icons, Android/PWA icons, and manifest configuration.

  • Detect missing icons
  • Find broken links
  • Manifest validation
Start Audit Generate Favicons
Favicon checker preview
Audit favicons instantly

Enter Website URL

  1. Enter any website URL or domain (e.g., example.com)
  2. Click "Check Favicons" to audit all icons and meta tags
  3. Review results: ✓ found, ✗ missing, or ⚠ issues detected
  4. Use Favicon Generator to fix missing or broken favicons
Pro Tip: Check favicon.ico (16×16, 32×32), Apple touch icon (180×180), and PWA maskable icon (512×512) for complete coverage!
We only fetch publicly available HTML and icon files. No login or private data is accessed.

About the Favicon Checker

Snipinsta's Favicon Checker audits any website's favicon configuration to ensure cross-browser and cross-device compatibility. Identify missing icons, broken links, and manifest issues in seconds.

  • Deep Scan – Checks HTML, manifest files, and common favicon paths.
  • Issue Detection – Highlights errors, warnings, and missing best practices.
  • PWA Ready – Validates maskable icons and manifest for Progressive Web Apps.
  • Detailed Report – See all detected icons with sizes, types, and HTTP status.
  • Private & Free – No account required. We only fetch public HTML/icons.

Common Favicon Issues We Detect

  • Missing favicon.ico at site root
  • No Apple touch icon (iOS home screen)
  • Missing 512×512 icon for PWA splash screens
  • No maskable icon in manifest
  • Missing theme-color meta tag
  • Broken icon URLs (404 errors)

Required Favicon Sizes

A complete favicon setup should include these files for maximum compatibility:

File Size Purpose Required?
favicon.ico Multi-size Legacy browser fallback Required
favicon-32x32.png 32×32 Modern browser tabs Required
favicon-16x16.png 16×16 Small tab icons Recommended
favicon-96x96.png 96×96 Desktop high-DPI Optional
favicon.svg Scalable Modern vector icon Optional
apple-touch-icon.png 180×180 iOS home screen Required
android-chrome-192x192.png 192×192 Android/PWA icon Required
android-chrome-512x512.png 512×512 PWA splash screen Required
*-maskable.png 512×512 Adaptive icons (Android) Recommended
site.webmanifest — PWA configuration Required
Note: Our checker validates all these files and reports any that are missing or return errors.

Favicon Validation and Troubleshooting

Why Favicon Checking Matters

Favicon validation ensures your website displays correctly across all browsers, devices, and platforms. Missing or incorrectly configured favicons create unprofessional impressions—blank squares in browser tabs signal broken implementations to users. Comprehensive favicon checking tests 15+ file formats and sizes, verifies HTTP response codes (200 OK vs 404 errors), validates manifest JSON syntax, and confirms proper HTML tag implementation.

Different browsers cache favicons at different intervals (Chrome: 24 hours, Firefox: session-based, Safari: indefinite). Our checker performs real-time HTTP requests to detect issues immediately, bypassing local cache. Common problems include incorrect file paths (favicon.ico in wrong directory), MIME type mismatches (serving PNG as ICO), missing CORS headers for CDN-hosted icons, and malformed web manifest files that prevent PWA installation.

What Our Checker Validates
  • File Accessibility: Tests HTTP 200 status for all icon URLs
  • Format Correctness: Verifies ICO, PNG, SVG file integrity and dimensions
  • HTML Tags: Checks <link rel="icon"> syntax and paths
  • Manifest Validity: Parses site.webmanifest JSON structure
  • Apple Touch Icons: Confirms 180×180px PNG for iOS devices
  • Cross-Platform: Tests desktop, mobile, and PWA requirements
Common Favicon Errors
  • 404 Not Found: Files uploaded to wrong directory or renamed incorrectly
  • Wrong MIME Type: Server sending text/plain instead of image/x-icon
  • Incorrect Dimensions: Non-square images or wrong pixel sizes
  • Missing Manifest: No site.webmanifest prevents PWA installation
  • Cache Issues: Old favicon persists despite file replacement
  • HTTPS Mixed Content: HTTP icons on HTTPS sites blocked by browsers

Fixing Favicon Issues

If our checker reports errors: (1) Verify files are uploaded to your site's root directory (https://example.com/favicon.ico), (2) Ensure correct MIME types in server configuration (.ico = image/x-icon, .png = image/png), (3) Check HTML <head> contains proper <link> tags with absolute or root-relative paths, (4) Clear browser cache and CDN cache if using one.

For WordPress sites, use our favicon generator then upload via Appearance → Customize → Site Identity. For static sites, place favicon files in root directory and add HTML tags. For CDN-hosted icons, configure CORS headers to allow cross-origin requests.

Frequently Asked Questions

It scans for favicon.ico, PNG favicons (16×16, 32×32), Apple touch icons (180×180), Android/PWA icons (192×192, 512×512), web manifest files, maskable icons, and meta tags like theme-color and msapplication-TileColor.

Yes! The Favicon Checker is completely free with no account required. Just enter a URL and get instant results.

Use our Favicon Generator to create a complete favicon package with all required sizes. Upload the files to your site's root folder and add the provided HTML code to your <head> section.

Maskable icons allow PWAs to display properly on Android devices with adaptive icon shapes (circles, squares, squircles). Without a maskable icon, your app icon may be cropped or displayed with padding.

No. We only fetch publicly available HTML pages and icon files. No login credentials or private data are accessed or stored.

Check your favicon after: (1) Initial website launch, (2) Rebranding or logo updates, (3) Server migrations or domain changes, (4) Adding PWA functionality, (5) Implementing CDN for icon hosting. Regular quarterly checks ensure files remain accessible and properly configured as browser requirements evolve.

A 404 error means the browser requested favicon.ico from your site's root directory but the file doesn't exist there. Fix this by: (1) Uploading favicon.ico to your root directory (same folder as index.html), (2) Verifying file permissions allow public access, (3) Checking server configuration doesn't block .ico files, or (4) Adding explicit <link rel="icon"> tag pointing to the correct path.

Browsers prioritize different icon formats: Safari prefers apple-touch-icon.png, Chrome uses manifest icons for PWAs, and older browsers default to favicon.ico. If you're seeing inconsistencies, ensure you have: (1) All required formats generated (ICO, PNG at multiple sizes, SVG), (2) Proper HTML <link> tags in correct order, (3) Valid site.webmanifest with icon references, and (4) Cleared cache on all browsers to test fresh loads.
Was this tool helpful?

Your feedback helps us improve our tools