Check every common favicon path, size, and format at once — before browsers, bookmarks, and home screens show a blank page instead
A missing favicon is a small thing that makes a site look unfinished — a blank tab icon, a generic gray square on an iPhone home screen, or a broken icon in a browser's bookmark bar. Browsers and operating systems check several different places for an icon, not just one file, so it's easy to have a favicon that works in one context and quietly fails in another. This tool checks the icons your page actually declares in its <head>, the handful of default paths browsers fall back to automatically (like /favicon.ico and /apple-touch-icon.png), and your web app manifest if you have one — then decodes each file it finds to confirm its real format and size, including reading the embedded size list straight out of multi-resolution .ico files. Run it after a redesign or a CMS migration to make sure nothing got left behind.
A missing or incorrectly configured favicon may seem like a minor website issue, but it can make your website look unfinished. Visitors may see a blank browser tab, a generic icon when saving your website to a mobile home screen, or a missing image in their bookmarks. These small details contribute to how people recognize and interact with your website.
The challenge is that websites do not always rely on a single favicon file. Browsers, mobile devices, and web applications may look for different icon declarations, default file paths, or entries in a web app manifest. An icon that appears correctly in one location may be missing, incorrectly sized, or unsupported in another.
The Favicon Checker helps you investigate these issues by examining the favicon references declared in your webpage's HTML, checking common default icon locations, and inspecting a web app manifest when one is available. It also examines the image files it finds to identify their actual formats and dimensions, including the embedded image sizes stored inside multi-resolution ICO files.
Whether you manage a WordPress website, an online business, a blog, or a web application, this tool helps you identify potential favicon configuration problems before they affect your site's appearance.
A favicon, short for favorite icon, is a small image associated with a website. It commonly appears in browser tabs, bookmarks, browser history, and other browser interfaces. Depending on the platform and configuration, related website icons may also be used for mobile home-screen shortcuts and installed web applications.
Common favicon formats include:
ICO: A traditional icon format that can contain several image sizes and color depths in one file.
PNG: A widely supported image format suitable for transparent icons.
SVG: A scalable vector format that can remain sharp at different display sizes where supported.
Apple touch icons: Image files commonly used to represent websites saved to the home screen on Apple devices.
The appropriate format and dimensions depend on where the icon will be used. A single file may be sufficient for some basic setups, while a website or progressive web app may need several icon declarations for broader compatibility.
The Favicon Checker examines several sources of favicon information to help you discover missing files, incorrect references, and potential compatibility issues.
The tool inspects the favicon declarations in your webpage's HTML <head> section. These declarations tell browsers which icon resources the website intends to use.
If a page references a favicon at an incorrect path, points to an unavailable file, or uses an unexpected configuration, the checker can help reveal the problem.
This is useful after changing a website theme, moving to a new domain, updating your content management system, or reorganizing image files. Such changes can leave behind outdated favicon URLs even when the rest of the website appears to work normally.
Some browsers may request conventional icon locations when a page does not provide an explicit favicon reference. The checker tests common fallback paths, including /favicon.ico and /apple-touch-icon.png.
This helps you discover whether an expected icon file exists even when it is not referenced in the page's HTML.
However, default paths are conventions rather than a guarantee that every browser will request the same files. A missing fallback file does not automatically mean your website has no working favicon if its HTML declares a valid alternative.
Web applications can use a web app manifest to declare information about the application, including icons used in supported installation and launch experiences.
When a manifest is available, the checker examines its icon declarations to help identify the image resources specified for the application.
This can be particularly useful for progressive web apps and websites that visitors can install or add to their devices. Keep in mind that checking manifest references does not, by itself, establish that every installation requirement or platform-specific behavior is correct.
A filename does not always tell you what an image actually contains. For example, a file with a .png extension might contain data that does not match the expected PNG format.
The Favicon Checker decodes the image files it finds to inspect their actual formats and dimensions. For multi-resolution ICO files, it can read the embedded size list, helping you determine which image sizes are included in the icon.
This information helps you investigate whether a favicon uses an unexpected format, contains unsuitable dimensions, or may need additional icon variants for your intended use.
Favicon behavior can differ across browsers, devices, and operating systems. An icon may be available but still fail to appear as expected because of an incorrect reference, an inaccessible file, an unsupported format, or a platform-specific requirement.
By examining the HTML declarations, common fallback paths, manifest entries, and image properties, the tool provides useful information for troubleshooting these problems.
The results should be treated as a technical inspection of the resources the checker can access, not as a guarantee that every browser will render the icon identically.

