Drop your JPEG file into the picker and our encoder produces a ICO output tuned for web delivery: quality factor 80 by default (a Lighthouse sweet-spot), correct color space, and an Accept-aware fallback you can ship behind a `<picture>` element alongside the original JPEG.
Will ICO actually be smaller than JPEG?
+
Almost always when going from PNG / JPG / TIFF into WebP or AVIF: expect 25-50% smaller than JPG at the same visual quality, 60-90% smaller than PNG. Going the other way (WebP / AVIF back to ICO = PNG / JPG) typically grows the file because you are leaving a more modern codec for an older one — useful for compatibility, not size.
Does JPEG to ICO preserve transparency / alpha?
+
Transparency survives when ICO supports alpha (PNG, WebP, AVIF, GIF, TIFF, SVG). Converting to JPG flattens the alpha channel onto white — if you need transparency on the modern web target WebP or AVIF instead of ICO.
Can I keep my color profile (sRGB / Display P3) going from JPEG to ICO?
+
Yes for ICO formats that store ICC profiles (PNG, JPG, WebP, AVIF, TIFF). Modern wide-gamut profiles like Display P3 round-trip through WebP and AVIF; sRGB profiles round-trip through every common ICO. If ICO cannot store a profile, output is tagged sRGB to keep browsers from guessing.
What lossy vs lossless quality settings does the ICO encoder support?
+
Lossy ICO (WebP / AVIF / JPG) accepts a quality 1-100, default 80. Lossless ICO (PNG / WebP lossless / TIFF) does not take a quality dial — every pixel is preserved. WebP and AVIF are the only formats that can do either, which is why they are ideal ICO targets when source JPEG mixes photos and graphics.
Will the ICO version look identical to the JPEG on a Retina display?
+
At quality 80+ on WebP / AVIF the difference is invisible to anyone but a trained eye even at 3x device pixel ratio. Photos compress slightly more visibly than line art; if your JPEG is screenshots or UI mockups, push quality to 90 or use a lossless ICO.
Does JPEG to ICO keep animation frames?
+
Animated JPEG (animated WebP, GIF, APNG) survives only when ICO is also animation-aware (animated WebP, GIF, APNG). Converting an animated JPEG to a static ICO (PNG, JPG, AVIF still) yields just the first frame — use a dedicated animation converter if you need to keep all frames.
Will EXIF camera metadata survive JPEG to ICO?
+
Yes by default when both JPEG and ICO support EXIF (JPG, PNG, WebP, TIFF, HEIC). Camera fields (ISO, shutter, lens, GPS) are copied through. Use the "strip metadata" option if you are publishing to the web and want to drop GPS coordinates before ICO leaves your browser.
Can I batch convert a folder of JPEG files to ICO?
+
Yes — drop multiple JPEG files at once and they encode in parallel. Free accounts: 100 MB per file. Pro accounts get more parallel workers and bigger per-file caps, so a 200-image gallery typically finishes in well under two minutes.
Are my JPEG files private during ICO conversion?
+
Yes — uploaded JPEG files are processed in isolated workers and deleted within minutes. No human reviews the pixels, no copy is retained, no third party gets a feed. See /privacy/ for the precise retention window.
How do I serve the ICO with a JPEG fallback on my site?
+
Use a `<picture>` element: `<picture><source srcset="image.ICO" type="image/ICO"><img src="image.JPEG" alt=""></picture>`. Browsers that understand ICO fetch the smaller file; older browsers fall back to JPEG. WebP is supported in 96%+ of installed browsers, AVIF in 90%+.
Why is my ICO file unexpectedly bigger / smaller than I expected?
+
A JPEG that is already heavily compressed (low-quality JPG) often grows when re-encoded into a lossless ICO (PNG / TIFF). A high-bitrate lossless JPEG (PNG / TIFF) often shrinks 60-90% when going to a lossy modern ICO (WebP / AVIF). Image content matters too — photos compress very differently from line art and screenshots.