Compress WEBP images

What compressing WEBP actually does

WebP is already an efficient format, so compressing an existing WebP is usually about hitting a specific size limit rather than chasing a general saving. The useful lever is quality: WebP holds up better than JPEG at low settings, and quality 70 is often perfectly acceptable where a JPEG at 70 would look obviously degraded.

Bear in mind that re-encoding a WebP compresses an already-compressed image. If you still have whatever the WebP was made from, going back to that original will give a noticeably better result at the same file size.

Getting a good result

• WebP degrades more gracefully than JPEG. Quality 70 is usable where a JPEG at 70 would show visible blocking.
• Switch to lossless mode for screenshots, logos and anything with text — lossy WebP softens hard edges.
• A transparent WebP compresses its alpha channel separately, and hard cutouts can pick up a faint halo in lossy mode.
• Above quality 90, WebP loses its advantage over JPEG and can produce larger files.

Hitting an exact file size

Upload forms, government portals and job applications frequently demand a file "under 200KB" and reject anything over it, without telling you by how much. Tick Aim for a specific file size and BriskFile searches for the highest quality that still fits, re-encoding up to eight times to find it.

The result is always under your limit, not near it. A file three kilobytes over the cap is rejected exactly as firmly as one three megabytes over.