# WebP to JPG > Convert WebP to JPG locally for software that will not open WebP. In the measured sample the JPG came out 8.7% larger, and transparency is flattened. - URL: https://bytescope.dev/en/image-convert/webp-to-jpg/ - Locale: en · Also: [ja](https://bytescope.dev/ja/image-convert/webp-to-jpg.md) · [zh-Hant](https://bytescope.dev/zh-Hant/image-convert/webp-to-jpg.md) - Runs: Your files never leave your browser — all processing is local. - Requires: Any modern browser (Chrome, Edge, Firefox, Safari), desktop and mobile. - Updated: 2026-09-08 ## What it does ### What a WebP loses on the way to JPG Transparency goes first. The target has no alpha channel, so a sticker, a logo or a cut-out product shot is composited onto the background color selected in the settings above, and the converter warns you as soon as it finds alpha to flatten. The result is a rectangle: the object now sits on solid white, or on whichever color you picked, and the cut-out cannot be reconstructed afterwards. Semi-transparent pixels — the soft edge of a shadow, a faded watermark — are blended into that color rather than clipped, so the edge looks correct against that one background and wrong against any other. Animation goes next. A multi-frame source is detected by frame count, and with this target the converter keeps the first frame, closes the decoder and warns that only one frame was converted. Frame delays and the loop count have no equivalent in a still format. Choosing GIF as the target instead preserves the whole animation, and keeping the original format obviously preserves it too. Then comes the usual toll: `EXIF` and `ICCP` chunks in the source container are not copied, and this is a second lossy generation. The first encoder has already quantized the image; the second now re-quantizes the decoded result with a different transform and 4:2:0 chroma subsampling, so the two sets of artifacts stack. On flat graphics and text — common here, because the source format is widely used for UI assets — the new stage adds ringing the input did not have. ### How the file size changed in a measured run This is the pair where the popular assumption runs backwards. On 2026-09-12 the script measured a 1280 × 854 lossy WebP at quality 85, 319,834 bytes, and encoded it to JPG at the same quality 85 with 4:2:0 chroma: 347,607 bytes. The output was about 8.7% larger than the input, despite being a second lossy generation of the same photograph. That is what people mean when they call the newer format more efficient — at matched quality settings it simply needs fewer bytes. The JPG figure came from sharp in Node while your browser encodes through canvas, so the exact number shifts a little, but the conclusion holds: this conversion is a compatibility decision, not a size optimization. ### When you should not convert WebP to JPG Do not convert to save space; the measurement says you will usually spend it. Do not convert anything that depends on transparency, such as an icon, a badge or a product image that has to sit on colored pages — PNG keeps the alpha and is offered right here. Do not convert an animation you want to keep moving. Do not make it a routine step for the web, where every current browser handles the original. It is the right call when one specific piece of software is the blocker: an older image editor or office suite, a print or photo-lab upload, a legacy CMS, a camera or e-reader that indexes one extension only, or a form that names .jpg in its accepted list. Conversion happens entirely in your browser — no upload, no queue, no watermark. Drop in as many files as you like and download them individually or as a zip. ## Limits Transparency goes first. The target has no alpha channel, so a sticker, a logo or a cut-out product shot is composited onto the background color selected in the settings above, and the converter warns you as soon as it finds alpha to flatten. The result is a rectangle: the object now sits on solid white, or on whichever color you picked, and the cut-out cannot be reconstructed afterwards. Semi-transparent pixels — the soft edge of a shadow, a faded watermark — are blended into that color rather than clipped, so the edge looks correct against that one background and wrong against any other. Animation goes next. A multi-frame source is detected by frame count, and with this target the converter keeps the first frame, closes the decoder and warns that only one frame was converted. Frame delays and the loop count have no equivalent in a still format. Choosing GIF as the target instead preserves the whole animation, and keeping the original format obviously preserves it too. Then comes the usual toll: `EXIF` and `ICCP` chunks in the source container are not copied, and this is a second lossy generation. The first encoder has already quantized the image; the second now re-quantizes the decoded result with a different transform and 4:2:0 chroma subsampling, so the two sets of artifacts stack. On flat graphics and text — common here, because the source format is widely used for UI assets — the new stage adds ringing the input did not have. ## FAQ ### Does converting WebP to JPG make the file smaller? Usually not. In the measured 1280 × 854 sample at matching quality 85, 319,834 bytes became 347,607 — about 8.7% larger, and a second lossy generation as well. Convert for compatibility with a specific program, not to save bandwidth. ### What happens to a transparent WebP logo or sticker? The transparent area is filled with the background color from the settings, white unless you change it, and a warning appears. The cut-out cannot be recovered from the result, so pick the color the image will actually sit on, or convert to PNG instead. ### Which programs still need a JPG rather than a WebP? Typically older desktop editors and office suites, some print and photo-lab upload portals, legacy publishing systems, a few cameras and e-readers, and forms whose accepted-extension list predates the newer format. Everything current on the web opens both. ### Are my images uploaded anywhere? No. Conversion happens inside your browser using the canvas API and a Web Worker — files never leave your device. There is no upload step, no queue and no file size limit beyond your machine's memory. ### Is EXIF metadata kept in the converted image? No — and that's a feature. Re-encoding through the canvas strips all metadata: GPS location, camera model, timestamps and color profiles. The output contains pixels only, which is usually what you want before sharing an image publicly. ### Can I convert many images at once? Yes. Drop or paste any number of files; each is converted in the background with its own progress and download button, and you can grab everything at once as a .zip archive. ### Will converting lower my image quality? It depends on the target. The converter always decodes to raw pixels and re-encodes, whichever formats are involved, which is also how metadata gets stripped. For lossless targets (PNG, and GIF within its 256-color limit) the pixels stay identical to what was decoded; for JPEG, WebP and AVIF the quality slider controls the trade-off, and converting a file that is already lossy adds one more generation of loss.