Skip to content
nah

Image Compression

Convert and compress images to WebP, AVIF, JPEG XL, or PNG with full quality control. No upload needed.

100% in your browser — files never leave your device

Six formats, one tool — no upload required

Image compression tools that run server-side charge per image, impose file size limits, or quietly retain your uploads. This tool encodes entirely in your browser using WebAssembly builds of the same codecs used in production image pipelines.

WebP is the right default for most use cases: excellent compression, fast encoding, and universal browser support since 2020. AVIF cuts file size by another 30-50% at the cost of slower encoding — worthwhile for high-traffic pages where bandwidth savings add up. JPEG XL offers the best theoretical quality-to-size ratio but has limited native browser support as of 2026.

For lossless output — screenshots, graphics, icons — PNG and OxiPNG preserve every pixel. OxiPNG applies extra optimization passes to produce files 10-20% smaller than standard PNG with identical content. All processing happens locally; nothing is transmitted.

Frequently asked questions

Are my images uploaded to compress them?

No. Compression runs entirely in your browser using WebAssembly codecs. Your images never leave your device — no upload, no server, no account required.

Which output formats are supported?

WebP (best speed/size balance, widely supported), JPEG (universal compatibility), AVIF (40-50% smaller than JPEG, slower to encode), PNG (lossless, standard), OxiPNG (optimized lossless PNG, smaller than standard PNG), and JPEG XL (next-gen quality, limited browser support).

What is the difference between PNG and OxiPNG?

Both produce lossless PNG output. OxiPNG applies additional optimization passes (via the oxipng WebAssembly codec) to produce smaller files than the standard browser PNG encoder, at the cost of slightly longer encoding time. The pixel content is identical.

What quality setting should I use?

Each codec has a sensible default: WebP at 80, JPEG at 75, AVIF at 50, JPEG XL at 75. Lower values shrink the file further at the cost of visible artifacts. The quality slider adjusts the codec's internal quantization parameter — there is no universal "equivalent quality" across codecs.

Why is AVIF so much slower than WebP?

AVIF encoding is computationally expensive — the codec trades CPU time for file size. Expect 2-10x longer encoding time compared to WebP at equivalent visual quality. The result is typically 30-50% smaller than WebP, which is worth it for images served at scale.

Related tools