Convert JPG to ICO.
Turn a JPG logo into a multi-size favicon ICO — locally.
Drop JPG files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Turn a JPG logo or photo into a classic favicon.ico with 16–256 px versions embedded — generated entirely in your browser, so the file never leaves your device. Non-square images are centered on a transparent square rather than stretched.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
From photo to favicon
Favicons live at 16–48 px, so detail disappears fast — bold shapes and strong contrast survive, fine text does not. Crop tight around the mark before converting, and check the 16 px look in a browser tab. If your logo exists as a transparent PNG or an SVG, PNG to ICO and SVG to ICO keep the cut-out edges.
Shipping the favicon
Name the file favicon.ico and put it at your site root — browsers request that exact path on their own, no markup needed. If the same JPG also appears on the page, Compress JPG shrinks it for serving.
Frequently asked questions
Which sizes end up in the ICO?
256, 128, 48, 32 and 16 px — sizes larger than your source are skipped. One file covers browser tabs, bookmarks, desktop shortcuts and Windows Explorer views.
My JPG isn’t square — what happens?
It is centered on a transparent square canvas rather than stretched, and every icon size is scaled from that square. For best results, crop the image to a square first.
Wouldn’t a PNG be a better source?
If you have one, yes — PNG carries transparency, so cut-out logos stay see-through. From a JPG the icon is a solid rectangle, which is fine for photos and boxed logos.
Is it private?
Yes. The conversion happens entirely on your device — the image is read, re-encoded and saved without ever touching a network. There is no server-side queue, no temporary copy in some bucket, nothing to expire or leak. Want proof? Run one file through, switch your connection off, and run another — it still works.