▮ Unuploaded

Converter · No upload

JPG to WEBP, privately

Drop in JPGs and download WEBP files that are typically much smaller at the same visible quality — the point of the format, and the reason pages built on it load faster. The conversion runs entirely inside your browser: nothing is uploaded, the network meter below proves it live, and it works with your wifi off. It is a re-encode, so keep your originals.

Statusidle Files— OutputWEBP Network since file read—

How this converter works

Your browser decodes JPG on every web page it loads, and every current browser can also encode WEBP from a canvas — so both halves of this conversion are already sitting in the software you're using. When you choose a file, the File API opens it in memory, the browser's decoder turns it into raw pixels, those pixels are drawn onto a canvas inside this tab, and the canvas encodes them to WEBP at the quality you set on the dial. The result is wrapped in a Blob and handed back as a download link, with the before and after sizes printed on the row so you can see what the trade actually bought. No step touches the network, because the file is already on your machine and this site has no server to send it to.

Volume is where this property starts to matter. Drop in an entire holiday folder — forty photos, eighty — and they process one after another, each row printing its old and new size, while the counter beside them holds steady at zero requests for the whole run. Not zero per picture: zero across the batch, because the counter arms once on your first file and keeps watching until you close the tab. Sending eighty personal photographs to a stranger's machine in order to save a few megabytes was always a peculiar bargain, and here you simply never strike it. See the methodology page for what that counter does and does not observe.

The honest limits. This is lossy-to-lossy: WEBP cannot recover anything JPG already threw away, and it adds a second generation of loss on top, so treat the output as a distribution copy and archive the JPG. Savings vary a lot by image — fine texture and noise compress poorly in any format, and a small or already-heavily-compressed JPG may come out no smaller at all. Support is broad in browsers but thinner outside them: some desktop software and upload forms still reject WEBP, and WEBP to JPG is the way back if you hit one. Encoding is done by the browser's own WEBP encoder, so results differ slightly between browsers; if yours cannot encode WEBP the file is reported as an error rather than silently returned in another format. Re-encoding also strips EXIF metadata — GPS, camera model, timestamps — from the output.

Frequently asked questions

Is my photo uploaded anywhere?
No. Your browser decodes the JPG itself, redraws it on a canvas inside this tab, and re-encodes it as a WEBP — all in memory, on your device. The readout's network meter counts every request from the moment your file is read and stays at zero, and the methodology page shows how to verify that independently.
How much smaller will the WEBP be?
For ordinary photographs, a meaningful fraction — often something like a quarter to a third off at a comparable setting, though it varies enough that averages aren't worth planning around. The results row prints the before and after size for your actual file, which is the only number that matters. Images dense with fine texture save least, and if one comes out larger, keep the JPG.
What quality setting should I use?
Somewhere around 0.80 to 0.85 is the usual sweet spot for WEBP — it degrades more gracefully at lower settings than JPG does, and that resilience is where most of the savings live. The dial starts at 0.92, which is deliberately conservative; lower it and watch the size figure until the result stops looking right at full zoom.
Will the WEBP look better than my JPG?
No. This is a re-encode of an already-lossy file, so the WEBP inherits every artifact the JPG had and adds a small amount of its own — generation loss, and the reason to keep your originals. WEBP's advantage is size at a given quality, not quality itself. Convert copies for the web and archive the JPGs.
What if my browser can't encode WEBP?
Then that file is reported as an error in the results list rather than converted. Some browsers accept a WEBP request from a canvas and quietly hand back a PNG instead; this page checks what actually came out and refuses to give you a file whose contents don't match its name. Current Chrome, Edge, and Firefox encode WEBP natively, as do recent versions of Safari.

Related tools