PNG to ICO Converter Online Free

Every website needs a favicon — the small icon in the browser tab — and every Windows program needs an icon. Both still speak ICO, a format that packs several sizes of the same picture into a single file so each program can pick the size it needs. Most icons start life as a PNG: logos are designed on transparent backgrounds, and PNG is the lossless format that carries that transparency. A PNG to ICO converter takes that finished artwork, crops it to a square, shrinks it to proper icon sizes, and stores each size as a PNG inside one genuine .ico file. The converter at the top of this page does exactly that in your browser: tick the sizes you want (16, 32 and 48 are ticked by default), and it builds the file byte by byte — a 6-byte header, a 16-byte directory entry per size, then the PNG image data for each size in turn. Nothing is uploaded to a server, and the transparency in your PNG is kept in every size.

The proof file for this tool was chosen to make the checking easy. When the converter was built, its packing code was tested outside the browser on a square test PNG of 512 × 512 pixels and 7,598 bytes, drawn as four bold colour quadrants — red, green, blue and yellow — so that any resizing error would be obvious. With the three default sizes ticked, the packer produced PNG entries of 318 bytes (16 × 16), 352 bytes (32 × 32) and 411 bytes (48 × 48). Add the container — 6 bytes of header plus 3 × 16 = 48 bytes of directory — and the finished icon is 1,135 bytes. Independent software then parsed the file back: the header read reserved 0, type 1, count 3, and each PNG extracted from its directory offset decoded at exactly the size its entry promised. One honest note about byte counts: these figures come from the build test, and your browser's own PNG encoder may land a few bytes either side of them for the same picture — encoders differ slightly in how they compress. The sizes inside the icon, which are what Windows and browsers actually read, are exact.

What an ICO File Actually Is

The ICO format is nearly as old as Windows itself — it arrived with the first Windows icons in the mid-1980s — and it became a web format in 1999, when Internet Explorer 5 began looking for a file named favicon.ico on every website and showing it beside bookmarks. Its structure reflects its job as a container rather than a picture format. An ICO file opens with a 6-byte header called ICONDIR: two bytes that must be zero, two bytes holding the type (1 for icons; 2 would mean a cursor), and two bytes counting how many images the file holds. Immediately after comes one 16-byte directory entry per image, recording that image's width and height (a byte each, where the value 0 means 256, since 256 does not fit in a byte), its colour count and a reserved byte, the colour planes and bits per pixel, the exact size of the image data, and the offset in the file where that data begins. Only after the directory does the picture data start.

What sits at each offset has changed once in the format's life. Early ICO files stored each image as a BMP-style bitmap with a mask. Since Windows Vista, an entry may instead hold a complete PNG file, compressed and self-contained — and that modern form is what this tool writes, with 32 bits per pixel recorded in the directory (red, green, blue and a transparency channel). PNG entries are smaller, support real transparency, and are understood by every current version of Windows and every browser that accepts ICO at all. Starting from a PNG source makes this form especially natural: the icon entries are PNGs, so a PNG original flows into them without ever passing through a lossy format. The multi-size design is the format's real point — a browser tab wants 16 × 16, a desktop shortcut wants 48 × 48, a high-density display wants a larger image still — and rather than forcing one compromise image on all of them, the ICO carries several and lets each reader choose.

Why Start from PNG Rather Than JPG

If you have ever wondered why there are two converters for this job, the answer is in what the two source formats keep and throw away. JPG is a photograph format: it compresses by discarding fine detail, and around the hard edges of a logo — exactly what an icon is made of — that discarding shows up as faint smudges and colour fringes when the picture is shrunk. JPG also has no transparency at all, so a logo drawn on a clear background arrives already baked onto white. PNG is the opposite trade: lossless, so every pixel is the pixel the designer chose, and a full transparency channel, so the clear surround of a logo stays clear through the conversion and into the icon, where it will be displayed against tabs, taskbars and desktops of every colour. If your artwork exists as a PNG, converting from the PNG is strictly the better route. If all you have is a photo, the JPG to ICO converter on this site does the same packing job from that starting point — the container does not care, but your edges will.

How to Use the Converter

Using the tool takes a few seconds. Follow these steps:

1. Click the file box and choose a PNG image from your device, up to 20 MB.
2. Tick the icon sizes to include — 16, 32 and 48 are ticked by default; add 128 and 256 if the icon will be shown large.
3. Press "Convert to ICO".
4. Read the result lines: they show the input file's name, size and dimensions, the square the image was cropped to, and the output ICO's exact size with the list of sizes inside it.
5. Click the download button to save the .ico file, then rename it to favicon.ico if it is headed for a website root.

The whole conversion happens on your device. If the file is not a PNG, is over the 20 MB limit, cannot be decoded, or has no size ticked, the tool says so plainly instead of failing silently. One warning belongs here rather than in the fine print: because icons are square, the tool crops a rectangle to its centre square. A subject near the edge of a wide image will be trimmed — the result line states the crop square, and if your subject sits off-centre, crop the PNG yourself first and convert the crop.

Worked Examples

Example 1: The build proof — a 512 × 512 test PNG at the default sizes

The build test began with a square PNG, 512 × 512 pixels, 7,598 bytes: four flat colour quadrants, chosen so that the resized entries could be checked by eye as well as by software. A square source needs no crop, so all 512 pixels of width fed the resize. The three default sizes came out at 318 bytes for 16 × 16, 352 bytes for 32 × 32 and 411 bytes for 48 × 48 — small, because flat colour compresses extremely well and icons are tiny pictures. The container added 54 bytes (6 of header, 48 of directory), giving the finished file of 1,135 bytes. Parsing that file back confirmed the structure end to end: header fields reserved 0, type 1, count 3; directory entries pointing at offsets 54, 372 and 724; and the PNG at each offset decoding at exactly 16, 32 and 48 pixels square. That round trip — build, parse, decode, measure — is what "a real ICO file" means, and it is the difference between a converter and a renaming trick.

Example 2: A portrait PNG — the crop arithmetic

The crop is pure arithmetic, and a portrait image shows how it bites. Take a PNG of 400 × 900 pixels — a phone-shaped export. Its centre square is 400 × 400, taken by trimming 250 rows from the top and 250 from the bottom; the full width survives and just under 56 percent of the height goes. Nothing is squashed: every pixel in the icon comes from that honest middle square, shrunk. The lesson generalises — for any rectangle, the square is the shorter side, centred — and it explains why experienced designers export a square version of a logo for icon work rather than letting any converter choose the middle of a tall or wide original. If the top and bottom of the tall image matter, make that square yourself first, then convert.

Example 3: Every size ticked — where the weight sits

Ticking all seven sizes changes the container maths and the balance of the file. The directory grows to 6 + 7 × 16 = 118 bytes, and each added size contributes its own PNG. The small entries stay light, but weight concentrates at the top: a 256 × 256 entry of a detailed image can outweigh all the smaller sizes combined, because PNG size grows with pixel count and detail — a 256 entry holds 64 times the pixels of a 32 entry. Include 256 if the icon will appear large, on a high-density display or a big desktop tile, and leave it out if the icon only ever lives in browser tabs, where it is pure extra weight downloaded by every visitor on every page.

Example 4: The smallest useful favicon — one size only

At the other extreme, ticking only 16 × 16 gives a container of 22 bytes (6 header + 16 directory) plus one small PNG. For a simple blog or an internal tool that is genuinely enough — browsers scale a lone 16 × 16 up where they must, accepting some softness. The example is a useful scale marker at the bottom end: the overhead of the ICO format is 6 + 16 × (number of sizes) bytes, a figure you can compute before converting anything, and at favicon sizes the artwork itself can be smaller than the directory that describes it.

How to Read the Output

The result lines tell you four things worth checking. The input line names the file you chose, its size on your device and its dimensions — confirm it is the image you meant, because converting the wrong draft of a logo is the commonest silent error. The crop figure gives the centre square the icon was made from, so you can see exactly how much of the sides (or top and bottom) was trimmed. The output line gives the ICO's exact size in bytes and lists the sizes inside it; compare the list against the boxes you ticked, and expect the total to equal 6 + 16 × (number of sizes) plus the sizes of the individual PNGs — a mismatch means something other than this converter produced the file. Finally, the download button repeats the output size in its label, so the saved file can be checked against the report byte for byte. If your PNG had transparency, it is still there: the 32-bit PNG entries carry an alpha channel precisely so a logo's clear surround stays clear against any background the icon lands on.

Where ICO Files Are Used

The favicon is the use everyone meets: browsers request /favicon.ico from a site's root by default, show it in tabs, bookmarks, history and shortcuts, and still treat the ICO as the baseline format even where PNG and SVG icons are also offered — a site without one shows a generic globe and logs a 404 in the server records. Windows is the second home: program shortcuts, taskbar buttons, desktop icons and file-type icons are ICO files, and the multi-size container exists because Windows shows the same program at 16 pixels in a list and 256 pixels on a large-icon desktop view. Installers and portable apps embed ICO for the same reason. Beyond those, ICO turns up anywhere a small branded picture must travel as one self-contained file: pinned web apps, browser extensions, kiosk software and embedded devices with icon-driven interfaces. Nobody chooses ICO for photographs or for sharing images — it is a working format for one specific job, carrying the right size of a small picture to whatever asks for it.

Common Mistakes

The first common mistake is renaming: changing "logo.png" to "favicon.ico" in a file manager does not convert anything — the bytes inside are still a single PNG with no header and no directory, and browsers and Windows will reject the file or ignore it. A real conversion re-encodes into the container, which is what this tool does. The second mistake is converting from a JPG copy when a PNG original exists: the JPG's edge smudges and baked-white background are inherited by every size in the icon, when the PNG would have kept both clean. The third is feeding the converter detailed artwork and expecting it to survive at 16 × 16: fine detail, text and faces dissolve at icon sizes, which is why real favicons are bold, simple shapes — test your design by looking at the 16-pixel size, not the 256. The fourth is ignoring the crop — converting a tall export and finding its top and bottom missing, when the centre square was stated on the page. The fifth is ticking every size by reflex: the 256 entry can be most of the file, and a favicon is downloaded by every visitor. The sixth is expecting enlargement to add detail: if the cropped square is smaller than a ticked size — a 100 × 100 source asked for a 256 entry — that entry is an enlargement, smoother but not sharper, because conversion resamples the pixels that exist and cannot invent new ones.

Limits: What This Tool Does and Does Not Do

The limits are simple and all stated on the tool itself. The source must be a PNG and no larger than 20 MB; anything else is refused with a plain message. The crop is always the centre square, never chosen interactively — if the subject is off-centre, prepare the square before converting. The icon entries are PNG images at the sizes you tick, up to 256 × 256; the tool does not produce the older BMP-with-mask entries, because every current reader accepts PNG entries and they are smaller and transparent. It also does not retouch, recolour, or simplify your artwork: icons at 16 × 16 are made by shrinking, and a design that looks busy at 16 pixels needs a simpler version, not a better converter. Finally, the tool produces the file; it does not install it anywhere. Putting it on a website or into a program is a separate step that you do in your own files.

Privacy: Your Image Stays in Your Browser

Your PNG is never uploaded. The conversion — reading the file, cropping, resizing, packing the container — all runs on your own device in the page, and the download is built there too. That matters for favicons precisely because favicons are logos, and logos are unreleased brand assets: sending one to a server means trusting a third party with artwork that may not be public yet. With this tool there is nothing to trust. The page can also be used offline once loaded, and nothing in the result depends on any account, sign-in or subscription. The only record of the conversion is the ICO file you choose to download.

Frequently Asked Questions

Is the downloaded file a real ICO file?

Yes. It is a 6-byte header, one 16-byte directory entry per size, and the PNG image data at the offsets those entries promise, built byte by byte on your device. It is not a PNG with an .ico name. Windows, browsers and icon tools that read the format parse it correctly, because it follows the same structure the format has used since the 1980s — only the entries are the modern PNG kind.

Why start from PNG rather than JPG?

PNG is lossless and carries transparency; JPG is lossy and does not. A logo converted from its PNG keeps sharp edges and a clear surround in every size of the icon. A logo converted from a JPG inherits edge smudges and a white background baked in. If the PNG exists, use it; if only a JPG exists, the JPG to ICO converter on this site does the same packing job from that starting point.

Why include several sizes in one file?

Because each reader wants a different one. A browser tab shows 16 × 16; a taskbar button or desktop shortcut wants 48 × 48; a high-density display or large-icon view wants 256 × 256. Shipping one file with the sizes inside means the icon is sharp everywhere instead of a single image stretched or shrunk to every purpose. The default 16, 32 and 48 covers the common cases; add 128 and 256 when the icon will be displayed large.

Why is my icon cropped?

Icons are square, so a rectangular PNG is centre-cropped to its shorter side before resizing — the result line states the square used. If the subject of a tall or wide image sits off-centre, the crop will trim it; in that case, crop the PNG to the square you want yourself first and convert the crop.

Does transparency survive?

Yes. Each size inside the ICO is stored as a PNG at 32 bits per pixel — red, green, blue and an alpha channel — so the clear surround of a logo stays clear in the icon, against tabs, taskbars and desktops of any colour.

Is my image uploaded anywhere?

No. Everything happens on your device in the page — reading, cropping, resizing and packing — and the only output is the ICO file you download. Nothing is sent to a server, and no account or sign-in is involved.

Related Tools on Your Smart Kit

If you have an icon problem in the other direction, or a different source image, the neighbouring tools cover it. The JPG to ICO Converter does the same genuine ICO packing starting from a JPG, for when the PNG original is not available. The PNG to PSD Converter turns a PNG into a real Photoshop file for editing rather than for use as an icon, and the PNG to PDF Converter places a PNG on a page for printing and sharing. The Image Resizer produces a PNG at an exact pixel size when you need a plain image rather than an icon container, and the JPG to PNG Converter recovers a lossless PNG from a photograph when that is the best available starting point for icon work.