CometWeb tools
WebP converter
PNG · JPG → WebP / AVIF · in-browser batch conversion, nothing uploaded
Why convert images to AVIF or WebP?
AVIF and WebP usually produce much smaller files at quality close to JPG/PNG.
Smaller payloads help LCP, transfer cost and (at scale) CO₂e estimates. This is not an emissions measurement.
Conversion is local (canvas). Images never leave the browser, and with a large batch the pace is limited by your device memory and CPU.
Compare quality on real images
Test photos, graphics containing text and transparent images separately. Inspect fine edges and tonal transitions. The smallest file is not always the best choice if details are visibly lost.
web.dev · Image formats ↗Which format to pick?
- AVIFAV1 Image Format
- Often the smallest modern option. Needs browser encode support.
- WebPWeb Picture Format
- Wide support, solid size/compatibility trade-off.
- JPGJPEG
- Legacy standard without transparency, often a fallback.
- PNG
- Lossless with transparency. WebP/AVIF usually cuts transfer a lot.
Drop one or more PNG files above, keep WebP as the target format and set the quality (80 is a good start; go higher for logos and screenshots). Each file shows its size before and after, and WebP keeps PNG transparency. Download the converted files when the list finishes; nothing is uploaded.
Yes (like JPG). Quality ~80 is a common start. Use higher quality for logos.
Decode yes in newer versions. Encode depends on the browser, otherwise fall back to WebP.
Canvas encoding usually drops metadata. Treat this as strip.
No. Conversion takes the first frame, so the WebP or AVIF output is a still image, and the saving shown covers that single frame, not the animation.
What else might come in handy
A CO₂e estimate and asset weight, broken down by source, with a reduction plan.