Website Favicon Checker
Make sure your site’s icon shows up everywhere it should. The checker finds every icon declared in the page – icon, shortcut icon, Apple touch icon and Safari mask icon – plus /favicon.ico, loads each one to measure its real size, checks its status and type, and reads the web app manifest’s icons. It tells you whether Google Search can use an icon (a multiple of 48 px square, or SVG), whether iPhones get a home-screen icon and whether installable app icons exist.
- Encrypted connection
- No sign-up
- Free to use
How to use Website Favicon Checker
- Enter the page address.
- Click “Check favicons”.
- See the icons and their real sizes.
- Add the missing ones.
Website Favicon Checker features
All icon types
icon, apple-touch-icon, mask-icon.
Real sizes
Measured, not just declared.
Google rule
48 px multiples or SVG.
Manifest icons
192 and 512 px.
Safe fetching
Public addresses only, with size and time limits.
Preview
Every working icon shown.
When to use Website Favicon Checker
- Fixing a missing icon in search results.
- Checking a new design.
- PWA preparation.
- Brand reviews.
Website Favicon Checker FAQ
Which favicon does Google use?
One declared in the page that is square and a multiple of 48 px (48, 96, 144…), or an SVG.
Do I still need favicon.ico?
It helps old browsers and tools that request it automatically.
What size is the Apple touch icon?
180 × 180 px PNG.
Why can the declared size be wrong?
The sizes attribute is just a hint; the real file can differ.
One icon, many places
Browsers, search results, bookmarks, home screens and installed apps all use different icon sizes. A small set – SVG, 48 px multiple, 180 px Apple and 192/512 px manifest icons – covers them all.
Create the full set with the Favicon Generator.
How it works: our server downloads the page once through a guarded fetcher that only connects to public addresses, follows a limited number of redirects and stops after a size and time limit. The HTML is then analysed in your browser as inert text – scripts on the page never run and nothing is stored.
What it cannot see: content and resources that a page adds with JavaScript after it loads, pages behind a login, and servers that block automated requests. For those, open the page in your browser, use its developer tools, or paste the page source where the tool offers a paste option.
Use the results as a starting point: fix the items marked red first, review the yellow warnings in context, and run the check again after a change. Requests are rate-limited to keep the service fair; if you check many pages in a row, wait a few minutes.
Related checks on this site cover the rest of a technical review – speed and Core Web Vitals, security headers, structured data, accessibility and SEO signals – so you can work through a whole site audit one topic at a time.
Who it is for: site owners checking their own pages, developers debugging a release, SEO and marketing teams auditing clients or competitors, and students learning how the web works. No account or installation is needed, and the results are plain text and tables you can copy into a report or ticket.