Drop your ICO file into the picker and our encoder produces a WebP 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 ICO.
Will WebP actually be smaller than ICO?
+
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 WebP = PNG / JPG) typically grows the file because you are leaving a more modern codec for an older one — useful for compatibility, not size.
Does ICO to WebP preserve transparency / alpha?
+
Transparency survives when WebP 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 WebP.
Can I keep my color profile (sRGB / Display P3) going from ICO to WebP?
+
Yes for WebP 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 WebP. If WebP cannot store a profile, output is tagged sRGB to keep browsers from guessing.
What lossy vs lossless quality settings does the WebP encoder support?
+
Lossy WebP (WebP / AVIF / JPG) accepts a quality 1-100, default 80. Lossless WebP (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 WebP targets when source ICO mixes photos and graphics.
Will the WebP version look identical to the ICO 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 ICO is screenshots or UI mockups, push quality to 90 or use a lossless WebP.
Does ICO to WebP keep animation frames?
+
Animated ICO (animated WebP, GIF, APNG) survives only when WebP is also animation-aware (animated WebP, GIF, APNG). Converting an animated ICO to a static WebP (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 ICO to WebP?
+
Yes by default when both ICO and WebP 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 WebP leaves your browser.
Can I batch convert a folder of ICO files to WebP?
+
Yes — drop multiple ICO 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 ICO files private during WebP conversion?
+
Yes — uploaded ICO 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 WebP with a ICO fallback on my site?
+
Use a `<picture>` element: `<picture><source srcset="image.WebP" type="image/WebP"><img src="image.ICO" alt=""></picture>`. Browsers that understand WebP fetch the smaller file; older browsers fall back to ICO. WebP is supported in 96%+ of installed browsers, AVIF in 90%+.
Why is my WebP file unexpectedly bigger / smaller than I expected?
+
A ICO that is already heavily compressed (low-quality JPG) often grows when re-encoded into a lossless WebP (PNG / TIFF). A high-bitrate lossless ICO (PNG / TIFF) often shrinks 60-90% when going to a lossy modern WebP (WebP / AVIF). Image content matters too — photos compress very differently from line art and screenshots.