JPG → WEBP
JPG to WEBP converter
Drop a JPG and get a WEBP that weighs about a quarter less at the same visual quality. The re-encode happens in this tab, so client photographs never cross the network.
WEBP adds a second generation of lossy compression to pixels that were already compressed, so keep the quality high; the JPEG's EXIF block does not carry over.
How to convert JPG to WEBP
Load the JPEG file
Drop the file or pick it from disk. The extensions .jpeg, .jpe and .jfif are all JPEG input, and each file is converted on its own.
Choose a high quality
Because the picture is compressed twice, 90–95 keeps it looking untouched; dropping to 75 trades visible detail for a few more kilobytes.
Save the WEBP asset
Save it as a site asset: every current browser renders WEBP, and the picture can sit on the page beside older JPEG fallbacks.
What happens when a JPG becomes WEBP
JPEG and WEBP both use block-based lossy compression, so this is not a move from a lossy world to a lossless one — it is a re-encode. WEBP's encoder is simply more efficient: at a quality a viewer can perceive, it needs roughly 25–35% fewer bytes than JPEG for the same picture, and it can also hold an alpha channel and animation.
Two consequences follow. The pixels pass through a second quantisation, so the quality should be set high enough that the trip is invisible. And the JPEG's metadata — EXIF timestamps, GPS, the orientation tag — is not written into the WEBP, which is a privacy gain and a loss if the capture data mattered. Keep the JPEG for print or archival work; WEBP is a delivery format.
JPG to WEBP questions
How much smaller is WEBP than JPG, really?
Google's comparisons put it at about 25–35% fewer bytes for equal perceived quality, and most pictures land inside that band. Flat, low-detail images gain less; busy photographs gain more. The result panel reports the exact new size.
Does converting back and forth damage my photo?
Every lossy save costs something, and this one is a second generation on an already compressed file. At quality 92 to 95 the difference is not visible at normal viewing sizes; if the picture will be edited and re-saved many times, work from the JPEG or a RAW copy.
Where does my photo go while it converts?
Nowhere: the decode and the encode both run on APIs inside this tab, so the picture never reaches a server. There is no queue, no sign-up and no watermark, and it keeps working once loaded, even with the Wi-Fi off.
Is there a file-size ceiling?
64 MB per image and one conversion at a time. Everything is held in memory in the tab, so a larger JPEG belongs in a desktop tool; for ordinary photos and website assets the ceiling is far away.