Why is the JPG larger than the WebP?

WebP compresses photos more efficiently than JPG; Google, which developed it, reports lossy WebP files 25 to 34% smaller than JPG at the same measured quality. Converting back to JPG at a similar quality therefore needs more bytes. Lower the quality if the size matters.

What happens to an animated WebP?

It becomes a still JPG of its first frame, because JPG cannot store animations. The list marks such files with "only the first frame was converted", so you can tell them apart from still pictures.

Does converting WebP to JPG lose quality?

A little. JPG compresses with loss, so the picture is compressed a second time. At quality 90 the difference is hard to see; at low qualities blocks and colour fringes appear.

Can I convert WebP to PNG instead?

Yes. Choose PNG under Convert to. PNG keeps transparency and adds no further loss, but for photos the file is much larger, about ten times the WebP in the example above.

Are my WebP files uploaded for the conversion?

No. The WebP is decoded and the JPG written by your own browser; no server takes part in the conversion. When advertising is enabled and permitted, the page also loads third-party advertising scripts; the privacy policy explains this.

Convert WebP to JPG

Turn WebP pictures that a program, form or printer does not accept into JPG files. Your browser does the work on your device; the pictures are not uploaded to our servers.

Your files are processed in this browser. They are not uploaded to our servers.

Choose images

No files selected yet.

JPG, PNG, WebP, AVIF, GIF, BMP or SVG, up to 50 MB each. You can also drop images here.

No result yet

Choose files and start. The result appears here.

What this tool does

Many websites deliver pictures as WebP because the files are small, so a picture saved from the web often ends in .webp. Older programs, some upload forms and some print services only take JPG. The tool writes each WebP as a JPG with the same width and height in pixels.

It handles the two cases where WebP and JPG differ: transparent areas get a colour you choose, and an animated WebP becomes a still picture of its first frame, marked as such in the list. The page also reads PNG, AVIF, GIF, BMP, SVG and JPG files.

How to use it

Choose the WebP files, or drop them on the marked area.
Leave Convert to at JPG. PNG is also offered if you need a lossless copy.
Set the quality. 90 is preselected; the example below shows how the size changes with it.
If the pictures have transparent areas, choose their colour under Background for transparent areas. White is preselected.
Start, then download single files from the list or all of them as one ZIP archive.

How the conversion works

WebP is specified in RFC 9649. A WebP file holds either lossy data (VP8), lossless data (VP8L) or, for animations, a sequence of frames, and it may have an opacity channel. Your browser decodes the file to pixels, and its JPG encoder writes them again at the quality you set, from 1 to 100.

A lossy WebP has already dropped detail when it was made. Converting it to JPG cannot bring that detail back and adds a second round of compression; at quality 90 the second round is hard to see. Converting to PNG adds no further loss but gives much larger files.

For animations, the HTML standard tells browsers to use the default image or, if there is none, the first frame when a picture is decoded or drawn this way. So an animated WebP becomes a JPG of its first frame, and the list says "only the first frame was converted". JPG cannot store animations; for moving pictures a video or GIF converter is needed.

Worked example

A camera photo of 3000 × 2002 pixels was saved as a lossy WebP of 945,324 bytes (with the cwebp encoder at its quality 80). Converted in Chrome, it became the following JPG files:

The same WebP photo converted to JPG in Chrome, by quality
Quality	JPG size	Compared with the WebP
100	5,842,920 bytes	6.18 times as large
90	1,593,352 bytes	1.69 times as large
80	1,108,806 bytes	1.17 times as large
70	888,740 bytes	0.94 times
60	746,340 bytes	0.79 times
PNG (lossless)	10,186,386 bytes	10.8 times as large

Each conversion took under a second and a half. In Safari the JPG at quality 90 was 2,294,137 bytes, because its encoder works differently. For most uses, quality 80 to 90 gives a JPG that looks the same as the WebP.

Common mistakes

Expecting an animated WebP to stay animated. JPG holds one picture; only the first frame is kept.
Choosing quality 100 "to be safe". In the example the file became 3.7 times as large as at 90, without regaining any detail the WebP had lost.
Converting a WebP sticker or logo with transparency and forgetting the background. Choose the colour of the place where the picture will be used.
Renaming picture.webp to picture.jpg. The content stays WebP, and programs that cannot read WebP still fail.

Frequently asked questions

Why is the JPG larger than the WebP?: WebP compresses photos more efficiently than JPG; Google, which developed it, reports lossy WebP files 25 to 34% smaller than JPG at the same measured quality. Converting back to JPG at a similar quality therefore needs more bytes. Lower the quality if the size matters.
What happens to an animated WebP?: It becomes a still JPG of its first frame, because JPG cannot store animations. The list marks such files with "only the first frame was converted", so you can tell them apart from still pictures.
Does converting WebP to JPG lose quality?: A little. JPG compresses with loss, so the picture is compressed a second time. At quality 90 the difference is hard to see; at low qualities blocks and colour fringes appear.
Can I convert WebP to PNG instead?: Yes. Choose PNG under Convert to. PNG keeps transparency and adds no further loss, but for photos the file is much larger, about ten times the WebP in the example above.
Are my WebP files uploaded for the conversion?: No. The WebP is decoded and the JPG written by your own browser; no server takes part in the conversion. When advertising is enabled and permitted, the page also loads third-party advertising scripts; the privacy policy explains this.

Last updated: September 29, 2026