Will transparency survive the conversion?

Some upload forms, stock-photo submission systems and prepress workflows specifically require the four-letter .jpeg extension. This produces exactly that, from a .webp source those systems will not touch. WebP is a delivery format, not a working format. Browsers render it everywhere, but the moment a .webp leaves the browser it hits software that never caught up — Photoshop only added WebP support in version 23.2, Office before 2021 will not place one, Outlook will not render one inline, and a long tail of upload forms validate against a hard-coded list that has never heard of it.

JPEG — Joint Photographic Experts Group image (.jpeg) — is lossy dct with none — no transparency at all and support described as: universal — every device, app and upload form ever made. Where WebP is optimised for the last hop to a browser, JPEG is what the software on the other side of that hop is expecting. Converting is a one-step fix for the "this file type is not supported" wall.

Size is the trade-off worth knowing about: JPEG files are 25-35% larger than a WebP of the same visual quality. Both formats are lossy, so a small amount of generational loss is added on re-encode. Invisible above quality 80.

Reasons to convert WebP to JPEG usually come down to compatibility, file-size, or specific feature requirements. Common situations:

• An app or platform only accepts JPEG uploads.
• You need a feature unique to JPEG (e.g. transparency, vector scaling, animation, multi-page pages, etc.) that WebP doesn't provide.
• You're optimising file size — modern formats often produce smaller files than the older format you started with.
• You need a single archival format across a project so files behave consistently in the same viewer.

1. Open the WebP → JPEG tool on webp.now.
2. Drag your WebP file onto the drop zone, or click Select files. You can drop a whole folder of files at once.
3. The output is fixed to JPEG. If the format supports extra options (page size, transparency background, quality, EXIF stripping), tweak them in the right-hand panel.
4. Click Convert. The job runs on our server and finishes in a few seconds for typical photos.
5. Download the result. Files stay in storage for 24 hours and are then permanently deleted.

The entire flow is free for the first 10 jobs per day with no signup required. A free account doubles that quota; a premium plan removes the limit entirely.

• JPEG has no alpha channel, so any transparency in your WebP is composited onto a background colour. Set that colour deliberately — white is the default and is rarely what a logo wants.
• Convert from the highest-quality WebP you have. Each lossy re-encode costs a little detail, and starting from an already-compressed copy compounds it.
• Strip metadata before sharing. Images saved from the web can carry the original photographer's EXIF, including camera serial and, occasionally, GPS coordinates.
• Batch the job rather than converting one at a time — the queue runs conversions in parallel and returns a single zip.
• Keep the .webp original if the image is also going back onto a web page. Serving the JPEG version instead will cost you page weight.