The ICO format is still, twenty-odd years after its
creation, the one Windows asks for as an executable's icon and the one many
browsers look for by default at /favicon.ico. The particularity
of ICO is that it's not a single image: it's a container that groups
several resolutions (16, 32, 256 px…) inside the same
file, and the system picks the one it needs depending on where it's shown.
Converting a normal PNG to that format requires a tool that builds that
structure correctly — renaming the file's extension isn't enough.
A common mistake is taking a logo.png and saving it as
logo.ico expecting it to work. It doesn't: a real ICO has a
binary header (ICONDIR) that describes how many images it
contains and at what resolution, followed by each one's data. Without that
structure, Windows and browsers don't recognize the file as a valid icon,
even if the extension says .ico.
app.ico with the 16, 24, 32, 48, 64, 128 and 256 px resolutions embedded in a single file..ico file and use it as a favicon (favicon.ico) or as your Windows app's executable icon.We started from a transparent cutout and with "Use current cutout" Icon Studio generated the icon in every size. The pixel-perfect preview at 128/64/48/32/16 px shows how the detail degrades when shrinking: at 16 px a simple subject with margin works best.
It exports the full set —including the multi-resolution .ico for a favicon— without uploading anything to a server.
For the browser, just upload the favicon.ico to the site's root (or wherever your server points) and, optionally, declare it in the HTML:
<link rel="icon" href="/favicon.ico" sizes="48x48">
Many browsers and crawlers request /favicon.ico directly even
if it isn't declared in the HTML, so it's worth always having it at the
domain root as a fallback, even if your main favicon is a more modern PNG or
SVG.
If you're packaging a desktop application (with Electron, Tauri, .NET or any
other stack), the installer and the executable ask for a multi-resolution
.ico to show in File Explorer, the taskbar and shortcuts. That's
where it shows most if the ICO has few resolutions: an icon that only
includes 256 px looks blurry when scaled down for the taskbar (usually
32 or 16 px), while one with the seven standard resolutions looks sharp
in any context.
An ICO is a container that groups several images of different resolutions (for example 16, 32 and 256 px) in a single file. The operating system or browser automatically picks the resolution it needs depending on where the icon is shown.
Technically you can convert any PNG, but the result looks better if the original is square: if it isn't, the converter fits it inside a square and may add margins or crop the longer edges.
None at the format level: it's the same type of ICO file with embedded resolutions. The difference is where you use it — the browser reads it as a favicon, and Windows reads it as the executable's icon.
No. A real ICO has a binary header (ICONDIR) that describes how many images it contains and at what resolution. Without that structure, Windows and browsers don't recognize the file as a valid icon, even if the extension says .ico.
Convert my PNG to ICO →The full favicon set a modern site needs, with the ready-to-paste HTML.
Every current size in one place, including the Windows .ico set.