Real bandwidth savings
WebP typically lands 25–35% below an equivalent JPEG. Across a photo-heavy page that is the difference between a fast paint and a sluggish one, and it directly improves Core Web Vitals scores.
JPG to WebP Converter
Convert JPG photos to WebP and cut file size by around a third.
- Upload
- Batch upload supported · 25 MB max
- Privacy
- Nothing is uploaded
- Cost
- Free · no sign-up · no watermark
Loading tool…
The tool is loading its code on your device. This happens once and is cached for later visits.
Processed entirely on your device
Your file is read, transformed and re-encoded inside this browser tab using JavaScript. There is no upload endpoint — nothing leaves your machine, nothing is stored, and the result is created as a local object URL that disappears when you close the page.
Overview
About the JPG to WebP Converter
Recompress JPEG images as WebP for faster pages. Choose lossy or lossless mode, tune quality, and convert in batch — processed locally, never uploaded.
If your site still serves JPEGs, converting them to WebP is the highest-return performance change you can make in an afternoon. Google built WebP specifically to beat JPEG at the same perceived quality, and Lighthouse flags unoptimised image formats as one of the most common reasons a page fails its Largest Contentful Paint budget.
Lossy or lossless?
Lossy WebP is the replacement for JPEG. It uses predictive coding — each block is predicted from its neighbours and only the difference is stored — which is why it beats JPEG's discrete cosine transform at low bitrates. Use it for photographs, hero images and anything with smooth gradients.
Lossless WebP is the replacement for PNG. It keeps every pixel exact and still typically produces files about 26% smaller than PNG. Use it for logos, icons, screenshots and diagrams where ringing artefacts would be obvious.
The toggle in this tool selects between the two. If you are converting photographs, leave it on lossy and set quality between 75 and 85.
Resize in the same pass
A 4000-pixel-wide camera JPEG displayed at 800 pixels is wasting roughly 95% of its bytes. Every recompression costs a little quality, so it is better to downscale and re-encode once than to convert now and resize later. Set the maximum width to match your largest real display size — commonly 1600 or 1920 pixels for full-bleed heroes, 800–1200 for content images.
Serving WebP correctly
Name the output with a .webp extension and set the Content-Type: image/webp header if you serve files directly. In HTML, a <picture> element gives you a graceful fallback:
<picture><source srcset="photo.webp" type="image/webp"><img src="photo.jpg" alt=""></picture>
Most modern build pipelines and CDNs will do this negotiation for you, but knowing the fallback pattern is useful when you are editing a legacy template by hand.
Step by step
How to use the JPG to WebP Converter
Upload one or more .jpg or .jpeg images.
Set the WebP quality — try 75–82% for photographs and compare against the original size.
Optionally cap the maximum width so oversized photos are downscaled in the same pass.
Press Convert to WebP and review the savings shown for each file.
Download the .webp results and drop them into your site or CMS.
Why use it
Benefits and common use cases
What this tool is good for, and what it deliberately does not try to do.
Two encoding modes
Lossy mode for photographs, lossless mode for graphics that must stay pixel-exact. Lossless WebP is still usually smaller than the PNG it replaces.
Resize while you convert
Most camera JPGs are far larger than they are ever displayed. Capping the width in the same step avoids a second pass and a second round of compression.
Safe for unreleased work
Client photography, unannounced products and internal mockups stay on your machine — the conversion is done by the browser's encoder, not a remote service.
Questions
Frequently asked questions
Short, honest answers about quality, limits and privacy.
How much smaller will my files get?
For typical photographs, expect 25–35% smaller than the source JPEG at equivalent visual quality. Images that were already heavily compressed will save less, and flat graphics saved in lossless mode can shrink dramatically compared with PNG.
Does WebP support transparency if my JPG doesn't have it?
WebP supports an alpha channel, but a JPEG never contains transparency to begin with, so the converted file will be fully opaque. Converting a PNG with transparency to WebP does preserve the alpha.
Will converting JPG to WebP degrade the image twice?
Some loss is unavoidable because you are re-encoding an already lossy image. At quality 80 or above the additional degradation is not perceptible. Keeping quality high and resizing in the same pass minimises the compounding effect.
Do all browsers support WebP?
Yes — WebP has been supported by Chrome, Edge, Firefox, Safari 14+ and all mobile browsers since around 2020. If you must support truly ancient clients, keep a JPEG fallback in a <picture> element.
Can I convert many images at once?
Batch conversion handles up to 20 files with identical settings and reports the size saved for each one, so you can verify the result before downloading.