ICO Converter Guide: JPG, PNG, SVG & WebP
Convert any image to a favicon or Windows ICO — JPG, PNG, SVG, WebP — free, private, right in your browser.
Turn a transparent PNG logo into a Windows/favicon ICO file. Free, instant, private.
Drop your PNG images here
Only PNG files accepted
Alpha channels in your source PNG carry through to every frame of the generated ICO — no white or black fill behind your logo.
One .ico carries the 16, 32 and 48 pixel frames together, so you ship a single asset instead of juggling a separate file per size.
Your PNG never leaves your device. The ICO container is assembled locally using the Canvas API — no upload, no server.
Drop several PNGs at once and download every generated icon individually or together as a ZIP.
Select or drag the .png file you want as an icon — usually a logo or app mark on a transparent background. The browser reads it locally, no upload involved.
The image is drawn onto three canvases at 16×16, 32×32, and 48×48 pixels, preserving transparency, then each is exported as a PNG frame — the same sizes browsers and Windows expect inside an .ico file.
The frames are assembled into one .ico file, with a short directory at the start telling any reader where each size begins — the structure Windows and every browser expect from a favicon.
PNG is the natural source for a favicon or app icon since it already carries a transparent background. People converting PNG to ICO are usually finishing a brand or app identity, not looking for a general-purpose image format.
Most CMS platforms and static site generators still expect a favicon.ico in the site root. Starting from a transparent PNG logo keeps the icon's background see-through instead of boxed in a solid color.
Windows .lnk shortcuts and .exe files require an .ico resource for their icon — a PNG logo needs to be packed into ICO format before it can be assigned as a custom shortcut icon.
Electron Builder, Tauri and similar bundlers all want an .ico for the Windows target specifically — the one format their config won't accept a PNG for, however the rest of the icon set is stored.
Installer builders like Inno Setup and NSIS ask for a standalone .ico alongside whatever else the app ships, usually generated from the same master PNG artwork.
PNG supports transparency. Since most logos and app icons need a transparent background rather than a solid color fill, converting from PNG keeps that transparency intact through to the finished .ico file — a JPG source would always produce an opaque icon.
The converter renders your PNG at 16×16, 32×32, and 48×48 pixels and packs all three into a single .ico file — the standard set for browser favicons, Windows shortcuts, and taskbar icons.
Yes. Each frame is stored as PNG data inside the ICO container, so any transparent background or alpha edge in your source PNG carries through unchanged.
Non-square sources are center-cropped to a square before scaling, since favicons and shortcut icons are always square. For best results, start with a square or near-square logo.
Yes — that's what it's for. Drop it in your site root as favicon.ico and most frameworks pick it up with no config at all; otherwise point a <link rel="icon"> at it. The browser chooses the frame it needs per context, so a tab, a bookmark bar and a pinned shortcut each get a size drawn for them.
No. The PNG is decoded and packed into the ICO container entirely in your browser using the Canvas API. Nothing is uploaded or stored.
Free, instant, no account needed.