Skip to content
HandfulTools

How to convert WebP to JPG (or PNG)

Why images saved from websites end up as .webp, what a JPG does to transparency and quality, and how to convert one in your browser or your usual software.

· 6 min read

Converting a WebP to JPG decodes the picture back to plain pixels and re-encodes those pixels with JPEG compression. Nothing is renamed and nothing is repackaged: a new, different file is written. That has two consequences worth knowing before you start — a JPEG cannot hold transparency, and JPEG is lossy, so the result is a fresh approximation of the image rather than a copy of it.

The quickest route here: open WebP to JPG, drop one or several .webp files, set the Quality slider (it runs from 40% to 100% and starts at 90%), then click Convert to JPG. Each file keeps its name with a .jpg extension, and files up to 50 MB are accepted. The decoding and re-encoding happen in your browser, so the pictures stay on your device. If the image has a transparent background you want to keep, use WebP to PNG instead.

The routes that actually work

Route Good for Watch out for
A browser tool like this one Any device, several files at once, nothing to install Large batches depend on your device's memory
Your system's own viewer (Preview, Photos) One file, no download Only on versions recent enough to decode WebP
An image editor (Photoshop, GIMP, Photopea) You were going to retouch the image anyway Opening an editor for a format change is slow
The command line (ImageMagick, dwebp) Hundreds of files, scripts, servers Installation, and a build with WebP support
Squoosh Comparing quality settings side by side One image at a time

Platform by platform

On macOS, recent versions decode WebP system-wide: double-click the file, then in Preview use File → Export, set Format to JPEG and drag the Quality slider. Older macOS versions show the file as a blank document and need a converter.

On Windows, recent builds of the Photos app and Paint open WebP. In Paint, File → Save as → JPEG picture does the conversion. If Windows offers to open the file in a browser instead, the build is too old and a tool is the shorter path.

On iPhone and iPad, recent iOS versions have a converter hidden in the Files app: save the image to Files, long-press it, then choose Quick Actions → Convert Image and pick JPEG and an image size. Photos itself has no format menu.

On Android, there is no system-wide image converter. Behaviour depends on the gallery app you have; opening the file in Google Photos, making any small edit and choosing Save copy generally writes a JPEG, but it also re-crops and re-compresses in ways you did not ask for.

In Photoshop, WebP has been read and written natively since the 2022 releases (File → Open, then File → Save a Copy with JPEG selected). Older versions need a plugin. GIMP has imported and exported WebP since 2.10: File → Export As, type a name ending in .jpg, then set the quality in the dialog that follows. Photopea runs in a browser and does the same job with a Photoshop-like interface.

With ImageMagick installed, magick photo.webp photo.jpg converts one file and magick mogrify -format jpg *.webp converts a folder. Google's own dwebp photo.webp -o photo.png decodes to PNG when you want the lossless route. Squoosh is the tool to reach for when you want to see what a quality setting costs before committing to it.

What converting to JPG does to your file

  • Transparency disappears. JPEG has no alpha channel. Our converter draws the image onto a white background first, so transparent areas come out pure white — not grey, and not the colour of the page you saved the image from. If that is wrong for you, convert to PNG.
  • Animation is lost. An animated WebP holds a sequence of frames; JPEG and PNG hold one picture. Only the first frame survives.
  • The pixels are re-encoded. If the WebP was lossy, you are compressing an already-compressed picture: the two sets of artefacts stack up. This is generation loss, and it is why you should keep the original WebP if there is any chance you will need to convert it again.
  • A lossless WebP loses more than a lossy one. WebP has two modes — lossy, and a lossless mode used for logos, screenshots and flat graphics. Converting a lossless WebP to JPEG throws away detail that was previously exact. PNG is the right target for those files.
  • The file often gets bigger. WebP generally compresses more efficiently than JPEG at the same visual quality, so the same picture frequently weighs more as a JPG. That is not a fault in the conversion.
  • Dimensions are unchanged. Conversion never resizes. A WebP can be at most 16 383 pixels on a side; JPEG allows far more, so nothing is ever clipped going in this direction.

Check whether you need to convert at all

WebP is no longer an exotic format. Every current browser displays it, most content management systems accept it as an upload (WordPress has done since version 5.8), and modern versions of macOS and Windows open it. The conversion is worth doing when the file has to leave that world: an upload form whose accepted-formats list stops at "JPG, PNG", a print service, a marketplace listing, an older piece of software on a work machine, or a colleague on a computer that has not been updated in a while.

Common problems, and what they mean

The background turned solid white. The original had a transparent background and JPEG cannot store one. Convert with WebP to PNG instead, which keeps the alpha channel intact.

The JPG is heavier than the WebP it came from. Expected, for the reason above. Lower the Quality slider a few notches, or run the result through Compress Image. Around 80% is usually indistinguishable from 90% on a photograph.

The picture looks blotchy around text or sharp lines. JPEG spreads detail across 8×8 pixel blocks and struggles with hard edges. For screenshots, charts, logos and anything with lettering, PNG is the correct format, not a higher JPEG quality.

I renamed the file to .jpg and the form still rejects it. Renaming changes nothing inside the file. The bytes still begin with a RIFF/WEBP header, and any form that checks properly will still see a WebP. A real conversion rewrites the contents.

The animated image became a still. Only the first frame is kept. To keep the movement, you need a GIF or a video file, which this converter does not produce.

Nothing happens with a very large batch. Everything runs in your browser's memory. Convert in smaller groups, or reduce the dimensions first with Resize Image.

Questions people ask

Why does my browser save images as .webp? Because that is what the site sent. "Save image as" writes the exact file the server delivered, and most sites now serve WebP because it loads faster.

Does converting improve quality? No. Conversion can only preserve or lose detail, never add it. A small or blurry WebP gives a small or blurry JPG.

JPG or PNG? JPG for photographs and for forms that demand it. PNG for transparency, screenshots, logos and anything containing text. Image Converter also writes BMP and ICO if you need those.

Are my images uploaded anywhere? No. Decoding and re-encoding both happen in the page, on your device.

Can I convert back to WebP later? Yes, with Image Converter — but the detail lost in the JPEG step does not come back. Convert from the original whenever you still have it.

Next steps

Tools used in this guide

← All guides