Convert JPG to WebP
WebP typically produces files 25–35% smaller than JPEG at the same perceived quality, which is why it has become the default format for fast websites. Drop your JPGs here, pick a quality, and get WebP files ready to upload. The encoder is the one already built into your browser.
How to use the JPG to WebP
- Add the JPGs you want to publish — product shots, blog images, hero photos.
- Set the quality. 82 is a sensible starting point for web use.
- Convert, then compare the size summary against your originals.
- Download the WebP files and upload them to your site or CMS.
Why sites moved to WebP
Images are usually the heaviest part of a web page, and page weight is one of the things Google measures under Core Web Vitals through Largest Contentful Paint. WebP uses prediction and transform techniques borrowed from the VP8 video codec, which handles gradients and flat areas more efficiently than JPEG's discrete cosine transform. In practice that means a photograph that is 400 KB as a quality-85 JPEG will usually land somewhere between 250 KB and 300 KB as a quality-82 WebP with no visible difference at normal viewing size.
Browser support is no longer a reason to wait
Chrome, Firefox, Edge, Opera and Safari 14 and later all display WebP. Every current mobile browser does too. The remaining gaps are outside the browser: email clients, older desktop applications and some upload forms. That is why the sensible pattern is to serve WebP on your website and keep a JPG for anything that leaves it — attachments, print, hand-off to clients.
Choosing a quality value
| Quality | Use for | Typical saving vs JPG 85 |
|---|---|---|
| 90–95 | Hero images, photography portfolios | 10–20% |
| 80–88 | Most web and product images | 25–35% |
| 65–78 | Thumbnails, backgrounds, long feeds | 40–55% |
WebP quality numbers are not interchangeable with JPEG ones: WebP at 80 usually looks like JPEG at 85–88. If in doubt, convert one image at two settings and compare them at full size.
Re-compression and when to avoid it
Your JPG has already been compressed once, so this is a second lossy pass. It is worth it for the size saving, but it means you should always convert from the highest-quality JPG you have rather than from a copy that has already been resized and re-saved several times. If the JPG is visibly blocky, WebP will faithfully reproduce the blocks.
What about transparency?
WebP supports an alpha channel, but a JPEG has none to give it, so the output is fully opaque. If you need transparency, start from a PNG.
Frequently asked questions
How much smaller will my images get?
For photographs, typically 25–35% at matched visible quality. Flat graphics and screenshots often do even better.
Which browsers can display WebP?
Chrome, Edge, Firefox, Opera and Safari 14 or later, on desktop and mobile. Support outside browsers is less consistent.
Should I delete my JPGs after converting?
Keep them. You will want a JPG for email attachments, printing and any upload form that rejects .webp.
Is the WebP encoder here lossless?
No. This uses the browser lossy WebP encoder. At quality 95 or above the difference from the source is extremely hard to see, but it is not a bit-exact copy.
Privacy
This tool runs entirely inside your browser using WebAssembly and the Canvas/File APIs. Your files are never uploaded to ToolFlint or any third party; you can verify this in your browser's network tab or by switching to airplane mode after the page loads. Read how we process files.
Last updated 2026-09-23.