Free, in your browser — your image never leaves you. WebP files are 25–34% smaller.
or drop the image here
Converting…
RoundCut converts JPG to WebP entirely in your browser using the platform's native image encoder. The file is never uploaded. WebP files are 25 to 34 percent smaller than JPEG at the same visual quality, per Google's WebP spec, which makes pages faster and helps Core Web Vitals. The output is near-lossless and visually indistinguishable from the source for photographs.
Drop a JPG file on the upload area (or click to pick one). The conversion runs the moment the file lands — there is no "Convert" button to chase. When the result is ready, the stats line shows the input size and the output size side by side, and the Download button saves the WebP to your device with the same base filename. If you want to convert another JPG, just drop it on top — the previous result is replaced.
WebP exists to make the web faster. Google's own spec puts WebP at 25 to 34 percent smaller than JPEG at equivalent visual quality, and on real photographs the savings are often larger — a 17 KB JPG can land near 7 KB as WebP, and a 116 KB 4K photo near 32 KB. Smaller image bytes mean a faster Largest Contentful Paint, which is one of Google's Core Web Vitals and a direct ranking factor for Search. The format ships with no per-pixel licensing fee, which is why every major CDN supports it by default.
Use WebP for anything destined for a webpage you control — hero images, product shots, blog photos, gallery thumbnails, social cards served from your own domain. Every modern browser decodes it (over 97 percent of global traffic in 2026, Safari included since version 14). Stick with JPG when the file is going somewhere that still expects JPEG: email attachments, print workflows, photo editors a generation behind, or platforms that strip and re-compress WebP back to JPG anyway. The right pick is wherever the file lands, not wherever you start.
JPG is already a lossy format, so going JPG to WebP is a lossy-to-lossy re-encode — minor extra artifacts are possible in theory. The encoder is tuned to a near-lossless setting where photographs are visually indistinguishable from the source. For best results, convert from the highest-quality JPG you have, not from a copy that has already been compressed by a chat app or a CDN. There is no quality slider in this version — the setting is what every conversion uses.
The conversion runs in the browser's native image engine. Nothing is uploaded, nothing is logged, nothing is queued on a server, and the page does not even keep the file in memory once you close the tab. If you open DevTools and watch the Network panel while you convert, you will see zero outbound image requests — the file simply never leaves your machine. The same code path runs on every modern browser, so there is no "server fallback" lurking behind the scenes either.
For the web, yes. WebP produces 25 to 34 percent smaller files than JPEG at the same visual quality, per Google's WebP spec, which is why every major site has moved to it. For print, CMYK workflows, or older photo editors that still cannot read WebP, JPEG remains the safer choice.
Strictly speaking yes — both formats are lossy, so re-encoding adds a small amount of extra compression. At the near-lossless setting used here the difference is invisible to the eye on photographs. For the cleanest result, convert from the original JPG straight off the camera rather than from a copy already compressed by a chat app or a CDN.
In almost every case, yes. Google's own spec puts WebP at 25 to 34 percent smaller than JPEG at the same quality, and on typical photographs the saving is often larger. Very small images — already heavily compressed thumbnails under 10 KB — may see little to no reduction, since they are close to the encoder's floor.
WebP is supported by more than 97 percent of browsers worldwide in 2026 — Chrome, Firefox, Safari (since 14 on iOS and iPadOS, since 16 on macOS Ventura), Edge, and Opera all decode it natively. The only holdouts are Internet Explorer 11 and Safari 13, both with negligible market share.
Your file never leaves your browser. The conversion runs entirely on your device using the platform image engine — no upload, no server, no data collection, no telemetry on the file's contents. You can verify it: open DevTools, switch to the Network panel, and run a conversion. You will see zero outbound image requests during the entire pipeline.
Not yet — the current version converts one JPG at a time. Batch conversion is on the roadmap for a later release. In the meantime, dropping a new JPG on the upload area immediately replaces the previous result, so working through a folder of photos is reasonably quick even without true batching.