JPG to WebP
Re-encode a JPG as WebP. The old compression artefacts are picture now, so the WebP encoder spends bits keeping them rather than clearing them.
Runs on your device. The file is never uploaded.
JPG to WebP puts one lossy encoder's output through a second one. Quality defaults to 80, and a lower number is where the saving is. Every ringing edge and blocking square left by the first pass reads as ordinary detail. WebP has no way to tell one from a real edge, so it pays to keep both.
Questions
Does JPG to WebP upload my files?
No. JPG to WebP 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 JPG to WebP 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 JPG to WebP 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 JPG to WebP 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. `jpg-to-webp` is the name it goes by on all three.