WebP to JPG
Turn a WebP into a JPG. Any alpha is flattened onto a background nobody picked, and a lossy WebP is put through a second lossy encoder.
Runs on your device. The file is never uploaded.
WebP to JPG has no alpha channel to write into, so the colour stored under each clear pixel is the colour you end up with, and nobody chose it. A WebP pulled off a web page has usually been through a lossy encoder once, so this is a second pass. The quality box governs that pass, not the one before.
Questions
Does WebP to JPG upload my files?
No. WebP to JPG runs inside this browser tab, in a Web Worker on your own machine, and no part of your file is sent anywhere. There is no upload step to skip — the tool cannot reach a server even if it wanted to, and the counter on the homepage shows the number of outbound requests the page has made: zero.
How many files can I use at once?
Drop as many as you like. Each file is handled separately and comes back as its own result, so twenty files in means twenty results out.
What can I change about the result?
One setting: quality (Quality 1-100). Defaults are filled in, so it runs without changing anything.
Is WebP to JPG free, and do I need an account?
It is free and there is no account, no sign-in and no quota. Nothing is metered because nothing runs on a server — the only limit is your own device's memory, which is what decides how large a file it can handle.
Does it work offline?
Yes. The whole site is stored in your browser after the first visit, so WebP to JPG keeps working with the network off. Tools that use a machine-learning model download that model once, on first use, and run offline afterwards.
Can I use WebP to JPG outside the browser?
Yes. Every tool here is the same code on three surfaces: this page, a CLI command, and an MCP tool an AI agent can call. `webp-to-jpg` is the name it goes by on all three.