WebP to JPG
Convert WebP images to JPG in your browser, animated files included, with a background colour of your choice behind transparent areas.
Drop your files here
.webp · up to 100 MB
How to Convert to JPG
- 1
Drop your WebP files
Up to 100 at once. Static and animated WebP are both read, and so are files that were saved with a .webp name but hold a PNG or an AVIF.
- 2
Pick quality and background colour
Quality runs from 40 to 100. If the image has transparent areas, choose what goes behind them, because JPG cannot store transparency.
- 3
Download the JPGs
One file downloads directly. Several files, or every frame of an animation, arrive as a single ZIP.
Why a WebP will not open in your program
WebP came from Google in 2010 and took a decade to reach broad support. Browsers handle it everywhere now, which is why so many images saved from the web arrive in this format. Plenty of software never caught up, though. Older versions of Office, most photo frames and televisions, many upload forms that check the file type, and a lot of print shops still expect JPG and nothing else. Converting is the shortest way out, and since JPG is the most widely readable image format in existence, the result will open essentially anywhere. The pixels are decoded with the same libwebp code a browser uses, so what you see on the page is what ends up in the JPG.
Transparency, animation and lossless WebP
Three things a WebP can do that a JPG cannot. Transparency has to become a solid colour, and you choose which one; the blend is computed in linear light so soft edges do not pick up a grey fringe. Animation has to lose its timing: you can take just the first frame, which is what most people want when they saved a picture from a page, or split every frame into its own numbered JPG. Frames are composited properly: WebP animations store only the rectangle that changed between frames, so a naive converter that decodes each frame on its own produces torn, half-empty pictures. Finally, a lossless WebP becomes a lossy JPG by definition; if that matters, WebP to PNG keeps every pixel exactly.
Your file stays on your device
The WebP decoder, the animation parser and the JPEG encoder all run inside your browser tab as WebAssembly. Nothing is uploaded, no server sees the image, and closing the tab clears it from memory. That holds for the whole batch, including animations that get split into hundreds of frames.
Frequently asked questions
Why will my WebP not open in some programs?
The format is newer than most desktop software. Browsers support it universally, but older photo viewers, office suites, TV media players and many upload forms only recognise JPG, PNG and GIF. Converting to JPG sidesteps all of that, since JPG is readable by practically everything made in the last thirty years.
What happens to transparent areas?
They get filled with the background colour you pick: white by default, or black, or any custom colour. JPG has no alpha channel, so there is no way to keep transparency. If you need it kept, convert to PNG instead, which stores transparency natively.
Can I get every frame of an animated WebP?
Yes. Switch the animation setting to every frame and each one comes out as its own JPG, numbered in order, packed into a ZIP. Frames are composited against the previous ones first, honouring the disposal and blending flags, so partial-update frames look right rather than half-empty.
Why is the JPG bigger than the WebP was?
Because WebP is a more efficient format; at the same visual quality it is usually 25-35% smaller than JPG. Converting to JPG buys compatibility and costs size. Lowering the quality slider trades some of that back; running the result through Compress Image afterwards is the other option.
Is quality lost during the conversion?
A little, unavoidably. The WebP is decoded to exact pixels, then re-encoded as JPG, and JPG is a lossy format. At quality 90 the difference is invisible on photographs. If the source was a lossless WebP, which is common for logos and screenshots, you are trading exactness for compatibility, and the page says so.
How many files can I convert at once?
Up to 100 files, 500 MB combined. All of them use the same quality and background settings and come back as one ZIP named pulsarkit-webp-to-jpg.zip. A file that fails does not stop the others.
How is this different from converting to PNG?
PNG keeps transparency and keeps every pixel exactly, but the file is typically three to eight times larger. JPG is small and universally readable but flattens transparency and loses a little detail. Pick JPG for photographs and for anywhere that will not accept anything else; pick PNG for logos, icons and anything with transparency you need to keep.
Does the file get uploaded to a server?
No. Everything happens inside your browser through WebAssembly. There is no upload, no account and no stored copy; closing the tab is all the cleanup there is.