WebP to JPG Converter
For the upload box that answers with “unsupported file type”. A .webp goes in, a .jpg comes out, and neither one visits a server.
JPEG has no transparency, so transparent areas are filled with this color.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to convert WebP to JPG
Drop the .webp files in
JPEG is already selected as the output here. Images saved out of a browser are usually WebP now, so a folder full of them is the normal case rather than the exception.
Nudge the quality up rather than down
The slider opens at 75. A WebP has already been through a lossy encoder once, so this is the second pass — around 85 costs a few bytes and keeps that from showing. Read the section below before dragging it the other way.
Check the smooth areas before you take the batch
Open the compare slider on one file and go straight to a sky, a gradient or a flat wall. Stacked compression shows up there first, as banding or faint squares, long before it touches the busy parts of the picture.
Download the JPGs and keep the WebP
Each row has its own download, and a ZIP appears once several are done. The WebP is still the better master: if you need another size later, go back to it rather than to the JPEG.
Trading efficiency for acceptance
The reason is almost never quality
Browsers have read WebP for years; the trouble is everywhere else. Job portals, school and government forms, older content managers, some office and print software and no end of internal tools check uploads against a list of file types written before WebP was common, and simply refuse it. JPEG is the one raster format nothing turns away.
Renaming the file does not work
It is the first thing people try, and it fails in a specific way worth understanding. A format is the bytes inside the file, not the letters after the dot: change .webp to .jpg and the file is still a WebP wearing a false label. A form that checks only the extension may accept the upload, and then the site’s own image processing chokes on it later; anything that actually decodes the file rejects it immediately. Converting rewrites the bytes, which is why it works where renaming does not.
The second encoder cannot see what is already gone
A WebP is not the original picture; it is what its encoder decided to keep. Hand that to a JPEG encoder and everything in it is treated as real detail — including the smoothing and the block edges the first pass introduced — so bits are spent preserving them before any new loss is added on top. The two passes stack instead of cancelling, and no setting on this page brings back what the first one removed.
A transparent WebP turns into a solid rectangle
This one catches people out, because a WebP pulled off a website does not announce whether it has an alpha channel. JPEG has none, so every transparent pixel is composited onto the background colour in the settings — white by default — and what looked like a floating product shot arrives as a product shot in a white box. Set the swatch to the destination’s colour before converting, or send the file to PNG or WebP instead if the cut-out has to survive.
The size can move either way
WebP is the more efficient format, so the JPEG of the same picture at a comparable look is often the larger file. But a WebP that was exported at a high quality, converted here at 75, can come out smaller. There is no rule to apply in advance, which is why each row prints the actual before and after with a smaller or larger label.
When the form also caps the file size
This is where JPEG earns its place over PNG. The same picture as a PNG is usually several times heavier than as a JPEG, so a 2 MB limit that a PNG blows straight past is comfortable for a JPG. Shrink the longest edge first, check the finished size on the row, and only then touch the quality slider. The 100 KB guide runs that order on the 100 KB limit forms ask for most often.
WebP to JPG — frequently asked questions
Why will a website not accept my .webp upload?
Most upload forms validate against a fixed list of file types, and plenty of those lists were written before WebP became common. Nothing on your side changes what the form accepts, so converting the file is the practical fix.
Can I just rename the .webp to .jpg?
No. The extension is a label, not the format — the bytes inside are still a WebP, so anything that genuinely reads the image will fail on it, sometimes after the upload appeared to succeed. The conversion here decodes the picture and writes real JPEG bytes, which is the difference.
Where did the .webp on my computer come from?
Almost always from saving an image out of a browser. Sites serve WebP to save bandwidth, and “save image as” keeps whatever format the site sent — which is how a perfectly ordinary picture lands in your downloads folder as something your other software will not open.
Does the JPG look worse than the WebP?
A little, since it is a lossy file written from a lossy source. At quality 85 the difference is hard to find in a photograph. What it will never do is look better — converting cannot restore detail the WebP already discarded.
My WebP has a transparent background. What happens to it?
It gets filled in. JPEG has no alpha channel, so transparent pixels are painted with the background colour in the settings — white unless you choose another one before converting.
Can I convert an animated WebP?
Not as an animation. A JPEG holds a single image, so what comes out is one still picture with the motion gone. If the movement matters, keep the WebP or build a GIF from the original source instead.
Would PNG be the better target than JPG?
For a screenshot, a diagram or anything with text in it, yes — PNG is lossless and adds no second round of blur. The catch is weight: a PNG made from a WebP is usually several times bigger, so when there is an upload limit in play, the JPG is the one that gets through.
The form rejects my JPG for being too large. What now?
Set the resize control to fit the longest edge to 2048 or 1024 px and convert again — a form that caps the size rarely needs the full resolution anyway. The row shows the finished byte count, so you can see whether you are under the limit before you go back to the upload page.