Files stay on your device. Enter send · Esc close drawers
Multi-size .ico for browser tabs
Icon and favicon specifications require multiple sizes in a single bundle so operating systems can pick the resolution that fits the context — taskbar, address bar, app drawer, app switcher. Favicon Pack (16/32/48) packages 3 sizes (16×16, 32×32, 48×48) into one output. Each size is downsampled from your source independently, so small sizes don't blur the way they would if you'd resized once and then sub-sampled. The preset outputs Multi-size .ico entirely in your browser.
| Output format | ICO |
|---|---|
| Multi-size bundle | 16, 32, 48 |
| Processing | 100% in your browser — no upload |
| Cost | Free, unlimited |
| Source | Official guidelines |
This preset is a deterministic recipe — every step has fixed parameters so the result is byte-identical across runs of the same input.
The multi-size ICO bundle is assembled by independently down-sampling your source for each target size (16, 32, 48 px). Sampling each size from the full-resolution source preserves more detail at small sizes than scaling once and then sub-sampling, which is what naive icon converters do.
The encoding runs through canvas APIs and a WebAssembly image-encoder; the source bytes never travel to a server.
Browsers, taskbars, and app drawers each pick the size that matches the context — 16×16 for the address-bar favicon, 48×48 for the high-DPI desktop tab icon. Packing all sizes (16×16, 32×32, 48×48) into one .ico file lets the renderer select natively rather than scaling on the fly.
Drop it at the root of your site as /favicon.ico. Most browsers fetch that path automatically without an explicit <link> tag. Modern setups also reference it explicitly via <link rel="icon" href="/favicon.ico"> in the document head.
Those are separate sizes (200×200 minimum for Apple, 512×512 for PWA install). This preset covers the legacy favicon need; pair it with the PWA-icon preset for full cross-platform coverage.
No. This preset runs entirely in your browser using WebAssembly + canvas APIs — no server round-trip. You can verify this in your browser's network panel: only static asset requests, no image upload. The file never leaves your device.