How to use WebP to JPG
- Choose a WebP image.
- Set JPG quality and background colour.
- Convert and download the JPG.
Useful to know
Use a high quality setting for photos you plan to edit again.
How to convert a WebP file to a JPG
- Drop in the .webp you saved from a page or received as a download. One file only, and it stays on this device. Anything over 25 MB, or over 40 megapixels once decoded, is refused.
- Adjust Quality if 82 is the wrong encode for this picture. The box allows 10 to 100, and it affects only the JPG.
- Open Background colour when you can see through parts of the WebP. White, #ffffff, replaces the empty areas, because a JPG has no alpha channel.
- Press Convert to JPEG. Check the still preview, especially logo edges, then save the download. The WebP remains the file that still has the animation or the empty background, if it had either.
Why a normal-looking photo arrives as a WebP
WebP is an image format Google published in 2010, taken from the still-image coding inside the VP8 video codec. A WebP can be lossy, in the same family of idea as a JPG, or lossless. It can include a transparent background, and it can store an animation of several frames in one file. Current browsers decode those variants. A wide stretch of desktop software still cannot, which is why a picture that looked fine on a web page becomes a closed file the moment it lands in Downloads.
Sites send WebP to ship fewer bytes. A browser that can show the format says so when it requests the image. The server, or the image host in front of the server, then sends WebP instead of the JPG or PNG it keeps as the master. Google does this on many of its own pages and image hosts. Shops, news sites and blogs do it too, because images are often the heaviest part of a page and a lighter image is one of the practical ways to improve Largest Contentful Paint. Google’s published comparison put lossy WebP photographs about 25–34% smaller than JPEG at a similar SSIM score. That number belongs to those tests. This converter does not apply it to your file. It reports the JPG it actually encoded.
The download is the awkward half of that arrangement. Right-click a picture in Chrome, Edge or Firefox and choose Save image as, and the browser writes the bytes it received. When those bytes were WebP, the file ends in .webp even though the page looked like an ordinary photograph. Changing the extension to .jpg leaves a WebP container with a misleading name. An app that only understands JPG will refuse it or show a broken thumbnail. This page decodes the WebP and writes a real JPG.
Where that WebP has to become a JPG
Use a JPG when the destination has asked for one, or when it has already failed on the WebP. Older copies of Word, PowerPoint and Outlook are a regular case. Current Microsoft 365 on an updated PC can often insert a WebP. Office 2016, Office 2019 and many work machines that stay on a fixed release still show an unsupported format or a blank picture. A JPG insert is the file those machines open. The same gap shows up in older Paint, the classic Windows Photo Viewer, and Photoshop from before version 23.2 in 2022, which needed a separate plug-in. Current Photoshop opens WebP on its own. If your editor already does, you may not need a conversion.
Upload forms are the other everyday stop. Job portals, school systems, visa-photo pages and some marketplaces list jpg, jpeg and png, and they reject a .webp even when the picture is under the size cap. Printing works the same way. A high-street lab and most home photo printers expect JPEG. WhatsApp is a separate quirk. Stickers are a special small animated WebP that the app creates itself. A photograph saved from a website is not a sticker. On many phones the photo picker will not offer that .webp as a picture for the thread, and sending it as a document shares a file rather than a photo people see inline. Make a JPG, then read the WhatsApp size guide if the chat compresses the attachment again after you send it.
If the picture is already a JPG and the only problem is its weight, open the image compressor and skip a format change. If the form also states a pixel size, set that size on the image resizer and bring the smaller WebP back here, so the JPG is not encoding pixels the form will discard.
Lossy WebP, lossless WebP, and the quality field
This page does not label the WebP mode you opened. Both modes become pixels, and the button then writes a JPG. That JPG is always a fresh lossy encode. The quality box accepts 10 through 100. A fresh visit shows 82, and the number applies only to the JPG.
A lossy WebP has already dropped some texture. The JPG cannot put that texture back. The quality number decides how much further this encode may go. 82 is a sensible first encode when the JPG will be viewed on a screen. Move into the nineties if the JPG will be printed or opened in an editor afterwards. Go lower only after you have looked at the preview and you need a lighter attachment. Values near the bottom of the range block up skies, walls and small type. Values near 100 add a lot of bytes, and photographs seldom show a difference worth that extra weight. Nothing here aims at an exact kilobyte count. If the form states one, convert on this page and compress the download.
A lossless WebP is a different start. Its edges and flat colour are still intact. A JPG spends that precision. Lettering, a screen capture or a diagram picks up fringes and blocks, and a modest quality number makes that obvious. When the next app can take a PNG, use the WebP to PNG converter and keep the WebP as well. Send a JPG of a lossless graphic only when the destination refuses every other type, and zoom the preview until the lettering is easy to read before you send the file.
A see-through WebP is composited onto a colour
The JPG container has nowhere to put an alpha value. A logo, a sticker or a product with empty space around it leaves this page as a solid rectangle. The workspace paints the chosen colour across the whole canvas, then draws the decoded WebP over that paint. Empty areas take the colour. Semi-clear areas mix with it, which is ordinary compositing onto the colour underneath. A soft shadow therefore becomes a tinted shadow, and the tint is ordinary image data from then on.
White is the starting value, written as #ffffff. Leave it when the JPG will sit on paper, a CV or a marketplace frame that expects white. Switch it when the artwork was drawn to float on a brand colour. A navy header with a white-backed mark shows a pale outline around the shape. Set the control to that navy, convert, and compare the result with a similar swatch. The checkerboard behind the original WebP is a preview device so the empty areas are visible. That pattern is display-only and never enters the JPG.
Nothing else on this site can recover those empty areas from the JPG afterwards. If the empty background is the asset, switch to the PNG conversion and hold on to the WebP. This page does not alter the file you selected.
An animated WebP becomes the first frame
The workspace asks the browser to decode the file on the same still-image path it uses for a JPG or a PNG. For an animated WebP that decode is a single frame. In current Chrome, Edge and Firefox it is the first frame. Later frames are not read, not played and not packed into the JPG. A JPG could not hold the loop even if they were. You get one still, with the width and height of that decoded frame.
That still can look unfinished when the animation was built as patches. Some files store a complete picture in the first frame. Others store a small change that only makes sense on top of the frames before it, and the rest of the canvas is empty. This page does not walk the loop or composite it into a finished picture. If the preview looks like a fragment, the motion lives in the WebP and a still JPG was the wrong export. Keep the WebP for a browser that can play it. Image Cosmos does not write a GIF or a video from these frames.
What to expect from the file size
A lossy photograph that was already WebP often comes out a similar size or larger as a JPG around the default quality. WebP was the compact file the site chose to send. A JPG is the compatible file, and compatibility is allowed to cost bytes. A lossless graphic can go either way. A moderate JPG quality may shrink it, and the edges pay for that. Read the size printed beside the result. Two browsers can encode the same canvas to JPG files that are not identical, so a ratio quoted from somewhere else is a poor promise.
The workspace takes a single file. Anything over 25 MB, or a decode over 40 megapixels, stops rather than trying to freeze the tab. Several WebP files means several separate runs. There is no zip. Decode, the colour fill and the JPG encode all happen in the browser, and the picture is not posted to Image Cosmos. Reload or leave the page and the temporary link disappears. If the pixel size is wrong, change it on the WebP and run the conversion again. Saving the new JPG a second time can soften it further.
| Job in front of you | The WebP you saved | The JPG this page writes |
|---|---|---|
| A photo a form will accept | Often rejected when the allow-list is JPG and PNG only. | A JPG at the quality you set. The result panel shows the real size. |
| A logo with a clear background | Alpha can be present in a lossy WebP and in a lossless one. | Empty pixels take the colour you set. The control opens on white, #ffffff. |
| An animated WebP | Plays in a browser. Several frames, one file. | One still of the first frame the browser decodes. Later frames are left out. |
| A lossless graphic | Sharp edges, and often already a compact file. | A lossy JPG. Edges can soften. The file may shrink or grow. |
| A lossy photograph | Already a delivery file, usually lighter than an older JPG of the same scene. | Another lossy encode. Detail the WebP discarded stays discarded. The size is often similar or larger. |
Making a WebP on purpose, for a site you control, is the other direction. JPG to WebP and PNG to WebP do that job. A PNG that already has a transparent background, and that a form will only take as JPG, belongs on the PNG to JPG page. These conversions change the container. They leave any earlier loss where it already is.
Related image tools
Frequently asked questions
Why does a right-click in Chrome download a WebP?
Chrome saves the bytes the site actually sent. Many sites, including a lot of Google pages, send WebP when the browser says it can display it, because the WebP is smaller than the JPG they keep behind the scenes. The picture on the page can look like an ordinary photo. Save image as still writes a .webp. Renaming that file to .jpg leaves the contents as WebP, so older software still cannot open it. Convert it when you need a real JPG.
Why do Word, PowerPoint and older Outlook refuse a WebP?
Plenty of Office installs predate WebP. An up-to-date Microsoft 365 on Windows can often insert one. Office 2016, Office 2019 and many workplace PCs on a fixed version still cannot, and the picture fails or shows as a blank box. Make a JPG on this page and insert that. If the slide needs the logo’s clear background, make a PNG instead. Nearly every Office version can place a PNG.
Can a photo lab or a WhatsApp chat use the WebP as it is?
A lab and a home photo printer usually want JPEG. WhatsApp stickers are a special small animated WebP that WhatsApp creates. A photograph you saved from the web is not a sticker. On many phones the photo picker will not drop that .webp into the thread as a picture, and sending it as a document shares a file rather than a photo people see inline. Convert to JPG first. If the chat then squeezes the attachment, the WhatsApp size guide explains that second step.
Does the quality setting treat a lossless WebP differently from a lossy one?
The slider always controls the new JPG, from 10 to 100, starting at 82. This page does not detect which WebP mode you opened. On a lossy photo the fine detail is already reduced, and the slider decides how much further the JPG may go. On a lossless logo or screenshot the slider is the first time those edges are discarded, so a low number does more obvious damage. There is no kilobyte target on this page.
Why has my transparent logo gained a solid background?
A JPG is a flat picture. Empty areas in the WebP are replaced by the colour in the background control, which opens on white (#ffffff). Semi-clear pixels are mixed with that same colour, so a feathered edge picks up a tint. Point the control at the page colour the logo will sit on if white is wrong, and look at the result before you download. The WebP file is not edited. Use the PNG conversion when the empty background has to survive.
Will an animated WebP stay animated as a JPG?
No. The browser decodes one frame. In current Chrome, Edge and Firefox that frame is the first frame, and the JPG is a still of it. Later frames are not read and JPG cannot hold an animation anyway. If the first frame looks like a fragment, the loop was stored as partial updates and this page does not walk the frames to composite them. Keep the WebP when the motion matters.
How large will the JPG be compared with the WebP?
A lossy photo that was already WebP is often a similar size or larger as a JPG at the default quality, because the WebP was the compact delivery file. A lossless graphic may shrink at a moderate quality and look worse around letters and hard edges. The result panel prints the real size. If a form then names a kilobyte cap, compress the JPG. Run that from the WebP again if the first JPG is wrong, rather than re-saving the JPG.