Follow these steps to inspect your website's favicon configuration:
Enter your webpage URL. Provide the address of the page you want to check.
Run the inspection. Allow the tool to examine the page's favicon declarations and relevant icon locations.
Review the discovered resources. Check which icon files are referenced in the HTML, found at common fallback paths, or declared in an accessible web app manifest.
Inspect file details. Review the detected image formats and dimensions, including embedded sizes for multi-resolution ICO files.
Investigate potential issues. Look for missing resources, incorrect paths, or icon configurations that do not meet your website's needs.
Correct your website configuration. Update the relevant HTML, icon files, or manifest entries as necessary.
Test again. Rerun the checker after making changes to confirm that the expected resources can be found and inspected.
For the most reliable results, check your homepage and any important page templates that use different HTML configurations.
Missing favicon: Upload an appropriate icon file and reference it correctly in your page's HTML, or configure the relevant icon declaration for your website platform.
Broken favicon URL: Check that the referenced path points to the correct file and that the resource is accessible without an unexpected redirect, permission requirement, or server error.
Incorrect image format: Make sure the file contains valid image data in the format expected by its declaration and intended use.
Unsuitable icon dimensions: Prepare appropriate icon sizes for the browsers, devices, and application features you want to support. Follow the relevant platform's current requirements rather than assuming one dimension works everywhere.
Missing manifest icons: If your website uses a web app manifest, review its icon entries and confirm that the referenced files exist and are accessible.
Outdated icon after an update: Browser caching can sometimes cause an older favicon to remain visible after a replacement. Refresh the relevant browser context, check the actual resource URL, and consider using a versioned filename or updated URL when appropriate.
A favicon is not a substitute for good content, accessibility, performance, or technical SEO. However, it supports visual identity and helps visitors recognize your website across common browsing contexts.
Regular favicon checks are particularly helpful after a website redesign, domain migration, hosting change, WordPress theme update, or web app manifest modification. They can also form part of a broader website maintenance routine.
The Favicon Checker focuses specifically on favicon declarations and image resources. It does not replace a complete website audit, and a successful icon check does not guarantee better search rankings, improved Core Web Vitals, or a particular appearance on every device.

A favicon checker is a tool that examines a website's favicon configuration. It can help identify declared icon resources, check common fallback paths, inspect manifest references, and verify the actual format and dimensions of discovered images.
ICO, PNG, and SVG are common choices, depending on browser support and implementation requirements. Apple touch icons and manifest icons may also be appropriate for particular devices and web application features. Choose formats and sizes based on the platforms you intend to support.
A favicon is not a direct ranking guarantee. Google can use a favicon in eligible search-result presentations, subject to its requirements, but having one does not guarantee that it will appear or improve rankings.
Different browsers and platforms can handle icon declarations, formats, caching, and application icons differently. Check the relevant file references, resource accessibility, image format, and platform-specific requirements.
Yes. The tool can read the embedded size list from multi-resolution ICO files, in addition to decoding discovered image files to inspect their actual format and dimensions.
No. The checker can identify issues in the resources it examines, but it cannot guarantee identical rendering across all browsers, operating systems, devices, or application-installation contexts. Test important configurations in the environments you support.
The Favicon Checker makes it easier to inspect website icon declarations, discover resources at common fallback locations, examine web app manifest entries, and verify image formats and dimensions.
Use it after redesigns, migrations, theme changes, or routine maintenance to catch favicon problems before they go unnoticed. A correctly configured favicon helps maintain a consistent website identity and gives visitors a more polished browsing experience.
Check your favicon configuration, resolve missing or incorrect resources, and keep your website icons ready for the browsing environments you support.