Initializing... drag & drop files here
Supports: ICO
ICO is Microsoft's icon container — a directory of small bitmaps in one file, each entry recording its width and height in a single byte, which is why 256x256 is the ceiling and why Microsoft's own icon guidance stops there. AVIF is the AV1 Image File Format, published by the Alliance for Open Media in 2019, which stores AV1-coded pictures inside a HEIF-style ISO base media container. The conversion is straightforward and keeps transparency intact, but it comes with two honest caveats worth reading before you click: an icon is small, and at icon sizes AVIF is not automatically the smallest option.
| Property | ICO | AVIF |
|---|---|---|
| Origin | Microsoft, in use since the earliest Windows releases | Alliance for Open Media, AV1 Image File Format v1.0.0 (2019) |
| Container | Icon directory with one entry per stored image | HEIF-derived ISO base media file format |
| Payload | BMP-style DIB, or a complete PNG for the larger entries | AV1 intra-coded image data |
| Holds multiple images | Yes — several sizes and colour depths in one file | One still image per file (sequences exist but are a separate use) |
| Maximum dimensions | 256x256 per entry | Far beyond anything an icon supplies |
| Transparency | Yes — 8-bit alpha on 32-bit entries, 1-bit mask on older ones | Yes — full alpha stored as an auxiliary image |
| Bit depth | Up to 32-bit (8-bit RGBA) | 8, 10, and 12-bit, wide gamut capable |
| Browser support | Read as a favicon everywhere | Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+ desktop and 16.0+ on iOS, Samsung Internet 14+ |
| Best at | Favicons and Windows app icons | Photographic and gradient-rich images on the modern web |
.ico onto the page or click "+ Add Files" to browse. Multi-size icon files are accepted and several can be queued at once..avif. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.AVIF's compression advantage comes from AV1's intra-frame prediction, and that advantage grows with image area. At icon dimensions there is barely any area to work with, while the container still has to carry its box structure, colour-property boxes, and an alpha auxiliary item. A 64x64 test icon encoded at the default preset came out slightly larger as an AVIF than the same picture saved as a PNG — the format is doing nothing wrong, there simply is not enough image for it to win on.
| Use case | Better choice | Reason |
|---|---|---|
A favicon at /favicon.ico |
Keep ICO — see PNG to ICO | Browsers request the icon file by that path and format |
| A 16-48 px UI sprite | PNG | Smaller than AVIF at that size and universally supported |
| A 256x256 logo on an AVIF-first site | AVIF | Enough pixels for AV1 to pay for its container overhead |
| An icon with a photographic or gradient face | AVIF | Exactly the content AV1's intra coder was built for |
| An icon you will keep editing | PNG | Lossless round-trips, opens in every editor |
.ico is a directory of bitmaps and the decoder reads the first entry, not the biggest — many icon editors write the smallest first. Re-save the icon containing only the size you want, or convert from the original artwork.<picture> element with a PNG or WebP fallback so browsers below the versions listed above still get an image.Yes. AVIF stores alpha as a separate auxiliary image, and the 32-bit RGBA entries inside modern icon files carry their 8-bit alpha channel across intact — including partially transparent anti-aliased edges. There is no Background Color control on this page precisely because nothing needs flattening. If your icon uses only the older 1-bit AND mask, the hard-edged transparency in the source is what you get in the output.
The first image stored in the file. An .ico is a directory of bitmaps at different sizes and colour depths, and the decoder reads entry zero rather than searching for the largest. Because icon editors often write entries smallest-first, a favicon bundling 16x16 through 256x256 can convert at 16x16. If the output is smaller than you expected, export the size you want as its own image and convert that.
Not dependably. Browsers still fetch /favicon.ico by default, and the well-supported alternatives declared through <link rel="icon"> are PNG and SVG. Treat this conversion as a way to bring icon artwork into an AVIF image pipeline, not as a favicon workflow — to build an actual favicon, go the other way with PNG to ICO.
No. Every icon entry is at most 256x256 pixels and most are 16, 32, or 48 pixels across. AVIF is an efficient way to store what is there; it cannot reconstruct detail that was never drawn. Choosing a larger output resolution enlarges the same pixels and softens the edges. For a crisp large graphic, convert from the original artwork rather than from the icon.
A quality value on a 1-100 scale passed to the AVIF encoder: "Very High (Recommended)" is 95, "Highest" is 100, then 90, 80, 70, 60, and 50 for the presets below. On flat icon artwork the difference between 95 and 100 is generally invisible while the file size difference is real, which is why 95 is the default.
It encodes toward the byte target you enter, searching quality settings to land under it, and the "Auto Scale" switch additionally permits reducing the pixel dimensions when quality alone cannot reach the target. On an icon this rarely matters — the file is already a few kilobytes — but it is useful when a CMS or an ad specification imposes a hard byte ceiling.
WebP is the safer middle ground for small graphics: it supports alpha, handles flat colour well, and is supported by a wider range of desktop tools. AVIF pulls ahead on larger images and on photographic content. For a 256x256 logo on a site that already serves AVIF, AVIF is a reasonable pick; for a 32x32 sprite, ICO to WebP or plain PNG will serve you better.
Every file is uploaded over an encrypted connection, decoded and re-encoded on our servers, and deleted automatically a few hours later. There is no sign-up, no watermark, and files are never shared or made public. Icons are measured in kilobytes, so both the upload and the resulting AVIF are small.