Favicon Generator

In practice, yes. Browsers prefer the PNG link tags, but a bare request for /favicon.ico still arrives from older browsers, feed readers, link-preview bots and crawlers that never parsed your head. The file written here is a real ICONDIR container with the 16, 32 and 48 px images inside, each stored as a PNG rather than a BMP, so the alpha channel survives and the whole thing costs a couple of kilobytes. That clears a recurring 404 out of your access log for about the price of one small image.

Sixteen pixels is roughly three letterforms wide, so a wordmark or a hairline stroke collapses into noise. Crop to the single strongest element of the mark before you generate, and keep the padding slider low, it goes to 25%, but every percent you add comes off a shape that already has almost no room. The artwork is composed once at 1024 px and halved repeatedly down to each target, which is as much as resampling can do for you.

Yes, an SVG with no width or height attributes is treated as 512 × 512 before it is scaled.

It fills the name field in site.webmanifest, and the short_name field beside it. Anything past twelve characters is trimmed for short_name, so open the manifest and check that line if your product name is long.