Secure server conversion
JPG to ICO Converter
Convert a JPG into a Windows ICO icon containing 16, 32, 48 and 256 pixel versions. It works — but a JPEG is usually the wrong starting point for an icon, for two specific reasons worth knowing before you use the result.
Drag and drop your JPG images here
Add several at once. Each file is processed and then deleted from our server.
Up to 20 MB per file Batch ready
Conversion queue
→
Your browser could not read this file, so it was converted on our server and deleted there straight away.
Your file had frames or pages. Only the first is in this download.
Step by step
How to convert JPG to ICO in 3 steps
-
Add your JPG
Square works best; anything else is padded rather than squashed.
-
Nothing to configure
All four standard sizes are written into one file.
-
Download your .ico
Format comparison
JPG vs ICO
JPG / JPEG (Joint Photographic Experts Group)
LossyShrinks photographs to a fraction of their size by discarding fine detail the eye is least likely to notice.
- Small files for photographs
- Opens on virtually every device, browser and app
- Blurs text and sharp edges, and re-saving loses a little more each time
ICO (Windows Icon)
Multi-size iconBundles several sizes of the same small image in one file, for Windows icons and website favicons.
- Several icon sizes in a single file
- Understood by every browser as a favicon
- Only for small images — each entry is at most 256 × 256 pixels
The two problems with a JPEG source
1. JPEG has no transparency. None — the format has no alpha channel at all. So whatever background your image has becomes part of the icon permanently. A logo on white gives you a white square, which looks fine on a light browser tab and like an obvious rectangle on a dark one.
This is the single most common complaint about home-made favicons, and it cannot be fixed at conversion time: the transparency has to exist in the source. PNG to ICO preserves it properly.
2. Photographs do not work at 16 pixels. A 16×16 icon is about the size of this letter "M". A photograph reduced to that is a smudge of average colours — recognisable to nobody, including you.
Icons that work small are simple: one shape, two or three colours, heavy contrast. That is why every recognisable favicon is a letter, a symbol or a silhouette, never a scene.
What this tool does anyway
Four sizes go into one file — 16, 32, 48 and 256 pixels — which is the whole point of ICO as a format. A browser tab takes the 16, a desktop shortcut takes the 48, and a large tile takes the 256, each getting a version rendered specifically for it rather than scaling a mismatched one.
Sizes larger than your source are skipped rather than invented. A 32-pixel source will not be blown up into a blurry 256-pixel entry that Windows would then prefer over the crisp small one.
Non-square images are padded, not squashed
If your JPG is not square — a wide logo, say — it is centred on a square canvas rather than stretched to fit. Stretching would distort it; padding keeps the proportions.
Because JPEG has no transparency to inherit, that padding is filled rather than clear, which is another reason a PNG source gives a better result: there the padding is genuinely transparent and the icon keeps its shape against any background.
Quality
Quality and file size
There is no quality setting. Each size inside the icon is stored losslessly, so the only quality loss is whatever the JPEG already had.
Start bigger than you need
Feed in at least 256 pixels square. Each size is rendered down from your source, and a source smaller than 256 simply cannot produce a sharp 256-pixel entry — that detail does not exist to be recovered.
Check the 16-pixel version before you ship it
Open the file and look at the smallest size at actual size, not zoomed in. It is genuinely surprising how much disappears. Fine lines vanish, thin text becomes a grey smear, and detail that looked essential at 256 pixels turns out to be noise.
If it fails that test, the answer is a simpler design rather than a better conversion.
A better route for most people
If this is for a website, the favicon generator produces the
whole set a modern site needs — the ICO plus the PNG sizes Apple and Android look for — rather than
the ICO alone. Browsers have wanted more than favicon.ico for years.
What ICO is for
ICO is a Windows format from the 1980s, and its one clever idea has aged well: a single file can hold the same image at several sizes, so whatever is displaying it picks the right one instead of scaling.
- Browser tabs and bookmarks —
favicon.icoat a site's root remains the universal fallback. - Windows application icons and desktop shortcuts.
- Installers, which conventionally require ICO.
- Folder icons and other shell customisation.
Why favicon.ico still matters
Modern sites declare their icons in HTML and use PNGs at various sizes. But browsers still ask
for /favicon.ico directly, without being told to, and so do feed readers, chat apps
generating link previews, and bookmark managers.
Having one costs nothing and prevents a stream of 404s in your logs. It is the belt-and-braces file even when your real icons are elsewhere.
Making a photograph work as an icon
If you must use a photograph:
- Crop hard. One face, one object, filling the frame. Anything showing a scene is lost.
- Raise the contrast well past comfortable. Small images need exaggeration to read at all.
- Simplify the background to a single flat colour, or remove it and use a PNG so it can be transparent.
- Test at 16 pixels first, before doing any of the rest.
Going the other way
ICO to PNG extracts the largest image from an icon, which is how you
recover artwork from an old .ico when the original is long gone.
What happens to your file
Browsers cannot write the ICO container, so this runs on our server. Your upload is deleted the moment conversion finishes, the result is deleted as you download it, and anything abandoned is swept automatically.
Privacy
What happens to your file
This tool runs on our server, so it works the same on every phone and computer. Your file is uploaded, and this is exactly what happens to it:
- Stored outside the public web root under a random name, never under your file's name.
- Processed, with the original upload deleted immediately — whether it succeeded or failed.
- The result sits behind a signed link that only you receive, which stops working after 20 minutes, and the file is deleted the moment you download it.
- Anything never collected is deleted automatically within 30 minutes.
- The image itself is never logged or kept. If a conversion fails, we record the formats involved and the error — not the file.
- Camera metadata, including any GPS coordinates recording where a photo was taken, is removed from the result. Only the rotation needed to show the image the right way up is kept.
Questions & answers
JPG to ICO: frequently asked questions
Why does my icon have a white background?
Because JPEG has no transparency — the format has no alpha channel at all, so whatever background the image had is permanently part of it. This cannot be fixed at conversion time; the transparency has to exist in the source. Use a PNG with a genuine transparent background instead.
My photo looks like a smudge at small sizes.
That is expected. A 16×16 icon is roughly the size of a letter on this page, and a photograph reduced to it becomes a blur of average colours. Icons that work small are simple — one shape, two or three colours, strong contrast — which is why recognisable favicons are letters, symbols or silhouettes rather than scenes.
What sizes go into the file?
16, 32, 48 and 256 pixels, all in one file — that is the whole point of ICO. A browser tab takes the 16, a desktop shortcut the 48, a large tile the 256, each rendered specifically rather than scaled from a mismatch. Sizes larger than your source are skipped rather than invented.
What happens if my image is not square?
It is centred on a square canvas rather than stretched, so the proportions survive. With a JPEG source that padding is filled rather than transparent, which is another reason a PNG gives a better result — there the padding is genuinely clear and the icon keeps its shape on any background.
How big should my source image be?
At least 256 pixels square. Every size is rendered down from your source, so a smaller source simply cannot produce a sharp 256-pixel entry — that detail does not exist to be recovered.
Do I still need a favicon.ico in 2026?
Yes, as a fallback. Modern sites declare PNG icons in HTML, but browsers still request /favicon.ico directly without being told to, as do feed readers, chat apps building link previews, and bookmark managers. It costs nothing and prevents a stream of 404s.
Keep going
Related image tools
PNG to ICO Converter
Convert PNG to a proper multi-size ICO containing 16, 32, 48 and 256 pixel versions. Transparency preserved.
Favicon Generator
Generate a full favicon set from one image: multi-size ICO, Apple touch icon, Android icons, manifest and the HTML to paste in.
ICO to PNG Converter
Convert Windows ICO files to PNG, keeping transparency. Extracts the largest image the icon contains.
JPG to PNG Converter
Convert JPG images to lossless PNG, free and with no sign-up. Understand when converting helps, and when it just makes a bigger file.