Convert WebP to JPG
You saved an image from a website and got a file ending in .webp that your photo editor, your printing service, or the form you are filling in refuses to accept. This converts it to an ordinary JPG, in batches. It also explains where WebP files come from, because knowing that makes them much less annoying.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your WEBP file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Converts WebP to universally accepted JPG
- Handles transparency with a chosen background color
- Batch conversion with ZIP download
- Adjustable quality
- No account and no watermark
How to use WebP to JPG
- 1
Add the WebP files
Drop them in. Files that are actually a different format despite the name are detected and converted anyway, with a note saying so.
- 2
Choose a background color if needed
WebP can hold transparency and JPG cannot, so any transparent area is painted before encoding. White is the default.
- 3
Set the quality
The default of 90 percent is a good match for the visual quality of a typical web WebP. Higher settings mostly add file size.
- 4
Save the JPGs
Download individually, or take the whole batch as one ZIP file.
How it works
The browser decodes the WebP into pixels using the same decoder it uses to display WebP images on any web page. Those pixels are composited over a solid background color if the source had any transparency, and re-encoded as JPEG.
The decode is exact — WebP's own decoder returns the pixels the file describes, with nothing approximated on the way in. All of the loss in this conversion happens on the JPEG side.
One consequence worth knowing: what you get is what the WebP contains, not what the original photographer had. Everything WebP's compression discarded is already gone before this tool sees the image, and JPEG then makes its own approximations on top. There is no way around that other than starting from the original.
Where WebP files come from
Almost always from saving an image off a web page. Sites serve WebP to browsers that support it, and "Save image as" hands you the file that was actually delivered rather than converting it back to something familiar. Right-clicking a photo on a shopping site, a news article, or a social platform and getting a .webp is the normal outcome now.
The second source is screenshot and capture tools, several of which now default to WebP for the smaller files.
The third is content management systems that convert uploads automatically. If you uploaded a JPG and later downloaded it back as WebP, this is why.
Choosing between JPG and PNG as the destination
If the image is a photograph and has no transparency, JPG is the right choice and this is the right page.
If the image has transparency you need to keep — a logo, an icon, a sticker, a product cutout — JPG cannot hold it and converting here will fill it with a solid color permanently. Use the WebP to PNG converter instead.
If the image is a diagram, a chart, or a screenshot of an interface, PNG will usually be both smaller and sharper than JPG, so it is the better destination even without transparency.
Examples
An image saved from a shopping site
The JPG is larger, which is the expected direction. WebP was chosen by that website precisely because it is more efficient, so converting away from it costs the saving back. You are trading file size for the ability to open it in anything.
A WebP sticker with a transparent edge
The soft transparent edge is now a hard white one. If this sticker is going onto a white page nobody will notice; onto anything else it will show as a white square. That is a JPG limitation rather than a conversion error, and the WebP to PNG converter is the right tool when the transparency matters.
Frequently asked questions
Why do websites give me WebP files at all?
Because WebP images are typically a quarter to a third smaller than JPEG at the same visual quality, which makes pages load faster and cuts bandwidth costs. Google developed the format and search rankings reward fast pages, so adoption has been rapid. The result is that saving any image from a modern site frequently gives you a format that plenty of desktop software still does not open.
Does converting WebP to JPG lose quality?
A little, yes. Both formats are lossy, so decoding one and encoding the other means two rounds of approximation rather than one. At the default 90 percent quality the additional loss is very hard to see. It is real though, which is why keeping the WebP as your archive copy and converting only the working copy is worth doing where possible.
What still refuses to open WebP in practice?
Older versions of Photoshop without a plugin, many photo printing and canvas-printing services, a good number of government and job application upload forms, some email clients when displaying attachments inline, older Office versions, and a variety of embedded devices and digital photo frames. Web browsers themselves have supported it universally for years — the gap is almost entirely in desktop and institutional software.
Can it convert an animated WebP?
Only the first frame. Animated WebP is a container holding a sequence, and JPG has no way to represent more than one image, so the animation cannot survive in any form. If you need the animation, converting to GIF or MP4 is the relevant operation and this is not the tool for it.
Is the conversion done on your servers?
No. Your browser already contains a WebP decoder and a JPEG encoder, because it needs both to display and save images normally. This page simply uses them. The file is read from your disk into the tab, converted, and written back out, with no network request involved at any point.