WebP Converter: WebP to JPG, JPG to WebP
This converts WebP images to JPG or PNG, and ordinary images to WebP, in your browser with nothing uploaded. Both directions exist for real reasons: WebP files you saved from the web open poorly in older software, and images you are putting ON the web are usually 25 to 35% smaller as WebP. Drop files in, pick a direction, done. Free, batched, unlimited.
Everything happens in this tab. Your files are never uploaded, because there is nowhere here to upload them to.
How to use it
Drop in your images
WebP files you want out of the format, or JPGs and PNGs you want in. Mixed batches are fine.
Let Auto pick the direction, or override it
By default each file converts to the other side of the pair: WebP comes back as JPG, and JPGs or PNGs come back as WebP. The format row overrides that for the whole batch; pick PNG when a WebP has transparency you need to keep.
Download the results
Individually or as a ZIP. The compare slider is there if you want to see exactly what the re-encode did, which for most images is nothing you can spot.
How this runs without a server
Every other tool in this category works the same way: you upload your image, a GPU in a data centre somewhere runs the model, and the result comes back. That architecture is why they all have credits, watermarks and sign-up walls. Someone has to pay for that GPU, and it is metered by the second.
This page does it differently. When you drop in an image, your browser loads the AI model itself and runs it locally. If your browser supports WebGPU, the model runs on your own graphics hardware, which is typically five to sixty times faster than the CPU fallback. If it does not, we fall back to WebAssembly, which is slower but works everywhere.
Two things follow from that, and they are the entire reason this site exists. First, your photo never goes anywhere: it is read into a canvas in your tab and stays in your device's memory until you close it. There is no upload endpoint on this domain to send it to. Second, our cost per image is zero, so the free tier is not a loss-leader with a trapdoor in it. It is just what the thing costs to run, which is nothing.
The model file is cached by your browser after the first download. That is the one wait you have to sit through, and it only happens once per browser. After that the tool works with your network disconnected, which is a decent way to prove to yourself that nothing is being sent.
Checking that for yourself
You do not have to take our word for it, and you should not. Open your browser's developer tools, go to the Network tab, and use the tool. You will see the model coming down. You will not see your image going up, because it never does. Then turn your wifi off: once the model is loaded, the tool keeps working with no network at all, which is not something we could fake. We walk you through both checks here.
Your photo stays on your device.
Not "deleted after 24 hours". Not "encrypted in transit". Never sent. Here is how we prove it.
Frequently asked questions
Why do so many downloaded images turn out to be WebP?
Because the sites you saved them from serve WebP to browsers to save bandwidth, browsers handle it natively, and the download keeps whatever the site served. The mismatch only appears when an older app, an upload form or a corporate system refuses the file. Converting to JPG makes the problem go away.
WebP to JPG or WebP to PNG, which one?
JPG for photographs: far smaller, and the quality difference is invisible for normal use. PNG when the image has transparency, since JPG would flatten it onto a background, or when it is a sharp-edged graphic that JPEG would smudge.
Should I convert my images to WebP for my website?
If your pages load images, yes, it is one of the easiest performance wins there is: typically 25 to 35% smaller than JPEG at matching quality, with transparency support included. Every browser has supported it since 2020. This tool does the conversion in batch, and it costs you nothing to try.
Does converting on this page upload my images anywhere?
No. Decoding and encoding both happen inside your browser. On the couple of browsers that cannot write WebP themselves, the page loads a small open-source encoder and runs it locally, and your images still go nowhere.