HTML Favicon Extractor
Find favicon, touch icon, pinned-tab and web app manifest declarations in HTML source. Add a base URL to resolve relative paths—without contacting the site or loading any extracted resource.
| Kind | Resolved URL / value | Details | Source |
|---|
Review the icon declarations in your HTML
Inspect common browser and platform icon references without opening the destination page.
Matching <link> relations include standard favicons, Apple touch icons, Safari pinned-tab icons and web app manifests. The scanner also reports theme-color and Microsoft tile image/color meta declarations.
With a base URL such as https://example.com/, relative paths are resolved locally so you can read their final addresses. Resolution does not make a request and does not check whether the file exists.
The analyzer scans source as text in a worker. It does not use a live DOM, execute scripts, render pasted markup, or load an image, stylesheet or manifest.
Declarations outside <head> are included but labelled. Entity references in attributes are decoded for common HTML entities and numeric references; malformed or uncommon markup may need a full HTML parser.
How to use the Favicon Extractor
Scan a source file or a copied HTML snippet.
Paste or open HTML
Paste source, drag in a local .html file, or choose Open HTML file.
Optionally add a base URL
Use the page address to resolve relative icon paths. No URL is contacted.
Review or export
Check declarations and notes, then copy or download the JSON report.
Frequently asked questions
It finds link relations for favicons, Apple touch icons, Safari pinned-tab icons and web app manifests. It also reports theme-color and Microsoft tile-image/color meta declarations.
No. The tool scans HTML text only. The optional base URL is used to resolve relative addresses locally; extracted URLs are never fetched or opened.
No. Pasted markup is scanned as source text in a time-limited worker. Scripts are skipped as text, and the markup is never inserted into a live document.
Browsers and common conventions expect most icon and manifest links in the document head. Matching declarations elsewhere are still reported and labelled so you can review their location.
The maximum source size is 1 MiB. Automatic scanning pauses on large input; use Analyze markup to run it manually.