Convert JPG to WEBP
Drop the JPG and download it as WEBP — same look, considerably lighter.
Drop an image here
or
PNG, JPG, WEBP, HEIC, AVIF, JXL, GIF, BMP, TIFF and SVG · up to 20 MB
The change that shows up most in page speed
If you run a site with photographs and want it to load faster, this is the one optimisation you can do in an afternoon that genuinely shows. WEBP weighs 25–35% less than a JPG of the same apparent quality, and every current browser has understood it since 2020.
The impact isn't just a feeling of speed. Largest Contentful Paint — one of the Core Web Vitals Google uses as a ranking factor — is usually determined by exactly that big image near the top of the page. Cutting it by a third moves the metric directly.
Watch out for double compression
A JPG has already been through lossy compression. Converting it to WEBP decodes it and compresses it again, this time with a different codec. At reasonable qualities you won't see it, but it's worth knowing the best result doesn't come this way:
- If you still have the original — the RAW, the export PNG, the designer's file — convert that to WEBP directly. You save a generation of loss.
- If all you have is the JPG, convert it and don't overthink it: the gap from the ideal route is small and the size saving is large.
- What you shouldn't do is bounce between formats repeatedly. Every round trip adds degradation that never comes back.
WEBP or AVIF?
AVIF compresses better still, roughly 20–30% below WEBP. In exchange it takes longer to encode and its support outside the browser is worse. For most sites WEBP is the sweet spot: nearly all the saving, none of the complications. If you serve a great many images and bandwidth is a real cost, AVIF starts to pay off.
Common questions
- How much will I save?
- 25–35% against a JPG of the same apparent quality, sometimes more on large photographs. Across a page with twenty images that's the difference between loading fast and not.
- Do all browsers support it?
- Yes. Chrome, Firefox, Edge, Safari and the mobile browsers have supported WEBP since 2020. If your audience is on current desktop or mobile browsers, you don't need a fallback.
- Do I lose quality converting?
- There's a second compression, because your JPG was already lossy. At the default quality it isn't visible. If you still have the uncompressed original, converting that straight to WEBP gives a better result than going through JPG.
- Should I delete the JPGs afterwards?
- No. WEBP is for publishing; the original is for archiving and re-editing. If you ever need another version, you'll want to start from the JPG rather than an image compressed twice over.
- What if someone downloads the image from my site?
- They'll get a WEBP, and their desktop software may not open it. That's the price of serving the efficient format, and it's why converters like this exist in the other direction.