JPG → WebP
Converting locally — nothing is uploaded
Same photo, markedly less weight — free, and finished on your machine.
Drop your JPGs in the drum
or — nothing leaves this tab
READS JPG · PNG · WEBP · GIF · BMP · SVG · AVIF
CYCLE →
WASH TEMP
OUT OF ORDER — JAM REPORT
The JPG → WebP cycle
The standard swap before publishing to the web: identical-looking photographs at a fraction of the weight, accepted by every browser released in the last decade.
WebP keeps transparency; JPG had none to give. Expect the folded copy noticeably lighter than the load. Either way, re-encoding through the canvas collects EXIF like lint — camera model, GPS coordinates and timestamps are stripped from the folded copy.
Need the other direction? WebP → JPG · Other routes into PNG → WebP, GIF → WebP, BMP → WebP.
Questions at the counter
How much smaller is WebP than JPG?
Typically 25–35% at matching visual quality. The exact figure depends on the image — busy textures shrink less, clean backgrounds shrink more. The ticket shows your actual before-and-after weight.
Can every browser open WebP?
Every current one can: Chrome, Edge, Firefox and Safari have all shipped support since 2020. Only very old software — legacy image viewers, some print-shop RIPs — still balks.
Which temperature should I wash at?
Warm (our default, roughly quality 85) suits most photographs. Hot for hero images you will crop or zoom; Cold when page weight matters more than fidelity, such as thumbnail grids.
Is the conversion really private?
Yes — architecturally. This page is static files; there is no server to receive an upload. Your JPG is decoded and re-encoded inside this tab by your own machine, and you can watch the absence of network traffic in your browser’s developer tools.