How this tool works
Enter the address at which your favicon image will be served. The generator recognizes SVG, PNG and ICO extensions, writes the corresponding type and escapes the href attribute. Copy the result into the document head, upload the actual image and confirm the image address returns the intended file.
<link rel="icon" type="image MIME type" href="escaped path">A worked example
The input /favicon.svg generates <link rel="icon" type="image/svg+xml" href="/favicon.svg">. A root-relative address uses your own site origin even on deeply nested calculator pages.
Good to know
Code generation only: no logo rendering, asset upload, file existence check, Apple icon creation or browser-cache invalidation. An SVG favicon should be a suitable standalone image; an HTML snippet is not an image file.
The link tag points to an image you actually host
A favicon is an image resource referenced from the document head. This generator prepares that reference for an SVG, PNG or ICO file; it does not turn the site title into artwork. The type is inferred from the file extension and the path is escaped for an HTML attribute.
A root-relative address such as /favicon.svg refers to the same site root from every nested page. A relative address such as ./favicon.svg refers to the current directory, which may differ between a homepage and a deep calculator route. The URL slug generator helps prepare page paths, but it does not upload icon assets.
Verify the image response as well as the HTML
After inserting the tag, check that the image address returns an image rather than a fallback HTML page or a missing-file response. Browser caches can retain an older icon, so an unchanged icon immediately after deployment does not prove the tag is wrong. A new filename can be useful when intentionally replacing a cached asset.
This small generator does not create an application manifest or every platform-specific touch icon. Those assets can have different size and mask requirements. Keep the main favicon recognizable at a small size, and avoid assuming that a detailed full-width logo will remain legible inside a browser tab.
A few questions, answered
Does clicking Generate upload my logo?
No. You must already have or create an image file and publish it at the entered path.
Why prefer a root-relative path on a multipage site?
It points to the same root asset regardless of the current page’s nesting depth.