WebP to JPG Converter

Converts WebP images to JPG, the format every app, printer and upload form accepts. Transparent areas are filled with white rather than black, and you choose the quality, anywhere from 60 to 100. Everything happens in your browser, so nothing is uploaded, and you can convert five files at a time.

Last updated

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

How to convert WebP to JPG

01

Drop in up to five WebP files

Drag them onto the panel or tap it to choose. PNG files are accepted too if you have a mix, and everything comes out as JPG.

Tip: Anything over 25 MB or wider than 8192 pixels is refused straight away, with a message saying which limit it hit.
02

Set the quality

80 is a good default for photographs. Go up to 90 for anything that will be printed or zoomed into, or down towards 70 if the file has to be small.

Tip: If a form gives a size limit in KB, the image compressor finds the highest quality that fits, so you do not have to guess.
03

Process and download

One file downloads directly; several arrive as a single ZIP. Names are kept and the extension becomes .jpg.

Tip: If the original had transparency, look at the result once to check that a white background is what you wanted.

Why convert WebP to JPG here

White behind transparency, not black

JPG has no alpha channel, so transparent areas must become a colour. They become white, and soft edges blend into white, instead of the black box and dark fringe that many canvas-based converters leave.

You choose the quality

The slider runs from 60 to 100 and maps to the encoder's quality setting. Above 90 the file grows quickly for little visible gain, and the slider says so when you get there.

Opens anywhere

JPG is accepted by every operating system, browser, phone, printer and upload form in use. When something refuses a WebP, converting is the dependable fix.

Runs in your browser

The WebP is decoded and the JPG encoded on your own device, in a Web Worker. Nothing is uploaded, and the tool keeps working offline once the page has loaded.

Metadata left behind

EXIF data in the original, including any GPS location, is not copied into the JPG. That is useful when a file is going to strangers, and worth knowing if you rely on camera details.

Five files per batch

Each image is fully decoded into memory before it is encoded, at about four bytes per pixel. Capping the batch at five keeps a phone browser from closing the tab partway through.

Frequently Asked Questions

Why does my JPG have a white background?+
Because JPG cannot store transparency, so the transparent parts of the WebP have to be filled with something. White suits almost every use: documents, listings and most web pages. If you need the transparency itself, convert to PNG instead, which keeps it.
Will converting lose quality?+
A little, because JPG is lossy and the WebP probably was too. At quality 80 or above the difference is very hard to see on a photograph. What to avoid is converting the same image back and forth repeatedly, since each lossy save costs a bit more.
Why is my JPG larger than the WebP was?+
WebP compresses more efficiently than JPG; Google's published measurements put lossy WebP 25 to 34 percent smaller at equal quality. So a JPG of matching quality is usually somewhat bigger. If size matters, lower the quality, or use the image compressor with a target size.
Why won't a WebP file open on my computer?+
Most current software opens WebP, but some older image editors and photo viewers, many print services and a lot of upload forms still do not. Converting to JPG is the quickest fix when you need the file to work somewhere specific today.
What happens to an animated WebP?+
Only the first frame is converted. JPG has no animation, and for an animated file the browser hands the converter a single still image, so the result is a still JPG of how the animation starts.
Is my image uploaded anywhere?+
No. Decoding and encoding both happen inside your browser. You can check by opening the developer tools, watching the Network tab while you convert, and seeing that no request carries your file.

Format Comparison

Feature SpecificationWebP to JPG conversionAlternative
Size at matched qualityBaseline25 to 34 percent smaller, by Google's figures
TransparencyNone, filled with whiteFull alpha channel
Opens inEverythingCurrent browsers and most current apps
Accepted by upload formsNearly alwaysOften refused
AnimationNoYes

Technical Overview & Specifications

Deep dive into WebP to JPG conversion architecture and processing.

Show Details

Platform Overview

Most people who need this did not choose WebP. They saved an image from a website, or an app exported one, and then hit something that refuses it: an application form that accepts JPG and PNG only, an old photo viewer, a print kiosk, an email to someone whose software shows a broken attachment. JPG fixes all of those, because it has been readable by everything for more than thirty years. The price is that a JPG is usually somewhat larger than a WebP of the same visual quality, since WebP's compression is newer and cleverer, and that a JPG cannot be transparent.

Both of those are dealt with here rather than left for you to discover afterwards. Transparent areas are filled with white before the JPG is written, which is what nearly everyone wants, instead of the black that appears when a converter simply discards the alpha channel. The quality slider starts at 80, which for almost any photograph is hard to tell apart from the source, and you can raise it if the file is going to be printed or looked at closely. Decoding and encoding both run in your browser, five files per batch, each up to 25 MB.

What changes between WebP and JPG

The two formats compress in a similar way but come from different decades. JPG splits the image into 8 by 8 blocks and transforms each block on its own. Lossy WebP, built on the VP8 video codec, uses larger blocks and predicts each one from its neighbours before storing only the difference, which is how it reaches the same quality in fewer bytes. Converting from WebP to JPG means decoding the WebP into plain pixels and compressing those pixels again the JPG way. There is no shortcut that maps one format's compressed data onto the other's.

In this tool that happens inside a Web Worker. The WebP is decoded by the browser's own decoder and drawn onto an OffscreenCanvas at its original size. A second canvas is filled with white and the image is drawn over it, which is the step that turns transparency into white rather than black, and that canvas is encoded as JPG at the quality you set. The quality value passes through a mapping that flattens the top of the range, where extra bytes stop buying visible improvement. If there is more than one file, the results are zipped in your browser before the download starts.