Check an image and save the result
- 1
Choose a local WebP
Select your source within the current file limits. Compression starts automatically after selection, without a separate Start button.
- 2
Compare the output
Inspect the preview and the original and result sizes. A result that keeps the original size may mean the source was already the smaller valid file.
- 3
Download the image
Save the result and open it in your destination app. Keep the original until you have checked appearance, transparency and any animation.
Compress several images together
For a folder of separate images, compress multiple WebP files. Review each status and download results individually or in a ZIP; the archive collects outputs rather than serving as an image input.
What stays with the image
The compressor uses the source lossy or lossless mode and preserves transparency, animation frames, timing and loops. EXIF, ICC and XMP metadata are retained. It does not resize the image or discard metadata simply to report a larger reduction.
If the re-encoded file is valid but not smaller, the original is retained. There is no guaranteed percentage reduction, and a smaller result should still be checked in the app that matters to you.
For animation, watch a full cycle and its restart instead of checking only a thumbnail. Compare pauses and moving objects, then inspect partially transparent edges against the background where the image will appear.
Quality and target-size expectations
This tool does not expose a quality slider, an encoding-method selector or an exact kilobyte target. It cannot promise a result under 100 KB or another upload limit. Image dimensions, visual complexity, animation length and existing compression all affect the available savings.
The WebP quality guide explains lossy and lossless tradeoffs. Changing encoding effort is not the same as changing pixel dimensions, and a “100” quality label elsewhere does not automatically mean mathematically lossless output.
The official WebP encoder reference distinguishes quality from compression method: method or level settings trade processing effort against the encoded result. They are not image dimensions, and this page selects its encoding settings automatically.
Lossless pixel encoding and a visually acceptable lossy result are different claims. A good-looking preview does not prove that every decoded pixel stayed identical, and recompression cannot restore detail the source already lost.
If the file is still too large and smaller dimensions are acceptable, resize the WebP before trying another compression pass.
Does the destination require another format?
Compress WebP when you want to keep WebP output. If a form needs an opaque still image, convert WebP to JPG. For static output that keeps alpha, convert WebP to PNG. Those conversions have different animation and metadata boundaries.
For a non-WebP source, first choose an image conversion direction. Renaming a PNG or JPG file to .webp is not encoding it, and choosing compression does not make an unsupported application accept the format.
Questions and answers
Practical answers for this task.
No exact-size control is offered. Check the actual result against the receiving service’s limit; some sources cannot shrink enough without other changes.
Image processing runs locally, but initial asset loading and licensing or account checks can require a connection. Follow the current usage information shown by the tool.
Not necessarily. A valid re-encode that is no smaller is replaced by the original. A genuine error is reported separately in the item status.
Check that the original is a complete, valid WebP rather than another format with a renamed suffix. Read the item’s actual error. Keep the source and try a valid replacement after addressing the reported problem.
Compare visible detail, transparent edges, animation and actual bytes in the destination app. There is no universal best result or guaranteed saving. Any free allowance and applicable usage rules come from the current service information.