Queued
Local re-encoding
WebP Compressor
Reduce an existing WebP by re-encoding it at a chosen quality, optionally at smaller dimensions. Everything runs locally, so the file does not spend time traveling to and from a compression server.
Compression results vary by image. A source that is already well optimized may shrink very little or can even grow at a higher quality setting. WebpForge reports the real output size so you can make the decision from the actual file.
WebP to WebP browser converter
Advanced settings
Used because JPG cannot store transparency.
Re-encoding creates a new file without source metadata.
100% Private. Images are processed locally on your device with no uploads.
No paywalls. Unlimited file conversions with zero daily limits or account sign-ups.
Quality and dimensions do different jobs
Lower quality asks the encoder to discard more visual information. Smaller dimensions reduce the number of pixels that must be stored. If an image is larger than its real display size, resizing is often the more defensible first step.
Repeated lossy compression accumulates damage. Compress from the best available source rather than repeatedly processing a previously compressed output.
Evaluate the result, not a percentage promise
Flat graphics, photographs, noise, transparency, and prior encoder settings respond differently. There is no honest universal saving. Compare the displayed byte sizes and inspect key images at their intended size.
- Try the default quality, then lower it in small steps if needed.
- Preserve the original outside this browser session.
- Avoid enlarging dimensions during compression.
Practical examples
- Situation
- A WebP photograph is twice the dimensions used by a site.
- Setting
- Set the actual display width and begin near quality 76.
- Expected result
- A smaller derivative whose measured output size is shown before download.
- Situation
- An already optimized WebP produces a larger result.
- Setting
- Keep the original or test a lower quality after visual inspection.
- Expected result
- No misleading claim that every recompression must save space.
Continue with purpose
Related tools and guides
Clear answers
Frequently asked questions
Will every WebP become smaller?
No. Existing compression, content, dimensions, and the new quality setting determine the result. The output may be larger, and the tool shows both sizes.
What quality should I use?
Start around 75–80 for a web derivative and inspect the result. Detailed or critical images may need a higher value.
Does compression remove metadata?
Yes. The decoded pixels are encoded into a new WebP without copying source metadata.
Is the image sent anywhere?
No. The WebP decoder and encoder run in local browser workers.