Convert JPG to WEBP

JPG → WebP cuts 25–35% at the same visual quality

No upload
Exact target size
Batch ready

Drag images here, or click to choose

JPG / PNG / WebP / HEIC · up to 25MB each · batch supported

Files never leave your device — everything runs in your browser.

Quality (lossy targets)

92%

Remove EXIF / GPS

What changes in a JPG → WEBP conversion

The cheapest win on the web: same pixels, a quarter smaller. The only reason to stay on JPG is a portal that hard-rejects .webp, and those still exist in government and banking forms.

What you lose

Support in a few legacy upload forms
Progressive decoding behaviour differs slightly

What survives

All pixels, no alpha to lose
Metadata is dropped — good for privacy

Colour profile handling

The decoded image is re-tagged as sRGB, which is what browsers and forms assume. A wide-gamut source will look slightly flatter but consistent; that trade is deliberate, because an untagged file looks different on every device.

Batch conversion

Drop a folder and every supported file is converted with the same settings. Progress is per file, failed files are retryable, and the whole set downloads as one ZIP. Nothing is queued on a server, so there is no upload time and no retention window.

Frequently asked questions

Does converting JPG to WEBP reduce quality?

Slightly. The image is decoded once and re-encoded once, which is one generation of loss. Set quality to 90 or higher to keep it invisible.

How many files can I convert at once?

Up to 200, with 4 concurrent workers. Each file keeps its own name, with the new extension appended.

Why does my JPG file fail to open?

The file may be corrupt, or it may be a format the browser cannot decode natively (TIFF, for example). Re-export it from the app that created it.

Are my files uploaded?

No. The conversion runs on a worker thread inside your tab. You can verify in DevTools → Network: dropping a file produces no request.