Unuploaded

Converter · No upload

Convert JPG to WEBP on your device

Convert JPG photos to WEBP and compare the original and output file sizes on each row.

The sample is a 240×120 JPG made in this tab. Compare the WEBP’s size and appearance with the JPG; some browsers switch to lossless WEBP at quality 1.

Read here — Statusidle Files— OutputWEBP Network since file read—

Undecodable JPGs fail, with browser reasons where available, as do images too large for the browser’s canvas, and unsupported WEBP encoding is an error. The WEBP encoder can reduce an image’s dimensions without a row warning; the row shows input dimensions. One WEBP per file, default 0.92; quality affects pending encodes. EXIF, GPS, camera model, timestamps and colour profile are not copied. Takes .jpg and .jpeg.

How this converter works

The File API reads the selected JPG into memory. The browser decodes it, draws the pixels onto a canvas and encodes WEBP at the chosen quality, using its own image decoder and WEBP encoder with no extra conversion library. The result is offered as a download, with the input and output file sizes on its row.

You can choose several JPGs and convert them as a batch. They are processed one after another in the browser, without upload. The network counter starts at the first file read and keeps counting across the whole batch until you close the tab, so it does not reset for each picture. What that counter observes and what it misses is set out on the methodology page.

Keep the original JPG for archiving or editing: WEBP cannot restore detail the JPG already lost, and a lossy WEBP encode can add further loss. Savings vary with the image and the quality, and a small or heavily compressed JPG can come out no smaller. Encoding is done by the browser, so results can differ between browsers, and the output pixels are 8-bit sRGB. The WEBP encoder has size limits of its own, separate from the canvas, so check the saved image’s dimensions if they matter. Some desktop programs and upload forms reject WEBP; WEBP to JPG (the reverse) converts back when a recipient needs JPG.

Frequently asked questions
Is my photo uploaded anywhere?
No. The browser decodes the JPG and encodes the WEBP through a canvas in this tab. The network meter counts resource-timing entries from the first file read onward, which leaves out earlier page loads and some connection types. The methodology page explains what its reading and an offline test can show.
How much smaller will the WEBP be?
It depends on the image, how it was compressed and the quality you choose. A quarter to a third smaller is a rough illustration; the result row shows the actual input and output sizes for your file. Fine texture can be harder to compress, so if the WEBP comes out larger or looks worse, keep the JPG.
What quality setting should I use?
The dial starts at 0.92. For a smaller file, try around 0.80–0.85, then check both the size and the visible detail at the size the image will be shown. The best setting differs from one photograph or graphic to the next.
Will the WEBP look better than my JPG?
No. Converting does not restore detail missing from the JPG, and WEBP re-encoding can add loss of its own, so inspect the output and keep the JPG original. Convert for a smaller delivery size or for a workflow that wants WEBP.
What if my browser can't encode WEBP?
The file gets an error row. Some browsers return a PNG when asked for a canvas format they cannot encode; this page checks the actual result and refuses a mismatch, and it does not just rename a PNG to .webp. Support depends on the browser and its version.

Related tools