Convert ICO to JPG

Almost nobody chooses JPEG for an icon on the merits. The people who arrive here have hit an upload field that lists .jpg and .jpeg and nothing else — a marketplace listing, an internal HR directory, a print service’s web form, a content system somebody configured in 2011 and nobody has touched since. The picture is fine; the gatekeeper is the problem.

That framing matters because it changes the advice. There is no version of this conversion that makes the image better, so the whole job is to lose as little as possible on the way through and to get the background right first time.

JPEG has no transparency. Not a limited version of it, not one bit of it — the format has three channels and no fourth. So every transparent pixel in the icon has to become an opaque one before the encoder sees it, and something has to decide what colour. The background setting is that decision, and it defaults to white.

Get it wrong and the failure is obvious after the upload rather than before it: a white square around a logo on a dark listing page, or a black square on a light one. Set it to the colour the image will sit on. If you do not know, white is the safer guess, because most upload destinations are still white pages.

An ICO is a container. It holds the same mark drawn at several sizes so that Windows and browsers can pick the right one, and a JPEG holds a single picture, so the conversion has to choose. It chooses the largest, because that is what your browser’s icon decoder hands back — verified by building a file with 16, 32, 48 and 256 pixel entries in four different colours and converting it: the result was 256 pixels, in the colour of the 256 entry.

The smaller drawings are not merged, scaled or written anywhere. If the small size was the one you needed, an icon editor such as GIMP will open the file and show every entry as its own layer.

This surprises people, because JPEG is the format everyone associates with making files smaller. That reputation is earned on photographs. An icon is flat colour with hard boundaries, which is exactly the content JPEG is worst at and PNG is best at, so the arithmetic runs the other way.

Measured on a test icon of 8,471 bytes holding four entries: the JPG came out at 4,005 bytes and the PNG at 1,737. The JPEG is more than twice the size of the PNG and it is also the lossy one. If your reason for converting was to save bytes rather than to satisfy a form, the conversion is working against you.

JPEG divides the image into eight-by-eight blocks and stores each as a set of frequencies. A photograph is mostly gentle gradients, which that representation suits. A sharp black line against flat white is the opposite: reconstructing it needs high frequencies the encoder has thrown away, so a faint ripple appears alongside every crisp edge. It is called ringing, and it looks like a smudge or a halo.

On a 256-pixel icon those blocks are large relative to the artwork — thirty-two of them across the whole width — so the artefacts sit right on the detail somebody drew carefully. Raising the quality reduces the effect and never removes it; the format does not have a setting that turns the transform off.

The default of 82 is chosen for photographs and is low for this content. On flat artwork the artefacts are visible rather than merely measurable, and the file is small enough in absolute terms that spending bytes on quality costs almost nothing — going from 82 to 95 on a 256-pixel icon moves a four-kilobyte file to perhaps eight.

Set it high. There is no meaningful upload budget being defended at this scale, and the difference between a clean outline and a fuzzy one is the difference between a logo that looks deliberate and one that looks scanned from a fax.

Icons are square by convention and by specification, so this is rarely a problem going out of an ICO — but many upload fields have a fixed aspect ratio and will letterbox or crop whatever you give them. A 256-pixel square dropped into a 1200 by 630 banner slot gets stretched or padded by somebody else’s code, with results you do not see until it is live.

If the destination has a stated size, prepare the image to it rather than letting the site do it. The background colour you set here becomes the padding, which is the one part of that process you can control from this page.

A surprising number of upload fields that display "JPG" in their help text accept a PNG without complaint, because the validation is on the MIME type reported by the browser and the list is longer than the message. It costs one attempt to find out, and a PNG from the same icon will be sharper, smaller and free of the background problem.

Where the restriction is real — some print services genuinely require JPEG because their pipeline flattens everything anyway — the conversion here is the right answer and the compromises above are the price. Say so to whoever asked, so that the fuzziness is understood as a format limit and not as a fault in the artwork.

Drop the whole folder. Every icon is decoded, filled and encoded independently and the results arrive as a ZIP, with the same background colour and quality across the set — which is what a catalogue or a listing page needs, since inconsistency between entries is more noticeable than any single file being slightly wrong.

Watch the pixel dimensions in the result rather than assuming they match. Icon sets collected over years are rarely uniform: some files carry a 256-pixel entry and some stop at 32, and the JPGs will differ accordingly with no warning from the converter.