PNG to ICO

Convert PNG or JPG to a Real .ico File

This PNG to ICO converter turns an image into a genuine multi-resolution .ico file — the format browsers expect at /favicon.ico and the format Windows uses for application, shortcut and folder icons. Drop a PNG or JPG, tick the sizes to embed, preview each one, and download in a single click. There's nothing to install and no sign-up — the conversion runs entirely in your browser.

Unlike tools that just rename a .png to .ico, this builds a proper icon: each selected size is rendered onto a square canvas and packed into one file using a client-side ICO encoder, so Windows and browsers can pick the right resolution for every context. Your file never touches a server.

Why a Multi-Resolution ICO Matters

A single .ico can hold many sizes at once. A browser grabs the 16×16 for the tab and 32×32 for bookmarks; Windows uses 48×48 for desktop shortcuts and 256×256 for the Large-icons view. Ship a one-size icon and it ends up blurry or stretched in at least one context. That's why this multi-size ICO generator lets you embed 16, 32, 48, 64, 128 and 256 px together in one file.

Quick presets make it effortless: Favicon (16/32/48), Windows (16/32/48/256) or All sizes. You can always toggle individual sizes and watch the live preview update instantly so you know exactly what you'll get before downloading.

UtiloKit vs Convertio, favicon.io and CloudConvert

Most online ICO converters — Convertio, CloudConvert, ILoveIMG — upload your image to their servers to process it. That means your logo or brand mark travels over the internet, gets stored on third-party infrastructure, and you have to wait for network latency. favicon.io's converter is popular but also server-side, and it generates a fixed set of sizes you can't customize.

UtiloKit converts entirely in your browser using the HTML5 Canvas API. Nothing is uploaded. You choose exactly which sizes to embed. The result is instant, private, and works even without an internet connection once the page loads. If you'd rather not send confidential logos or internal assets to an unknown server, that local-only conversion is the deciding difference.

Batch Convert, Keep Transparency, Export PNGs

Need to convert a whole folder? Drop or paste multiple PNG or JPG files at once — each becomes its own .ico with your chosen sizes, and Download all saves them together. Transparency is fully preserved: every size is PNG-encoded inside the icon, so the alpha channel from your source survives and rounded logos stay cut-out against any background.

You can also export individual PNG sizes — click any tile in the size preview to save just that resolution, handy when you need a 32×32 or 256×256 PNG alongside the .ico for use in web app manifests or Apple touch icons.

PNG to ICO on Windows 11, Mac and iPhone — No Software Needed

Searching for how to convert PNG to ICO on Windows 11 usually turns up suggestions for Paint, GIMP, or sketchy .exe downloads. You don't need any of them: this runs in your browser on any OS — Windows, Mac, Linux, even iPhone and Android. Convert the image, then right-click a shortcut or folder → Properties → Change Icon and point it at your new .ico.

For website use, drop the file at your site root as favicon.ico and add <link rel="icon" href="/favicon.ico"> to your HTML head. Most browsers detect /favicon.ico automatically. Building a complete favicon set? A favicon generator tool can output every PNG size, the .ico, a web manifest, and the HTML snippet in one download.

Private by Design — Your Image Never Leaves Your Browser

Every conversion happens locally with the HTML Canvas API and a client-side ICO encoder — your image is never uploaded, logged, or shared. This is the key advantage over server-based converters like Convertio and CloudConvert: your logos, brand assets, and confidential graphics stay on your device throughout the entire process.

The tool works offline once the page has loaded, has no daily limits, no file-size caps (within browser memory), and produces no watermarks. Completely free, completely private. Bookmark this PNG to ICO converter and reach for it whenever you need a favicon or Windows icon without any friction.

Inside the ICO Format: How the Container Works

An ICO file is not a single image — it is a container format built around an ICONDIR structure. The file begins with a 6-byte directory header identifying it as an ICO, followed by a list of ICONDIRENTRY records, one per embedded image. Each entry stores the width, height, color depth, byte size, and file offset for that image. Windows reads the directory first, then seeks directly to whichever entry matches the size it needs, ignoring the rest.

Historically, every entry stored a BMP/DIB bitmap — a Device-Independent Bitmap stripped of its file header. The format supported 1-bit (monochrome), 4-bit (16-colour), 8-bit (256-colour), 24-bit (true colour), and 32-bit (true colour plus a full 8-bit alpha channel) color depths. Starting with Windows Vista, Microsoft allowed PNG-compressed images inside ICO entries for the 256×256 size and above, slashing file sizes dramatically because PNG compression on a 256×256 icon is far more efficient than storing it as an uncompressed BMP.

When Windows needs to display an icon, it walks the ICONDIRENTRY list and picks the entry whose dimensions are closest to the required display size. If no exact match exists, Windows scales the nearest larger size down — which is why missing a common size like 16×16 results in a noticeably blurry title-bar icon even if 32×32 is present. Having every standard size in the file removes that scaling step entirely and gives the operating system pixel-perfect art at every display context.

