Skip to main content

WebP to JPG converter

Convert WEBP images to JPG format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

JPG is the format nothing refuses, which is why this conversion exists. The trade is worth stating plainly: a WebP is decoded and then compressed again by an older codec, so a little quality goes and the file usually gets bigger rather than smaller. Transparency disappears too - the page paints the canvas white before drawing, so a cut-out product shot lands on a white rectangle. For a photograph headed into an upload form or an old editor, none of that matters much; for a transparent logo, it matters a lot.

Key facts about WebP to JPG converter

Key facts about WebP to JPG converter
Codec changeWebP's VP8 intra coding is decoded and the pixels are re-compressed with JPEG's DCT blocks - a second lossy generation.
TransparencyLost to a white fill. The canvas is painted #FFFFFF before your image is drawn, so alpha areas become white and soft edges blend into it.
Size directionUsually upward. WebP is the more efficient codec, so matching its visual quality in JPEG typically costs 20-40 percent more bytes.
Quality slider30 to 100, defaulting to 90. Lower settings make the size gap disappear but stack visible artifacts on top of the ones WebP left.
Animated sourcesOnly the first frame is used; the canvas captures a still, and the JPG has no way to store a sequence anyway.
MetadataNothing is transferred - no EXIF, no XMP, no colour profile. The JPEG is written from the canvas and carries only pixels.
ColourBoth codecs subsample chroma, so a red or magenta edge that already softened in the WebP softens a second time.
Compatibility gainedEvery phone gallery, email client, marketplace uploader, office suite and print service accepts JPG without question.
BatchTwenty files per run at up to 500 MB each; several results are packed into converted-jpg-files.zip.

What happens to your file

All of it happens in this tab: the browser's built-in WebP decoder produces the pixels, a canvas is filled white and then receives the image, and canvas.toBlob with image/jpeg and your quality value writes the result. No endpoint is contacted at any point, which is easy to verify - load the page, go offline, and the conversion still completes. The download link addresses a blob in page memory rather than a file on a server.

About this tool

  1. 1

    Drop in the WebP files

    Only .webp is accepted on this page; anything else is refused with a message before decoding.

  2. 2

    Consider what is behind the image

    If the source has transparency, decide whether a white background is acceptable - it is the only background this conversion can produce.

  3. 3

    Set the quality

    90 keeps the result close to the source. Going lower is only sensible when a size limit forces it, since you are already on a second generation.

  4. 4

    Convert and download

    Use the side-by-side comparison to check edges and flat areas before saving the .jpg or the ZIP.

Specs & compatibility
Input and outputTakes .webp only (image/webp) and returns .jpg with the image/jpeg type; any other extension is refused before decoding.
Conversion pathWEBP to JPG runs in three steps: an <img> element decodes the WebP and passes frame one to the canvas; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/jpeg type returns the finished file.
Browser supportThe WebP side needs Chrome 32, Firefox 65, Edge 18 or Safari 14 to decode, while writing the JPG is just as universal, since every canvas implementation encodes JPEG.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the JPG encode, max-dimension presets from 3840 down to 200 px resize the WEBP first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty WEBP files per run at 500 MB each; one result downloads as a single JPG, several as converted-jpg-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized WEBP fails before any JPG bytes exist.
  • A product photo with a transparent background needs PNG, not JPG - the white fill will show as a box on any coloured page.
  • Expect the JPG to be larger than the WebP at the same visual quality; that is the cost of a format everything can open.
  • If the WebP came from a website and was already heavily compressed, keep the quality high to avoid compounding the damage.
  • For sending photos by email or messaging, downscaling with a preset saves far more than pushing the quality slider down.
  • Uploading an image saved from a website to a form, marketplace or portal that rejects .webp.
  • Opening a downloaded image in older desktop software that has no WebP decoder.
  • Preparing photographs for a print service or photo-book tool that accepts JPG only.
Because WebP is simply better at compression. To reach a comparable appearance, JPEG needs roughly a fifth to a third more data, and the gap is widest on smooth gradients. You can force a smaller file by lowering the quality slider, but you will be adding a second layer of artifacts to an image that already has one.
They become solid white. JPEG has no alpha channel, so the conversion paints the entire canvas white before drawing your image; transparent regions show that white, and semi-transparent edges blend towards it. When the cut-out matters, convert the WebP to PNG instead, which preserves alpha exactly.
A little. Two lossy codecs in sequence means the JPEG encoder is approximating an image that was itself an approximation. At quality 90 the second pass is hard to notice on photographs, but flat areas and sharp graphics show it sooner, and repeating the round trip makes it steadily worse.
Not through this page. The conversion captures only the first frame, because that is what a canvas receives from an image element. Turning an animated WebP into a moving format needs a tool that reads every frame and its delay, then writes them into an animated container.
No. Decoding, the white fill, drawing and JPEG encoding are all browser operations running locally, and the output is a blob: URL created in this tab. The most convincing test is to disconnect from the network after the page has loaded and convert anyway - it works.

Related tools

View all

Need the opposite? Try JPG to WEBP

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy