Converting PNG to ICO repackages your image inside the icon file format that Windows and web browsers use, and our free tool does it in your browser in a second or two. Drop in a square PNG, choose which sizes to embed, and download a .ico file you can use as a website favicon, a custom folder or shortcut icon, or an application icon. There is nothing to install, no account to create, and because the whole conversion happens on your own device, no file is ever uploaded to a server. That last point is the one that matters most, and we come back to it below.
PNG is one of the best image formats on the web, but it is not an icon file. When a system asks for an icon, a favicon.ico for a website, a custom icon for a Windows shortcut, or an app icon for a build tool, it wants the ICO format specifically, and a PNG will not do. Converting PNG to ICO bridges that gap. Your artwork looks exactly the same; it is simply stored in the container these systems recognize. This page explains what the conversion changes, how transparency carries over, how to pick the sizes to embed, and how to convert a PNG on ToolFiddle without your image ever leaving your device.
What converting PNG to ICO actually does
An ICO file is a small container. Unlike a PNG, which holds a single picture, an ICO can hold several images inside one file, each at a different pixel size and color depth. That design exists because an icon has to look right in a lot of places at once, a tiny 16-pixel browser tab and a large 256-pixel preview, and rather than force one size to stretch, the format lets the file carry a purpose-built version for each.
Converting PNG to ICO takes your single PNG image and writes it into that container, usually at the several sizes you choose, so the result is one .ico file that whatever displays it can read as an icon. The pixels are the same pixels; the picture is not recompressed into something lossy or blurred. What changes is the wrapper. Your PNG becomes an ICO, which is the file type a favicon slot, a Windows shortcut, or an app build step will actually accept.
So the conversion is less about changing the image and more about changing its role. A PNG is a picture. An ICO is an icon. Converting PNG to ICO turns a picture you have into an icon a system can use, and the multi-size container is what makes that icon sharp everywhere it appears.
Why ICO instead of PNG
If PNG is so widely supported, it is fair to ask why you would ever want an ICO. The answer is that certain places accept only the icon format, by long-standing convention.
The website favicon is the classic case. For years, browsers automatically requested a file named favicon.ico from the root of a site, and that .ico is still the most broadly compatible favicon there is. Old browsers, feed readers, and various tools look for it by name. Converting your logo PNG to ICO is exactly how you produce that file.
Windows shortcuts and folders are another. When you want a custom icon on a desktop shortcut, a pinned folder, or a drive, the Properties dialog asks for an .ico file. A PNG will not appear in the picker. Converting the artwork to ICO first gives Windows the file it expects.
Application icons round it out. Many build systems and installers for desktop programs want the program's icon supplied as an .ico, often with several sizes embedded so the app looks right in the taskbar, the title bar, and the large icon view. Developers convert a source PNG to ICO to feed those tools.
In each of these, PNG is a fine place to keep your artwork, but the delivery format has to be ICO. That is the whole reason a PNG to ICO converter exists.
How transparency carries over
One of the best reasons to convert from a PNG specifically, rather than a JPG, is transparency. The ICO format supports 32-bit images with a full alpha channel, which is the same kind of smooth, per-pixel transparency a PNG carries. That means when you convert PNG to ICO, the clear areas of your image stay clear in the icon.
This matters most for favicons and logos. A brand mark on a transparent background needs to sit cleanly on whatever color surrounds it, a light browser tab, a dark tab, a colored folder view. If the transparency were lost, the icon would arrive with a solid rectangle around it that clashes with its surroundings. Because ICO preserves the alpha channel, a transparent PNG becomes a transparent icon, and the mark floats correctly on any background.
The contrast with JPG is the lesson here. JPG has no transparency at all, so an icon made from a JPG carries a solid background whether you want one or not. Starting from a PNG, which keeps its alpha channel through the conversion, is the way to get a clean, background-free icon. If your source happens to be a JPG or another format, converting it to PNG first, or using the broader ICO Converter, lets you decide how the background is handled.
Choosing which sizes to embed
Because an ICO can hold several images, converting PNG to ICO involves a small decision: which sizes to include. The right answer depends on where the icon will be used, and the good news is that including a few common sizes covers almost everything.
- 16x16. The smallest common size, used in browser tabs and next to bookmarks. It is tiny, so simple, bold artwork reads far better here than fine detail.
- 32x32. This covers higher-resolution tabs, the Windows taskbar, and many list views. On a sharp display the system often prefers this over the 16x16, so both should look clean.
- 48x48. Used by Windows in various icon views, and a useful middle size between the tab icon and the large preview.
- 256x256. The large size for high-resolution displays and big icon previews. It is stored efficiently inside the .ico and is what keeps the icon crisp when something shows it large.
For a favicon, embedding 16x16, 32x32, and 48x48 is a solid baseline, and adding 256x256 makes it future-proof on sharp screens. For a Windows or app icon, including the same range up to 256x256 keeps it sharp from the taskbar to the large icon view. The ToolFiddle PNG to ICO converter lets you pick the sizes rather than forcing one, so you can match the file to the job. When in doubt, include several; the extra sizes cost very little and mean the icon is ready wherever it lands.
How to use the ToolFiddle PNG to ICO converter
We built the converter so you can get an .ico without reading a manual, and the flow is quick.
- Add your PNG. Drag a single file onto the page, click to browse your device, or paste from the clipboard. A square PNG at least 256 pixels on each side gives the sharpest result, because it has detail to spare when the tool scales down to the smaller sizes. There is nothing to sign up for and no box to tick first.
- Pick the sizes. Choose which sizes to embed in the .ico, such as 16x16, 32x32, 48x48, and 256x256. If you are not sure, including a few common sizes is the safe choice and keeps the icon sharp across small tabs and large previews alike. The proof sheet shows each size at its true pixel size, and enlarges whichever one you tap, so you can see how the artwork holds up before you download.
- Convert and download. The tool builds the .ico with your chosen sizes and lets you save it right away. Your original PNG is never changed, so you keep it for any later edit. Because none of this touches a server, the icon is ready the instant you ask, with no upload and no queue.
- Use the icon. Drop the favicon.ico into your site root, or point a Windows shortcut, folder, or app build at the .ico through its settings. The same file works across those uses because it is a proper multi-size icon.
Worked example: a favicon .ico from a logo PNG
Say you run a small newsletter and you have a logo saved as a 512x512 PNG on a transparent background. You want the classic favicon.ico so the browser tab shows your mark, and so older readers and tools that look for favicon.ico by name find it.
You open the PNG to ICO converter, drag in the logo, and choose to embed 16x16, 32x32, 48x48, and 256x256. You glance at the small preview: at 32x32 the mark is clear, and at 16x16 it still reads, because the logo is a single bold shape rather than a busy illustration. You convert and download favicon.ico. The transparent background came straight through, so the icon will sit cleanly on a light or dark tab.
You upload favicon.ico to your site root and, to be thorough, add a link tag pointing to it. A hard refresh later, the tab shows your logo. The whole job took a couple of minutes, and because one .ico holds all four sizes, the favicon looks sharp both in a normal tab and on a high-resolution laptop screen.
Worked example: an app icon from a PNG
Now say you are packaging a small desktop utility and the build tool asks for the program's icon as an .ico with several sizes. Your designer handed you a 256x256 PNG of the app mark.
You add the PNG to the converter and embed 16x16, 32x32, 48x48, and 256x256, the range that keeps the app looking right from the taskbar to the large icon view in a file explorer. You convert, download the .ico, and point your build configuration at it. When the app is installed, the taskbar shows the small version, the title bar shows another, and the large icon view shows the crisp 256x256, all from the one file you made. Converting PNG to ICO with the full range of sizes is what makes the app icon look intentional rather than pixelated in one place and fine in another.
Real-world use cases for a PNG to ICO converter
The conversion shows up wherever a system wants an icon file rather than a plain image, and the reason is almost always compatibility with something that expects ICO.
- Making a website favicon. This is the most common. A favicon.ico in the site root is the classic, widely supported favicon, and converting a logo PNG to ICO is the direct way to produce it. Even sites that also use modern PNG and SVG icons keep the .ico as the dependable fallback.
- Setting custom Windows icons. People convert a PNG to ICO to give a desktop shortcut, a folder, or a drive a custom look through the Properties dialog, which accepts only .ico files. It is a small personalization that a PNG cannot do on its own.
- Packaging desktop applications. Developers convert a source PNG to ICO to supply the program icon their build tools and installers require, usually with several sizes embedded so the app looks sharp in every view.
- Preparing icons for older software. Some legacy programs and utilities accept icons only in the ICO format. Converting the artwork to ICO ensures it simply loads where a PNG would be rejected.
- Building browser extension and small project assets. Various project scaffolds and tools expect a favicon.ico or an icon.ico in a specific spot, and converting a PNG is the quick way to satisfy that requirement without opening a heavy image editor.
Tips and common mistakes
A few habits make PNG to ICO conversions come out clean, and a couple of errors are easy to sidestep.
- Start from a square, high-resolution PNG. Icons are square, and a source at least 256 pixels on each side gives the converter detail to work with when it scales down. A small source produces a soft icon at the larger sizes.
- Square the image before converting if it is not already square. A rectangular PNG has to become a square to be an icon, so pad it with transparent edges or crop it first. Letting a rectangle stretch into a square distorts the artwork at every size. The crop image tool handles the trim, and the image resizer gets it to the right dimensions.
- Keep the artwork simple for small sizes. The 16x16 version is the hardest to read. Fine lines, small text, and busy detail turn to mush. A bold, simple mark stays legible in a tab, which is where the icon is smallest and most visible.
- Embed more than one size. The point of ICO is the multi-size container. Including 16x16, 32x32, 48x48, and 256x256 means the icon looks right in a small tab and a large preview alike, rather than being stretched from a single size.
- Start from a PNG, not a JPG, when you want transparency. PNG keeps its alpha channel through the conversion, so a clear background stays clear. A JPG has no transparency and brings a solid rectangle with it.
- Keep your original PNG. The .ico is the delivery file, but the PNG is your editable source. Hold on to it so you can regenerate the icon or make a change later.
A closer look at the ICO format
Understanding the ICO format a little makes the conversion make sense. ICO is the icon file format that originated with Windows, and its defining feature is that it is a container. Inside one .ico file sit a small directory and then a series of images, each with its own size and color depth. A single file can therefore carry a 16x16, a 32x32, a 48x48, and a 256x256 image all at once, and whatever displays the icon reads the directory and picks the size it wants.
Early icons used a limited palette and a separate mask to describe which pixels were transparent. Modern ICO files use 32-bit color with a full 8-bit alpha channel, which gives the same smooth, per-pixel transparency you get from a PNG. That is why converting a transparent PNG to ICO keeps the transparency intact. Interestingly, larger images inside an .ico, the 256x256 in particular, are commonly stored using PNG compression within the container, so the format literally embeds a PNG for its big size while keeping the classic icon structure for the small ones. That is exactly what the Compatible setting in the tool does, and the Smallest file setting stores every size as PNG instead, which modern Windows and every current browser read happily.
The favicon is the reason most people outside Windows ever meet the format. When the web was young, browsers were told to fetch favicon.ico from a site's root, and the icon container was a natural fit because it could hold the small tab size and a slightly larger bookmark size together. That convention stuck, which is why an .ico is still the most compatible favicon you can ship, and why converting a PNG to ICO remains a routine step in setting up a site. If your needs go beyond a single favicon.ico to the full modern set of PNG icons and HTML tags, that is a job for the favicon generator, but the .ico at the center of it starts life as a PNG to ICO conversion like this one.
Your image never leaves your device
Here is the part that sets this PNG to ICO converter apart from most of the field, and it is worth dwelling on because file converters are exactly where privacy tends to go wrong. Most online converters work by uploading your file to a server, converting it there, and sending it back. That means a copy of your image, whatever it is, travels across the internet and sits, at least for a while, on a machine you do not control.
Our converter does not work that way. The PNG to ICO conversion runs directly in your browser, on your own device, using your own hardware. When you add a PNG, the tool reads it locally and writes the .ico locally. There is no upload, no copy left on a server, and no record of what you converted. You can switch off your internet connection after the page has loaded and the tool keeps working exactly the same, which is the plainest proof that your files are staying with you.
This is not a theoretical concern. In 2025 the FBI's Denver field office warned the public that a wave of free online file-tool and converter sites were quietly harvesting the files people uploaded, and in some cases planting malware on their computers, all while appearing to work normally. A file converter is a natural target for that kind of abuse, because people feed it logos, brand assets, and images that can hold private information. The surest defense is for the file never to reach the converter's servers in the first place. On-device processing gives you that by design: your image is not exposed in transit, not stored where a breach could leak it, and not fed into anything you did not agree to, because it never leaves your hands.
Genuinely free, with nothing held back
The second thing that separates this PNG to ICO converter from much of the field is that it is free in the ordinary meaning of the word. A lot of converter sites are really a funnel toward a subscription. The conversion works, and then a watermark lands on the output, or a message says you have used your free conversions for the day, or the multi-size icon and higher resolution sit behind a paid plan.
None of that happens here. There is no sign-up and no account, and we do not ask for your email. We do not stamp a watermark on your icon or quietly limit which sizes you can embed to nudge you toward a paid tier, because there is no paid tier. There is no daily counter and no cap on how many files you can convert. You can convert one logo today and a batch of project icons tomorrow, and never hit a wall. Rival converters routinely limit free users, reserve multi-size output for subscribers, or lock the large 256x256 size behind a monthly charge. We built the opposite, on the view that a basic everyday conversion like this should simply work for everyone.
Instant and unlimited by design
The third advantage falls straight out of running on your device. Because your file is never uploaded or downloaded, there is nothing to wait for. You do not watch a progress bar creep while a PNG is sent over a slow connection, and you never sit in a queue behind other people at a busy moment. The conversion happens the instant you add the file, about as fast as your device can read it.
The same design removes the artificial size ceilings that server tools impose to control their costs. There is no small maximum file here to bump into, and no limit on how many icons you can build in a day. Because the page is not loaded down with the heavy advertising and tracking scripts that clog so many free converters, it opens quickly and stays responsive. The whole thing is meant to feel like a utility you own, not a service you are borrowing for a moment.
Works on any device, even offline
The converter runs on a phone, a tablet, or a computer, in any current browser, and the layout adapts to whatever screen it finds. On a Windows PC you can convert PNG to ICO and immediately set the result as a custom folder or shortcut icon, and the steps are the same on Windows 11, Windows 10, or a Mac. On a phone the usual annoyance of uploading an image over a cellular connection simply does not apply, because the work is done on the device itself. Once the page has loaded you do not need a live connection to convert, so a patchy signal will not stop you, and nothing depends on a particular brand of browser.
Related tools on ToolFiddle
Converting a PNG to an icon is often one step in a short workflow, and the neighboring tools finish the job. If you need the complete website icon package, every favicon size for browsers and phones plus the HTML tags to paste in, the Favicon Generator builds all of it from one source, while this tool focuses on the single .ico. If your source is a JPG or another format, or you want to turn an existing .ico back into a PNG, the ICO Converter handles conversion in both directions across several formats. And when your PNG needs to be squared off or scaled before it becomes an icon, the Crop Image tool and the Resize Image tool get it to the right shape and size first. Every one of these runs in your browser the same way this converter does, so your files stay with you across the whole workflow.
The short version
Converting PNG to ICO repackages your image into the icon file format that websites and Windows expect, without changing how the picture looks. It is the direct way to make a favicon.ico, a custom shortcut or folder icon, or an application icon from artwork you already have as a PNG. The ICO container can hold several sizes at once, so embedding 16x16, 32x32, 48x48, and 256x256 keeps the icon sharp from a tiny tab to a large preview, and because ICO supports a full alpha channel, a transparent PNG stays transparent. Start from a clean, square, high-resolution PNG, pick your sizes, and do all of it here, where your image never touches a server, there is no sign-up, watermark, or limit, and the .ico is ready the moment you ask.