An ICO is the Windows icon format, a small container built to show a program or shortcut at whatever size the desktop needs. A JPG is the universal photo format that opens in every app, browser, and document editor. Converting ICO to JPG pulls the icon image out of that Windows-specific container and saves it as a plain picture you can drop into a slide, an email, or a web page.
Two things about ICO make this conversion different from an ordinary image swap, and knowing them before you start saves you a blocky or unexpectedly white result. This guide covers both, explains what happens inside the conversion and why the result can look rough, then walks through it.
From icon container to flat photo
Where a JPG stores one flat picture, an ICO is really a small bundle of pictures at different resolutions, plus, usually, a transparent background so the icon sits cleanly on any desktop color. JPG supports neither of those features. So the conversion picks one image out of the bundle and flattens away the transparency, giving you a single ordinary photo-style file.
ICO is a multi-size, transparent icon container. JPG is one flat, opaque image. Converting means choosing a size and losing the transparency.
A container of icons versus a photo codec
These two formats were designed for jobs that could hardly be more different. ICO is Microsoft's icon container. As MDN describes, a single .ico file can hold several images at once, each a different size and color depth, so the operating system can pick the right one for a taskbar, a title bar, or a large desktop tile.[1] The same format is what browsers historically requested as a site's favicon through the link element's icon relation, which is why tiny .ico files are scattered across the web.[2] Its whole reason for existing is to serve one crisp icon at many sizes, with transparency so it floats on any background.
JPG is the opposite kind of thing: a single-image, lossy photographic codec standardized as ISO/IEC 10918 by the Joint Photographic Experts Group.[3] The files you exchange are usually wrapped in the JPEG File Interchange Format that the Library of Congress catalogs as JFIF.[4] JPEG stores exactly one flat, opaque image, and its compression was tuned for the smooth gradients of photographs, not the hard edges and flat color of an icon. Converting from one to the other means collapsing a multi-size, transparent icon set into a single opaque photograph, which is why the two ICO quirks below matter so much.
Inside an ICO file: directory and images
The ICO format is unusually simple to describe, and understanding its layout explains why the "pick the largest size" advice exists at all. An ICO file begins with a short header that says how many images the file contains. Immediately after it comes the icon directory: a table with one entry per image, and each entry records that image's width, height, color depth, and where in the file its pixel data begins. Only after this directory do the actual image payloads follow, one after another.
The consequence is that a single .ico is genuinely a bundle. A well-made application icon might carry a 16 by 16 version for the taskbar, a 32 by 32 for the title bar, a 48 by 48 for medium views, and a 256 by 256 for large desktop tiles, all in the same file, so Windows can pick whichever fits without ever scaling.[1] Each embedded image is stored in one of two ways: older icons use a bitmap plus a separate one-bit or eight-bit transparency mask, while modern icons, especially at large sizes, embed a full PNG for better compression and clean alpha. A converter has to read the directory, decide which of these embedded images to take, and decode that one, which is why the size you end up with is a choice rather than a given.
How the conversion works under the hood
A converter handles ICO to JPG in three moves. First it parses the ICO directory, the small table at the start of the file that lists every image the icon contains along with its dimensions and color depth, and selects one entry, ideally the largest, to convert. Second it decodes that entry into raw pixels; each image inside an ICO is stored either as a PNG or as a bitmap with a separate transparency mask, and decoding produces a full grid of colored pixels plus, usually, an alpha channel.
Third, because JPEG cannot store transparency, it composites the image onto a solid background, replacing every transparent pixel with a chosen fill color, and then encodes the flattened result with JPEG's lossy compression. That compression breaks the image into blocks, transforms each into frequency components, and quantizes them, discarding the high-frequency detail that costs the most bytes. For a photograph this is nearly invisible, but for an icon's crisp lines it is exactly the wrong kind of loss, which is the root of the quality issue covered further down.
What JPEG compression does to an icon
JPEG's compression is the reason an icon and a JPG are a slightly uneasy match, so it is worth seeing what the codec actually does. JPEG works by splitting the image into eight-by-eight pixel blocks and running each block through a discrete cosine transform, which re-expresses the block as a sum of frequency patterns: smooth, gradual changes are low-frequency, and sharp edges are high-frequency.[3] The codec then quantizes those frequencies, storing the low-frequency information precisely and the high-frequency information coarsely, because human vision is far more sensitive to broad tone than to fine detail. For a photograph, where almost everything is low-frequency gradient, this throws away almost nothing you can see.
An icon is the opposite kind of image. Its defining features, black outlines, flat blocks of color, and crisp edges, are exactly the high-frequency content JPEG treats as expendable. When the codec coarsens those frequencies, it introduces two characteristic artifacts: ringing, faint ripples that echo out from a hard edge, and mosquito noise, a shimmer of stray pixels around high-contrast lines. On a photo these are invisible; on a sharp logo they are the first thing you notice. This mismatch is not a flaw in any particular converter, it is fundamental to asking a photographic codec to store graphics, and it is why the quality section below recommends the highest source size and, where crispness matters, PNG instead.
Two quirks of ICO files
| Quirk | What it means | What to do |
|---|---|---|
| Multiple sizes inside | One .ico often holds 16, 32, 48, and 256 pixel versions | Pick the largest so the JPG is not blocky |
| No transparency in JPG | The transparent background gets filled, usually with white | If you need the transparent edge, use PNG instead |
If your icon looks blocky after converting, you almost certainly grabbed a small embedded size. Redo it and select the largest resolution in the file, often 256 by 256.
Convert ICO to JPG, step by step
Open the converter and add your ICO
Open the FileFormer image converter and drop your .ico in. It runs on your device, so the file is never uploaded.
Choose JPG and the largest size
Set the output to JPG and select the biggest resolution the icon contains. That gives the sharpest possible result from an inherently small source.
Convert
The chosen icon image is flattened to JPG. Any transparent area is filled with a solid background color rather than left see-through.
Download and check the edges
Save the JPG and look at the corners. If a white box appears where the icon used to float, that is the missing transparency, and PNG is the fix.
Why an icon can look rough as a JPG
Even when you pick the largest embedded size, an icon can come out of JPG conversion looking slightly worse than expected, and the reason is baked into how JPEG works. Its lossy compression was designed for photographs, where color changes gradually and a little smoothing goes unnoticed. Icons are the opposite: sharp black outlines, flat blocks of color, and hard edges. JPEG's block-based transform tends to sprinkle faint halos and speckles around those high-contrast edges, an artifact often called ringing or mosquito noise, so a crisp logo can pick up a subtle fuzz that was never in the original.
The transparency fill adds a second issue. Because the see-through background becomes a solid color, an icon that was drawn to float now sits in a visible rectangle. If the fill color clashes with wherever you place the image, the icon looks boxed in. Both problems have the same root cause: JPEG is a photo format being asked to do a graphics job. Choosing the largest source size and a fill color that matches the destination background is the best you can do within JPG's limits.
If the icon will sit on a white page, set the transparency fill to white so the rectangle disappears against the background. Matching the fill to the destination is the simplest way to hide the lost transparency.
Real-world scenarios and the right target
Whether JPG is genuinely the right destination depends on where the image is going. A few common cases:
| What you are doing | Best target | Why |
|---|---|---|
| Placing an icon on a white document page | JPG, white fill | Compact and universal; the fill blends into the page |
| Putting a logo on a colored slide or website | PNG | Keeps transparency so it floats on any background |
| Keeping the crispest possible edges | PNG | Lossless, so no ringing around hard lines |
| Emailing a quick, small copy of an icon | JPG | Smallest file when transparency does not matter |
| Extracting a favicon for reuse in graphics | PNG | Preserves alpha and sharpness for later editing |
The pattern is consistent: JPG suits an icon that will live on a plain, matching background, and PNG suits everything where transparency or edge crispness matters.
When PNG is the better target
JPG is the right choice when you want a compact, universally openable image and a solid background is fine, for example an icon placed on a white document page. But icons are often designed to sit on any color, and JPG cannot preserve that. If you need to keep the transparent background, convert the icon to PNG instead, which supports an alpha channel and also handles sharp icon edges better than JPG's photo-oriented compression.
In short, reach for JPG when the icon will live on a plain background and file size matters, and reach for PNG when transparency or crisp edges are the priority.
JPG versus PNG and WebP for icons
JPG is rarely the ideal destination for an icon, so it is worth weighing the two formats that usually serve it better. PNG is the natural home for anything that started as an icon: it is lossless, so the hard edges stay perfectly crisp with no ringing, and it supports a full alpha channel, so the transparent background survives intact. The only thing you give up is a little size, and for a small icon that difference is trivial. For the vast majority of ICO conversions, PNG is simply the correct answer, and JPG earns its place only when a solid background is acceptable and you specifically want the smallest possible file.
WebP is the modern third option and, in a sense, the best of both: it offers a lossless mode that keeps edges razor sharp like PNG, a lossy mode that beats JPG on size, and full transparency in either. Where it is supported, a lossless WebP can hold an icon at smaller size than PNG while preserving the alpha channel. Its one weakness is reach: a handful of older tools and document editors still do not read WebP, whereas JPG and PNG are understood literally everywhere. The practical decision tree is short: choose PNG when you want guaranteed compatibility with crisp, transparent output, choose WebP when your destination supports it and size matters, and choose JPG only when the icon will sit on a plain matching background and universal openability outweighs the loss of transparency and edge sharpness.
Turn your icon into a JPG now
Pick the largest size and export a standard image in your browser, with nothing uploaded.
Key takeaways
- An ICO holds several sizes; pick the largest so the JPG is not blocky.
- JPG has no transparency, so the icon's transparent background is filled, usually with white.
- Use JPG for a plain background and small size; use PNG to keep transparency and crisp edges.
- The result is one flat photo-style image, ready for documents and the web.