Favicon & App Icon Generator

A modern, complete favicon setup needs far more than the single favicon.ico file browsers required a decade ago, it needs PNG icons at several specific sizes, a combined ICO file for legacy compatibility, an Apple touch icon for iOS home screens, and a web manifest describing icons for Android and PWA install prompts. This tool takes one uploaded SVG or image and generates that entire set automatically, correctly sized and packaged, ready to drop directly into a website's root folder.

Why one icon size was never actually enough

A favicon shows up in more places than the browser tab it was originally invented for: a small size in the browser tab itself, a slightly larger size in a bookmark list, a much larger size when a page is saved to an iOS or Android home screen, and various in-between sizes across different browsers and operating systems. Serving one fixed-size image for all of these means it either looks blurry when scaled up, or unnecessarily heavy when a tiny 16px context only needed a fraction of that data. This tool generates purpose-sized PNGs, 16, 32, 48, 180, 192, and 512 pixels, so every context gets an image rendered specifically for it rather than one size stretched or shrunk everywhere.

What each generated file is actually for

favicon.ico is a single file bundling the 16, 32, and 48 pixel sizes together, still the format many older browsers and some crawlers look for by default at the site root. apple-touch-icon.png, at 180 pixels, is what iOS uses specifically when a page is added to an iPhone or iPad home screen, without it, iOS falls back to taking an automatic, often unflattering screenshot of the page instead. The 192 and 512 pixel PNGs are referenced by site.webmanifest, the file Android and modern PWA-aware browsers read to determine what icon to show during an install prompt or on a home screen, with 512 specifically used for the larger splash-screen-style icon some platforms display.

How a modern PNG-based ICO file is actually built

An older favicon.ico traditionally stored uncompressed bitmap data internally, which is why older favicons were often surprisingly large files. Since Windows Vista, the ICO format has also supported embedding standard PNG data directly inside the same container structure, which is both smaller and simpler to generate correctly, and is now the approach every modern browser and operating system reads without issue. This tool builds a real, spec-compliant multi-size ICO file using that PNG-embedding approach, containing all three legacy-relevant sizes in one file, exactly as a properly built favicon.ico is expected to work.

Starting from SVG versus a raster image

Both SVG and standard raster formats, PNG, JPG, WebP, work as a source, but starting from an SVG generally produces sharper results at every generated size, since a vector source can be rendered fresh and crisp at each specific target resolution rather than being scaled up or down from one fixed pixel grid. If your source is already a raster image, results will still be correctly sized and functional, just subject to the same scaling limitations any raster resize has, most noticeable if scaling up to the larger 512 pixel size from a smaller original.

Runs entirely in your browser

Every resize, the ICO packaging, and the manifest generation all happen directly in your browser using the canvas API, nothing you upload is sent to a server. If your source is an SVG that needs cleanup first, unnecessary metadata or an oversized viewBox, our SVG Optimizer and SVG ViewBox Fixer are useful first steps, both part of the same SVG & Design Tools collection this tool belongs to.