Starting from an SVG is the best possible way to make a favicon, and it is worth understanding why. An ICO holds the same icon at several sizes. When the source is a bitmap, the small sizes are made by shrinking a large one. When the source is a vector, each size can be drawn from scratch at exactly the resolution it needs — no downscaling, no softening.
Rendered, not resampled
That distinction shows up most at 16 pixels, which is the size in a browser tab and therefore the one nearly everyone actually sees. A 16-pixel icon squeezed down from a 512-pixel PNG has soft, muddy edges because every original edge lands between pixels. The same icon drawn directly at 16 pixels puts its strokes on the pixel grid and stays crisp. This tool renders all six sizes from your vector independently for exactly that reason.
What you get
One .ico containing 16, 32, 48, 64, 128 and 256 pixel versions, each stored as PNG data with transparency intact. 256 is the ceiling the format allows. Put it at the root of your site as favicon.ico — browsers request that path on their own even with no markup pointing at it.
Design for the smallest size
- Simplify hard. A 16-pixel square is 256 pixels in total; fine detail, gradients and thin strokes all disappear.
- Most effective favicons are one letter or a single bold shape, often a cropped fragment of the full logo rather than the whole thing.
- Use a square viewBox. A wide logo gets fitted inside the square and centred, leaving empty space above and below.
- Check contrast against both light and dark browser chrome, since transparency means the tab colour shows through.
Make the SVG self-contained first
External references will not resolve. If the file links to a web font, an external stylesheet, or a bitmap sitting on a server, none of it loads — no network requests are made during conversion, by design. Text set in a linked font is the usual casualty. Convert text to outlines in your vector editor before exporting, which is good practice for logos anyway.
Serve the SVG too
Current browsers accept an SVG favicon directly, and it stays perfectly sharp at any size on any display. The sensible arrangement is to declare the SVG for browsers that take it and keep this ICO alongside for the automatic /favicon.ico request, older browsers, and Windows pinned shortcuts. An SVG favicon can also respond to the browser’s dark mode using a media query inside the file, which no ICO can do.
Rendering uses your browser’s own SVG engine and the container is written byte by byte in this tab. Nothing is uploaded, so an unreleased brand mark stays on your machine.