Which Sizes Windows Uses — and Why Each One Matters

Windows does not pick icon sizes arbitrarily. The shell maps each display context to a specific logical size: 16×16 appears in title bars, the taskbar thumbnail labels, menus, and the small-icons list view; 32×32 is used in the classic desktop icon view and the Details pane; 48×48 fills the Medium Icons view in File Explorer; 64×64 and 128×128 serve Large and Extra Large Icons view; 256×256 is what the shell renders in the Jump List hover preview, the "Open with" dialog, and Windows Photo Viewer thumbnails. On high-DPI monitors running at 150–200 % scaling, Windows also upsamples from the largest available size, so a 256×256 entry is what keeps the icon crisp on a 4K screen.

A single-size ICO — say, just 32×32 — forces Windows to upscale to 48, 64, 128, and 256 px and downscale to 16 px entirely from that one source. The results look soft and amateurish compared to a multi-resolution ICO that provides every size as purpose-rendered artwork. For serious application or product icons, some teams also include a 512×512 entry (used by macOS if the ICO is imported into ICNS workflows) and even 1024×1024 for ultra-high-DPI contexts, though Windows itself caps its use at 256×256.

The practical takeaway is to always include at least 16, 32, 48, and 256 px in any ICO destined for Windows. If you are producing a favicon only, 16, 32, and 48 are sufficient because browsers never request the larger sizes from an ICO file. The size picker in this converter is pre-organised around these real-world usage patterns, and the live preview lets you check rendering quality at each size before committing to a download.

The Modern Favicon Stack: ICO, SVG, PNG, and Web Manifest

Browsers have moved well beyond the original convention of serving a single favicon.ico from the site root. The current best practice is a layered stack. The ICO file at /favicon.ico remains the universal fallback — it is fetched automatically by Safari on macOS, every version of Internet Explorer, RSS readers, email clients that show sender favicons, and a long tail of specialised browsers that ignore <link> tags. For that reason, the ICO cannot be skipped even in 2024. On top of the ICO sits an SVG favicon declared as <link rel="icon" href="/favicon.svg" type="image/svg+xml">: Chromium and Firefox prefer this over ICO and PNG because an SVG scales to any resolution without pixelation. An SVG favicon can even embed a @media (prefers-color-scheme: dark) rule inside the file to switch between light and dark variants automatically — something no raster format can do.

Apple devices require a separate <link rel="apple-touch-icon" href="/apple-touch-icon.png" sizes="180×180"> PNG for the home-screen icon when a user adds a web page to their iPhone or iPad. Android and desktop PWA installations read icon definitions from a web app manifest (/site.webmanifest), which lists PNG icons at 192×192 and 512×512. The minimal complete favicon setup therefore has four components: the favicon.ico (for legacy and universal fallback), the SVG favicon (for modern browsers), the Apple touch icon PNG, and the manifest PNGs. This PNG to ICO converter handles the ICO component; paired with an SVG export of your logo and a favicon generator for the manifest PNGs, you get a future-proof setup in minutes.

One common misconception is that placing a <link rel="icon"> pointing to a PNG is enough and the ICO can be dropped. In practice this breaks Safari 15 and below on macOS, causes blank favicons in Outlook email notifications, and produces missing icons in aggregators like Feedly. The ICO at the root is still required as insurance — it costs nothing to serve a 5–15 KB file, and its presence closes the gap for every browser and client that does not read <link> tags.

Designing Effective Favicons: Constraints and Principles

A 16×16 favicon gives you exactly 256 pixels of canvas. At that resolution, fine lines vanish, text becomes illegible, and multi-element illustrations collapse into noise. The most effective favicons treat the 16 px grid as a distinct design problem rather than a miniaturised version of the full logo. The core principles are: use a bold, simple silhouette that reads as a single shape; choose a single letter or a geometric mark rather than a wordmark; ensure high contrast between the icon and its background so it remains visible on both light and dark browser chrome; and avoid thin strokes — any line thinner than two pixels at 16×16 will either disappear or alias into a grey smear.

The relationship between a brand's full logo and its favicon is often a deliberate simplification. A company whose logo is "Stripe" in a custom typeface uses a lowercase "S" for the favicon. GitHub's Octocat logo is detailed at large sizes but the favicon reduces it to the iconic cat-octopus silhouette in a circle. The best favicons work as a standalone mark — recognisable even when cropped to a 16 px circle by a mobile browser displaying it on the home screen. When your source PNG is 512×512 or larger, the quality headroom is there; the challenge is making choices about what to remove, not what to keep.

From a UX standpoint, a distinctive favicon has measurable value. Users with many browser tabs open navigate visually — they glance at the tab bar looking for a colour or shape, not reading the page title. A unique, high-contrast favicon reduces the time to locate the correct tab and lowers the chance of closing the wrong one. Brands that use a solid colour square or a generic document icon at 16×16 lose this ambient recognition entirely. Investing a few minutes in a proper multi-size ICO with clean rendering at every size is one of the smallest-effort, highest-return improvements in a front-end project.