JPG to WebP Converter

Batch-convert JPEG to WebP with quality and size controls, compare sizes and download a ZIP.

Choose up to 20 JPG images or drop them here

10 MiB per image · 50 MiB per batch · 12 million pixels per image. Files stay in this browser.

Maximum edge

Quality (1–100)

WebP quality follows your browser encoder; some browsers choose lossless at 100. Transparency is retained; a smaller file is not guaranteed. Images are never enlarged. Animated PNG and WebP are rejected; metadata is not retained.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Prepare JPEG photographs as WebP assets with chosen quality and dimensions, measured file sizes and batch ZIP downloads.

How to use it

1Select JPEG photos and choose Original dimensions or a maximum edge.
2Set lossy quality from 1 to 100 and convert to WebP.
3Compare each preview and byte count before downloading the files or ZIP.

Example

Input: 1,600 × 800 JPG; edge 640; quality 90
Output: 640 × 320 lossy WebP

A smaller file is not guaranteed; compare the measured bytes.

What happens to your data

Photographs are converted with the browser's WebP encoder and packaged locally. File names and image contents are not sent to an image-conversion server, and exports disappear when cleared.

Last updated October 2026

Turn JPEG website photos into WebP with a chosen quality and optional maximum edge. Review the actual output size and preview before saving one file or a batch ZIP. This workflow is for preparing photographs before uploading them to a website, product catalog or publishing system that accepts WebP.

Converting to WebP can reduce a photograph's encoded size, but savings are not guaranteed. The starting JPEG, resolution, browser encoder and quality setting all affect the result. A low-quality JPEG can become larger without gaining detail, so the tool reports both sizes instead of assuming every conversion is an improvement.

How it works

The source header must identify JPEG. The converter accepts .jpg and .jpeg names, but a misleading extension does not bypass the signature check. File limits are 10 MiB each, 12 million pixels and 8,192 pixels per side; choose at most 20 images and 50 MiB per batch. A failed image is reported separately, allowing other valid photos to finish.

Quality is a whole number from 1 to 100. It controls the browser's WebP encoder, rather than a percentage of original quality or an exact file-size target. Chromium chooses lossless WebP at quality 100; that behavior is browser-specific, so the setting is not a portable guarantee of exact pixel preservation. Inspect edges, gradients, small text and faces before choosing a final setting. The same number need not produce byte-identical output across browser versions.

Use Original dimensions for a straight format change. A maximum edge scales only photos that are larger than that edge, preserving proportions without cropping or enlarging. For example, a 1,600 × 800 JPEG becomes 640 × 320 at a 640-pixel edge. Reducing dimensions usually changes the visual result more than a small quality adjustment; choose dimensions based on the intended display and its pixel density.

The output MIME type is checked. If the browser falls back to PNG because it cannot encode WebP, the file is rejected instead of being saved under a false .webp extension. Successful images can be downloaded individually or packaged, with distinct names, into a ZIP. Total output is capped at 60 MiB; the archive includes only the successful files.

Canvas conversion keeps decoded image pixels, not the original EXIF, GPS or color-profile metadata. It cannot restore detail already lost in JPEG. Settings changes invalidate old output, and Cancel discards the current run. Save results before navigating away; the page does not retain a conversion history. Your source files and generated images are processed in the browser without upload.

Worked example: Prepare a smaller website photo

Input: 1,600 × 800 JPEG; edge 640; quality 90
Result: 640 × 320 WebP

Output byte size depends on the source and browser; quality 90 is lossy.

Common use cases

Preparing product photos before uploading them to a WebP-compatible store
Reducing a large hero image to a deliberate pixel size
Comparing the byte cost of a JPEG and its converted WebP
Downloading named WebP assets for a static website in one archive

Frequently asked questions

Is JPG to WebP always smaller?＋

No. Compare the displayed input and output byte counts. Photos already compressed strongly as JPEG may not benefit, especially at a high WebP quality setting. Keep the JPEG when the WebP is larger or visibly worse.

Does WebP quality 100 mean lossless?＋

It depends on the browser. Chromium chooses lossless WebP when canvas quality reaches 100, but browser implementations differ. This page does not offer a separate portable lossless switch. Resizing still changes pixels, and JPEG detail already lost is never restored.

Can I choose an exact target size such as 100 KB?＋

No. The controls choose quality and dimensions; actual bytes are measured after conversion. Reduce the maximum edge or quality, convert again and compare. Very detailed images need more bytes than flat images at the same settings.

Why did my output disappear after changing quality?＋

The previous download represented the old settings. Clearing it prevents a stale export from being presented as the new conversion. Press Convert again to generate and inspect an output using the new quality.

Does this change all image links on my website?＋

No. It creates downloadable files only. Upload them to your publishing system and update references there. Check that the destination accepts WebP and that the page actually serves the new image.

Can a WebP recover a low-resolution JPEG?＋

No. Changing format cannot add source detail. The converter does not enlarge small images or apply AI enhancement; it keeps or reduces their decoded pixel dimensions.