Unuploaded

Converter · No upload

JPG to WEBP, privately

Convert JPG photos to WEBP and compare the original and output file sizes on each row. Savings depend on the image and quality setting. Processing is local and works offline once the page has loaded. Keep the original JPGs: conversion is another encode, not a recovery of lost detail.

Statusidle Files— OutputWEBP Network since file read—

Undecodable JPGs fail, with browser reasons where available. Images beyond canvas capacity fail; unsupported WEBP encoding is an error. WEBP export may reduce dimensions without a row warning; shown dimensions are decoded input, not checked output. One WEBP per file, default 0.92; quality affects pending encodes. Source EXIF, GPS, timestamps and colour profile are not copied. Takes .jpg and .jpeg.

The sample is a 240×120 JPG made in this tab. WEBP can be lossy; some browsers select lossless encoding at quality 1. Neither restores JPG detail. Compare output size and appearance; it may not be smaller.

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. The result is offered as a Blob download, with input and output file sizes shown on the row. This uses the browser's image decoder and WEBP encoder rather than an additional conversion library. A browser that cannot produce WEBP gets an error rather than a differently formatted file with a WEBP extension.

Choose several JPGs to convert as a batch. Files are processed one after another in the browser without uploading them, and each result row shows the original and output file sizes. The network counter starts on the first file read and keeps counting across the batch until the tab closes; it does not reset for each picture. The methodology page explains what that counter observes and what it misses.

WEBP cannot restore detail already lost in a JPG, and a lossy WEBP encode can add further loss. Keep the original JPG for archiving or editing. Size savings vary with image content and quality; a small or heavily compressed JPG may not get smaller. Some desktop applications and upload forms reject WEBP; WEBP to JPG (the reverse) is available when a recipient needs JPG. Encoding is browser-native, so outputs can differ between browsers. Original EXIF fields, including GPS, camera model and timestamps, are not copied. Output pixels are 8-bit sRGB and the embedded input colour profile is not carried. Moving the quality dial affects files not yet encoded. Decode failures include the browser's reason when available; an image beyond the browser's canvas capacity is reported as failed. The native WEBP encoder has separate size limits and may produce a file with reduced dimensions even when the image fits the canvas. The row shows decoded input dimensions, not verified saved-output dimensions, and does not warn of this reduction. Check the saved image's dimensions if they matter.

Frequently asked questions

Is my photo uploaded anywhere?
No. The browser decodes the JPG and encodes WEBP through canvas locally. The meter counts resource-timing entries from the first file read, not earlier page loads or every connection type. The methodology page explains what its reading and an offline test can establish.
How much smaller will the WEBP be?
Savings vary with the image, source compression and selected quality. A quarter-to-third reduction is an illustrative comparison, not a prediction for your file. The result row shows actual input and output file sizes. Fine texture can be harder to compress; if the output is larger or looks worse, retain the JPG.
What quality setting should I use?
The dial starts at 0.92. To look for smaller output, try around 0.80–0.85 and inspect both the size and visible detail at the intended display size. These are starting points, not guarantees about every photograph or graphic.
Will the WEBP look better than my JPG?
The conversion does not restore detail missing from the JPG. WEBP re-encoding can introduce additional loss, so inspect the output and retain the JPG original. The reason to convert is delivery size or compatibility with your intended workflow, not automatic quality improvement.
What if my browser can't encode WEBP?
If the browser cannot produce WEBP, the file gets an error row. Some browsers return PNG when asked for an unsupported canvas output format; this page inspects the actual result and refuses a mismatch instead of changing only its extension. Support depends on the browser and version.

Related tools