PNG
ICO
ICO
ЗАГРУЗИТЬ
PNG
Нажмите или перетащите PNG
Ожидание файла
Ожидание конвертации...
Нажмите или перетащите PNG
Tool guide
An ICO holds several copies of the same picture at different scales, and the browser picks whichever one fits the tab strip, the bookmarks bar or a desktop shortcut. That is why a classic favicon.ico still sits in the root of most sites: it covers the places where SVG and PNG icons are ignored — old IE builds, feed readers, pinned Windows tiles. This tool assembles that container from your PNG inside the tab. See also: unpack an existing ICO back into PNG frames, square the logo up before you build the icon, trace the same icon into vector SVG.
At minimum 16×16 and 32×32 — the tab and the bookmarks bar at standard and retina scale. 48×48 serves two masters: a Windows desktop shortcut and Google's crawler, which picks that size for the icon shown in search results. 256×256 covers large tiles and app lists, and Windows Explorer reads entries up to that size. There is no point packing more than five entries: the file grows while the browser still displays only one bitmap.
In the domain root, under exactly that name: browsers and crawlers request /favicon.ico on their own with no markup involved. You can also add a link tag with rel="icon" in the head, which is required if the file lives in another folder or has a different name. Verify updates in a private window — old icons cache for a long time.
The input is restricted to image/png on purpose. JPG has no alpha channel, so the icon would carry an opaque rectangle of background that shows up as a white slab on a dark tab strip. Convert the image to PNG with the neighbouring converter, cut the background out, and only then build the ICO.
Feed it a PNG that already has transparency — the alpha channel is carried into the ICO as is, and nothing paints a white plate underneath. Bear in mind that at 16×16 thin lines on a transparent background nearly vanish; for small scales a solid mark on a filled shape survives better than a delicate outline.
No. The ICO container stores static images only; animation is not part of the specification and not part of this tool. Blinking site icons are made either with an animated GIF referenced by link rel="icon" or by a script swapping the favicon on a timer, and browser support for both is uneven.
No. The PNG is read inside the tab, each scale is rendered on a canvas, and the ICO container's bytes are assembled in page memory and handed over as an ordinary file download. Nothing leaves the browser, so an unreleased logo can be prepared without an NDA in the loop.
It depends on how many entries you pack. A 16 + 32 + 48 set usually lands within 5-10 KB; adding 256×256 pushes the file to 15-40 KB, because the large bitmap is stored uncompressed inside the container. If first-load speed matters, stick to the three small scales.
Before: logo.png at 512×512, transparent background, a letter on a coloured circle
After: favicon.ico with four entries — 16, 32, 48 and 256 pixels, around 15 KB
Before: icon.png at 256×256 plus a custom size of 64 typed into the field
After: favicon.ico holding 16, 32 and 64 — exactly what the corporate portal asks for
Your rating and feedback help decide what to improve next.