JPG to WebP Converter

Converts JPG photos to WebP, which every current browser displays, usually a quarter to two thirds smaller. A 252 KB JPEG saved at quality 90 came back at 76 KB at our default of 80. The conversion runs in your browser, so nothing is uploaded, and you can do five photos per batch.

Last updated

Target Format
jpg ➔ webp
80%
Up to 5 images per batch

How to convert JPG to WebP

01

Drop in up to five JPGs

Drag them onto the panel or tap it to choose. PNG and existing WebP files are accepted too, and come out as WebP.

Tip: Start from the largest, least compressed copy you have. A camera original converts better than a JPG that has already been through a messaging app.
02

Choose a quality

80 is the default and suits most photographs. Product shots that customers zoom into deserve 85 to 90; large background images can go down to 70.

Tip: Above 90 the file grows quickly while the improvement becomes hard to see, and the slider warns you when you cross that line.
03

Process and download

One file downloads directly; several arrive as a ZIP with their original names and a .webp extension.

Tip: Compare one converted photo with its original at full size before converting a whole folder at the same setting.

Why convert JPG to WebP here

Smaller at the same quality

WebP's prediction-based compression stores photographs in fewer bytes than JPG manages: about a quarter to a third fewer at matched quality by Google's measurements, and often far more when the JPG was saved generously.

Displays in every current browser

Chrome, Edge, Firefox and Safari all display WebP, on desktop and on phones. For a website built today, a JPG fallback is rarely needed.

You choose the trade-off

The quality slider runs from 60 to 100. The number is mapped before it reaches the encoder so the top of the range does not waste bytes on detail nobody can see.

Nothing is uploaded

The JPG is decoded and the WebP encoded on your device, inside a Web Worker. Your photos never leave your machine, and the tool works offline once the page has loaded.

Camera metadata stripped

Camera details and any GPS location stored in the JPG's EXIF data are not carried into the WebP. On a public website that is usually a benefit rather than a loss.

Five files per batch

Every photo is fully decoded into memory before it is re-encoded. Five at a time keeps peak memory within what a laptop or phone browser will allow.

Frequently Asked Questions

How much smaller will my photos get?+
It depends on how the JPG was saved. At matched quality, Google measured WebP 25 to 34 percent smaller. Generously saved JPGs shrink much more: our test photo at JPG quality 90 went from 252 KB to 76 KB at WebP quality 80. JPGs that were already heavily compressed shrink less.
Will converting reduce quality?+
Slightly, as any lossy re-encode does, but at quality 80 or above it is very hard to see on a photograph. Avoid repeated conversion, and avoid starting from a JPG that already shows blocky artefacts, because WebP will faithfully keep those too.
Do all browsers support WebP?+
Every current version of Chrome, Edge, Firefox and Safari displays WebP, on desktop and on phones. Safari added it in 2020. Unless you have to support very old Apple devices, you can serve WebP without a JPG fallback.
Should I use WebP or AVIF?+
AVIF is smaller again, typically 20 to 50 percent below WebP, but it is slower to encode and browsers cannot create it, so our AVIF converter uses a server. WebP is the safe, fast default; AVIF earns its place on large hero images where every kilobyte counts.
Do I need to convert before uploading to my website?+
It depends on the platform. WordPress has accepted WebP uploads since version 5.8, so converting first saves space and bandwidth there. Platforms that run images through their own CDN, such as Shopify, already serve WebP to browsers that support it, so converting before uploading gains little.
Are my photos uploaded anywhere?+
No. Decoding and encoding happen in your browser. Open the developer tools, watch the Network tab while you convert, and you will see that no request carries your photos.

Format Comparison

Feature SpecificationJPG to WebP conversionAlternative
Size at matched quality25 to 34 percent smallerBaseline
Our 1200 × 900 test photo76 KB at quality 80252 KB at quality 90
TransparencySupportedNot supported
Browser supportAll current browsersEverything ever made
When compressed hardGoes softGoes blocky

Technical Overview & Specifications

Deep dive into JPG to WebP conversion architecture and processing.

Show Details

Platform Overview

When a website is slow, its photographs are usually the reason, and most of those photographs are JPGs. WebP was designed to replace JPG on the web in particular. Google's published comparison found lossy WebP files 25 to 34 percent smaller than JPGs of the same measured quality, and every browser in current use displays it, Safari included since 2020. On a page with a dozen product photos, that difference is the gap between a page that appears at once and one that fills in piece by piece.

Real conversions often save more than that figure suggests, because many JPGs were saved at a higher quality than anyone needs. Our 252 KB test image had been saved at quality 90; at WebP quality 80 it came back at 76 KB, 70 percent smaller, and looked the same at normal size. The other side of it is that converting a JPG means decoding something already compressed and compressing it again. Done once at a sensible quality, that second pass is invisible. Done repeatedly, or from a JPG that was already squeezed hard, it adds up, so convert from the best copy you have. Everything happens in your browser, five files at a time.

Why WebP beats JPG on photographs

JPG transforms every 8 by 8 block of pixels on its own, so it cannot take advantage of the fact that neighbouring blocks in a photograph usually look alike. Lossy WebP, built on Google's VP8 video codec, predicts each block from the blocks above and to the left that have already been decoded, choosing among several prediction modes, and stores only the difference between the prediction and the real pixels. Differences are smaller numbers than raw pixels, and small numbers compress well. WebP also smooths the block edges that JPG is known for, which is why a heavily compressed WebP goes soft rather than blocky.

Here the JPG is decoded by your browser inside a Web Worker, drawn onto an OffscreenCanvas at full size and encoded to WebP by the browser's built-in encoder at the quality you chose. That quality is passed through a mapping that flattens the top of the range, where WebP would otherwise spend many bytes on detail nobody can see. The browser's encoder does not expose the slower, more exhaustive settings of the command-line libwebp tools, so a careful command-line encode can sometimes shave off a few percent more. For photographs on a web page that difference is rarely worth the extra work.