Free · no sign-upAny number of filesNothing uploaded

WebP to JPG

Turn a WebP into a JPG that every app on your machine will actually open. Your browser can already read the file, so the conversion happens here on your own device with no upload and no waiting.

Works in every browser, including SafariA whole folder at once, saved as one ZIPQuality under your control, not fixed at one settingNo file count, no watermark, no account
  1. Drop the WebP files inOne, or a folder's worth. Nothing is uploaded, so nothing waits.
  2. JPG is already pickedSet the quality if you want a smaller file than the default 85.
  3. Save one, or allA single JPG, or the whole batch as a ZIP.

Drop images here, or click to choose

Drop WebP files here. As many at once as you like.

Free · no sign-up · nothing uploaded. Your files are decoded and re-encoded on your own device, so a photo with a face or a location in it never leaves the machine.

How to convert WebP to JPG

  1. Drop your WebP files in

    One, or a folder of them. Nothing is uploaded, so a large batch starts converting immediately rather than after a wait.

  2. JPG is already selected

    The quality slider sits at 85, which is where most photographs stop showing a visible difference. Move it if you want a smaller file.

  3. Save one, or the batch

    Each card shows the new size before you commit. A single file downloads on its own, several arrive as a ZIP.

Why this one works in every browser

Reading an image format and writing it are two separate features, and browsers ship them separately. Every current browser can read a WebP, because that is what makes the format useful on the web at all. Writing one is rarer: Chrome and Edge can, Safari cannot.

WebP to JPG only needs the half that is universal. The WebP is decoded by the browser's own reader, and the pixels are written back out as JPG, which every browser has been able to write for twenty years. So this page behaves the same on Chrome, Edge, Firefox and Safari, on a desktop or a phone. The conversion that gets awkward is the other direction, and that is covered on the image converter page.

Where WebP files come from

Almost always from saving a picture off a web page. Sites serve WebP because it is smaller, and since about 2020 they have been able to serve it to nearly everyone. So you right-click, choose Save image as, and get a file your own computer then declines to open. Nothing has gone wrong. The site made a sensible choice for its bandwidth and you inherited the file.

The same thing arrives through screenshots on some Android builds, through images pulled out of a CMS, and through design handoffs where the exporter defaulted to WebP. If you are being asked for a JPG by a print shop, a marketplace listing or an old bit of company software, this page is the shortest route between the two.

What the conversion actually does to the picture

It decodes and re-encodes, which has one consequence worth stating plainly. WebP is a lossy format, and so is JPG, so the picture goes through a second round of throwing detail away. The first round already happened before you ever saw the file. This one is small at quality 85 and invisible on most photographs, but it is not nothing, and it is not reversible.

If you have any route to the original, use it. Converting from the source beats converting from a copy that has already been squeezed once. Where the WebP is all you have, which is the normal case, quality 85 to 92 is the range where the second pass costs you very little and the file stays a sensible size.

Two other things change. Transparency is lost, because JPG has no alpha channel: a WebP with see-through areas comes out with white behind them, chosen deliberately since browsers left to themselves fill that space with black. And metadata is dropped, so any EXIF, colour profile or GPS tag attached to the WebP is not carried across. For a picture going onto the public web, losing the location tag is the point.

If you need the transparency kept

Convert to PNG instead. PNG holds an alpha channel, loses nothing on the way through, and every piece of software that refuses WebP will happily open a PNG. The WebP to PNG page is the same tool with that format already selected. The trade is size: a photograph saved as PNG can be several times larger than the WebP, because PNG throws nothing away at all.

Frequently asked questions

Why will my software not open a WebP file?

Because it was written before WebP mattered, or it decided not to bother. WebP came from Google in 2010 and only reached majority browser support around 2020, so anything older than that has no reason to know it exists. Photoshop needed a plugin until version 23.2. Plenty of desktop apps, print shops, CMS uploaders and photo frames still refuse it outright. Your browser is the one piece of software on the machine guaranteed to read one, which is why converting it here works when nothing else will.

Will the JPG be bigger than the WebP it came from?

Usually, and often by a lot. WebP exists because it beats JPG at the same visible quality, typically by 25 to 35% on a photograph. Converting undoes that advantage, so a 180 KB WebP commonly lands somewhere around 250 KB as a JPG. Every card here shows the exact change before you save, so you can drop the quality slider a few points if the size matters more to you than the last of the detail.

What happens to an animated WebP?

You get the first frame and nothing else. WebP can hold an animation in the way GIF does, but JPG holds exactly one still picture and has no concept of a second one. So the conversion keeps frame one and the movement is gone, with no warning from the format itself because nothing has gone wrong as far as JPG is concerned. If the animation is the part you want, keep the WebP or look for a GIF or MP4 of it instead.

move openesc close