Does this include favicon.ico?
Yes. The ZIP includes favicon.ico along with the core favicon PNG sizes.
Is this a full app icon pack?
No. The Favicon Converter focuses on the favicon and web-icon layer rather than the broader mobile app asset pack.
What input formats does it accept?
It accepts PNG, JPG, SVG, and WebP source images, so you can start from vector or raster files.
Does this upload my image?
No. The Favicon Converter runs entirely in your browser, so your image is never uploaded.
Is the Favicon Converter free?
Yes. It is free to use, private, and fully client-side with no sign-up.
What exactly is in the ZIP?
favicon.ico containing the 16, 32, and 48 pixel entries, plus six standalone PNGs: 16, 32, 48, apple-touch-icon at 180, and Android Chrome icons at 192 and 512. That is the practical set a small site or landing page needs.
What HTML do I need to add?
The ZIP does not include the snippet, so at minimum drop favicon.ico at your site root, where browsers find it without any tag, and add a link for the apple-touch-icon and the 32 pixel PNG. The Android 192 and 512 icons are only picked up when they are referenced from a web app manifest.
Should the favicon have a transparent background?
For the browser tab, transparent is fine and often better, since it adapts to light and dark tab bars. For apple-touch-icon.png it is a problem, because iOS composites a transparent home-screen icon onto black. If you expect home-screen installs, export with a solid background.
I fed it an SVG. Why are there no SVG files in the ZIP?
Because the pack is a raster bundle. The SVG is rendered to a bitmap first and every output is a PNG or an ICO. A modern SVG favicon, referenced with rel="icon" type="image/svg+xml", is worth adding by hand alongside this pack, and it is the only one that stays sharp at any size.
Is my logo uploaded to build the bundle?
No. Every size is rendered on a canvas in your browser, the ICO container is assembled locally, and the ZIP is built in the tab. The image never leaves your machine.