filetity

SVG -> ICO · Local tool

SVG to ICO

Turn an SVG into a favicon holding every size, each one drawn from the vector.

Last updated

  1. 01 / Your device

    the file stays here

  2. 02 / Browser memory

    the work runs locally

  3. 03 / Back to you

    saved on this device

When you would use this

Situations, not settings.

A new site that needs a favicon.ico
The logo already exists as an SVG. The browser still asks for /favicon.ico before it reads a line of your HTML.
A Windows app or shortcut icon
Windows wants an ICO with several sizes inside it, and picks the one that fits the place it is drawing.
An old favicon that looks rough at 16 pixels
One made by scaling a big PNG down goes soft. Drawn from the vector at 16, the strokes land on whole pixels.

How it works / no cloud

A conversion engine, not an upload form.

The SVG is drawn six times, once at each icon size, rather than rendered once and scaled down. A renderer given a 16 pixel box hints and snaps strokes for 16 pixels, and the same artwork rendered at 256 and resampled to 16 is mush next to it, which matters because a favicon is mostly looked at 16 pixels wide. Each render is written as a PNG payload inside the ICO container, which is what keeps transparency. The SVG is loaded as an image rather than into the page, so any script or remote reference inside it is inert.

  • Offline ready
  • Installable app
  • No file limit queue

Straight answers

No accordion. Nothing hidden.

Is it free?
Yes, with no watermark and no page limit.
Does it need an account?
No. There is no account system.
Is my file processed on my device?
Yes. The file is read by your browser and never uploaded. There is no server to send it to.
What formats are supported?
SVG in. ICO out, holding 16, 32, 48, 64, 128 and 256 pixel versions in one file.
What are the limits?
Every size is produced, because a vector has no resolution to run out of. An SVG that references a remote font or image is drawn without it, since the file is loaded inert for safety. Very complex artwork renders slowly at 256 but still renders.
Does it work on mobile?
Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
Does it work offline?
Yes. Nothing is downloaded to make this work, so it keeps working with no network connection once the page has loaded.
Why is SVG a better favicon source than PNG?
Because a vector has no resolution to run out of. Our PNG to ICO page deliberately leaves out any size larger than the image you gave it, since upscaling a 48 pixel PNG to 256 makes a blurry icon and shipping that is worse than shipping fewer sizes. An SVG has that limit removed: all six sizes are drawn from the artwork itself, so the 256 pixel version is as sharp as the 16.
Do I still need an .ico if I have an SVG favicon?
Usually yes, and for one specific reason: a browser looking for favicon.ico at the root of your site does not read your HTML first. Modern browsers will use an SVG you declare in a link tag, but the bare request to /favicon.ico still happens, and so do bookmarks, Windows shortcuts and a long tail of readers and crawlers that only understand ICO. Ship both.
Does it scale down or draw each size separately?
Each size is drawn separately. That is the whole point of starting from a vector. Rendering once at 256 and resampling would throw away the thing an SVG is for, and small icons are exactly where hinting and stroke snapping decide whether a shape reads at all.
What happens to transparency?
It is kept, with a real alpha channel. The sizes are stored as PNG payloads inside the ICO container, which every Windows since Vista reads, and nothing is painted behind the artwork. An icon sits on a light desktop, a dark dock and a tab strip, and a white square behind a logo would show on two of the three.

How this one works

Keep working locally

7 available · more coming