WebP to JPG Converter

Convert WebP to JPG, with control over quality and what happens to transparency

Something downstream will not take a .webp — a marketplace listing form, a print shop, an email client, an ATS that only accepts JPEG, an older editor, a device that has never heard of the format. JPG is the lowest common denominator of digital images and the thing that always works. This tool re-encodes your WebP files as JPEGs in your browser, with a quality slider so you decide the trade between file size and visual fidelity, and it does one thing to your image that you should know about before you press the button: it flattens transparency onto a white background.

Drop files onto the upload area or click to browse, set the quality, press Convert All, then download. Multiple files at once, up to 50 MB each.

The flattening problem: JPEG has no alpha channel

WebP can store per-pixel transparency. JPEG cannot — not partially, not at all. The format has no way to say "this pixel is see-through", so every pixel in the output must be some opaque colour. Something has to be put behind the transparent parts, and this tool's answer is explicit and predictable: white, #ffffff. Before your image is drawn, the canvas is filled with solid white; the image is then composited on top. Wherever the WebP was transparent, the JPG is white. Wherever the WebP was half-transparent, the JPG is a 50/50 blend of your pixel and white.

For a photograph, none of this matters — photographs are fully opaque, so the white layer is entirely hidden and the output is identical to what you would get either way. For a logo, an icon, a cut-out product shot, a sticker, a signature scan, or a UI element, it matters a great deal, and it is not reversible. A white box is now baked into the pixels.

The quick test: open the WebP in a viewer that shows transparency as a checkerboard. If you see checkerboard, converting to JPG will turn that area white. If the image is solid to the corners, convert freely.

Choosing a quality setting

The slider runs from 10% to 100% and starts at 92%. JPEG quality is not a percentage of anything you can see — it scales the quantization tables that decide how much fine detail the encoder discards. What it means in practice is that the top of the range costs a lot of bytes for very little visible gain, and the bottom of the range saves bytes you will regret.

Content matters more than the number. Photographs of faces, foliage, and texture hide compression well and tolerate 80% comfortably. Screenshots, charts, and anything containing text fall apart much earlier, because JPEG's discrete cosine transform is fundamentally bad at hard edges — it is the reason text in a low-quality JPEG grows a grey ghost around every letter. If your WebP is a screenshot, JPEG is the wrong destination at any quality.

Getting the quality right on the first try

One behaviour to know: files already marked complete are skipped when you press Convert All again. Moving the slider and re-converting will not re-encode a file that already converted — it only picks up files still pending. To try a different quality on the same image, remove that file (or use Clear All) and add it back in.

So the efficient workflow for a large batch is to convert one representative file first, check the reported output size and open the result at full size, and only then add the rest. Each row shows original size, converted size, and the percentage change, which tells you immediately whether your setting is achieving anything. If a photo shows a large size increase, your quality is set too high for the content — you are spending more bytes on JPEG than the WebP encoder spent, which defeats the purpose.

Generation loss: why you convert once, from the best source you have

Both WebP (in its usual lossy mode) and JPEG are lossy. Each throws away detail it judges you will not miss, and neither can put it back. When you convert a lossy WebP to JPEG, you are applying a second, different set of approximations on top of a first — and the second encoder cannot tell the difference between real detail and the first encoder's artifacts, so it faithfully spends bits preserving the damage.

Once is usually invisible at sensible quality. The problem is repetition. Save a JPEG, open it, crop it, save again, mail it, someone re-saves it, and each round compounds. This is why images that have been round-tripped through chat apps and re-saves for years look like they have been through a washing machine.

Three rules that follow from this:

• Convert from the best source you have, not from a copy of a copy. If the original is available as a PNG or a camera file, start there rather than from a WebP that a website already re-compressed.
• Convert last, not first. Do your cropping, resizing, and colour work in a lossless format, and export to JPEG once at the end.
• Keep the WebP originals until you are certain the JPEGs are what you need. The conversion is one-way; there is no path back to the detail you discarded.

What is not a source of loss here: resizing. The conversion preserves the image's exact pixel dimensions, reading them from the decoded image and sizing the canvas to match. Nothing is scaled, cropped, or padded.

What else does not carry across

The conversion runs through the browser's canvas, which deals in pixels. Metadata a WebP might have been carrying — EXIF, ICC colour profile, XMP — is not written into the JPEG. In most cases this is unimportant or actively useful, since it strips any embedded location data before you share a file. It is worth knowing if you were depending on an embedded colour profile for print work, in which case check the output on a calibrated display before sending it to a printer.

Batches, limits, and rough edges

• Many files at once, added by drag-and-drop or the file picker, and you can add more to the list without clearing it. Files convert one at a time so the tab stays responsive.
• 50 MB per file. Anything larger is skipped at the point it is added.
• WebP only. A file is accepted if its MIME type is WebP or its name ends in .webp; everything else is ignored.
• Skipping is silent. Files rejected for size or type disappear without a warning, so count the rows against what you dragged in before converting.
• Download All saves files individually, not as a ZIP. Your browser may prompt before allowing multiple downloads — allow it, then check your Downloads folder before concluding anything failed.
• Names are preserved with the extension swapped: banner.webp becomes banner.jpg.
• Animated WebP yields one frame. A canvas holds a single frame, so an animated source converts to a still JPEG.
• Failures are per-file — a corrupt or truncated image reports its error in its own row and the rest of the batch continues. Truncated downloads and half-finished cloud syncs are the usual culprits; re-fetch the original and retry.

Your files stay on your machine

Everything happens inside the browser tab. Each file is read from disk by the page, decoded by the browser's built-in WebP decoder, drawn to an in-memory canvas, and encoded to JPEG by the browser's own encoder. No image data is sent to this site or to any third party. There is no upload, so there is no server-side copy to be retained, indexed, or deleted — and no privacy policy you have to take on faith.

You can check this directly: open developer tools, watch the Network tab while a conversion runs, and you will see no image leaving. The tool also keeps working with the network disconnected once the page has loaded, which is a reasonable proof on its own. Practically it also means no account, no queue, no per-day limit, and no watermark — and it means the encoding speed depends on your own machine rather than on someone else's server load.

Quick decision guide

• Photograph, no transparency, needs to go somewhere that rejects WebP — this is exactly the job. 85–92% quality.
• Hard file-size ceiling on an upload form — start at 85%, step down, and resize the image first if you are still over. Compressing harder is the worse of the two levers.
• Anything with a transparent background that will not sit on white — convert to PNG instead. JPEG has no alpha channel and no setting here changes that.
• Screenshot, chart, or an image with text — JPEG will ring around the edges. A lossless format is the better destination.
• An asset you will keep editing — do not convert to JPEG yet. Edit losslessly, export to JPEG once at the end.