JPG → WEBP
☞ runs entirely in your browser — nothing is uploadedDrop your JPG here
or click to browse — JPG / JPEG only
Converted preview
OneImageTool
Free Image Tools
JPG → WEBP
Shrink JPEG photos to WebP for faster pages — convert with quality control.
or click to browse — JPG / JPEG only
Converted preview
one engine, many formats
Swapping JPEG for WebP is the cheapest page-weight win most sites have left: the same picture, typically a quarter to a third fewer bytes, and no markup change needed for any browser released in the last several years.
The catch is that you are re-encoding an already lossy file. The artifacts baked into the JPEG cannot be removed, and a low quality setting here stacks a second round of loss on top of them.
jpeg vs webp
Same pixels, a more efficient encoder, and one thing worth being careful about.
WebP usually lands well under the JPEG for the same perceived quality, which is why it is worth doing across a whole image folder rather than one hero image.
The exported WebP can carry transparency even though the JPEG could not. Nothing is added automatically, but the format no longer stands in the way if you edit it later.
You are compressing an already compressed image. Keep quality at 80 or above unless you have compared the result against the original at full size.
three steps
Drop a .jpg or .jpeg file. The page locks the input format, so a stray PNG is rejected rather than quietly converted.
The preview re-encodes as you move the slider. 80 to 85 is a good starting range for photographs on a web page.
Save the .webp and point your markup or CDN at it. The original JPEG on your disk is left alone.
quick answers
For photographs, commonly a quarter to a third smaller than the JPEG at a comparable quality setting. Images that were already heavily compressed save less, because most of the redundancy is gone.
Every current browser does. Very old Safari and Internet Explorer versions do not, which is why a picture element with a JPEG fallback is still a reasonable pattern for very broad audiences.
Not on a JPEG source. The image has already lost detail once, and a second aggressive pass tends to make the existing artifacts more visible rather than hide them.
WebP supports it, but a JPEG has no transparency to carry over. Start from a PNG if you need an alpha channel in the result.
No. Width and height are preserved exactly. Resize first if the image is larger than it needs to be — resizing usually saves more bytes than any quality setting.
No. Decoding and encoding both happen on your device through the canvas API. Nothing is sent to a server.