Convert JPEG to WebP
Drop a JPEG file below and get a WebP back. The conversion happens on your own machine, so nothing is uploaded and there is no size or quantity limit beyond what your browser can hold in memory.
Drop images here
Ctrl/⌘ VPaste a screenshot or copied image
Accepts JPEG
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert JPEG to WebP?
For the same picture, WebP usually lands well under the size of the JPEG original. That matters when you are trimming page weight or squeezing under an upload limit.
WebP supports an alpha channel, so you can cut out a background after converting. The conversion itself will not invent transparency that the JPEG file never had.
Both formats are lossy. Every re-encode discards a little more detail, so it is worth starting from the original rather than from a copy that has already been through this a few times.
Almost everyone doing this is trying to make a website faster, and it works: WebP will usually take a JPEG down by a quarter to a third at matching visual quality, across a whole image library that adds up fast. One caveat is worth understanding first, because it decides how good your result can be.
Before you convert
You are compressing something that was already compressed
The JPEG threw away detail when it was made, and the WebP encoder now works on that damaged picture — including its blocking artefacts, which it faithfully spends bytes preserving. If you still have the original camera file or the layered export, encoding WebP from that will give you a smaller and cleaner result than going through the JPEG. When the JPEG is genuinely all you have, this is still worth doing; just do not expect it to match what a direct encode would have achieved.
Do not raise quality to compensate
The instinct on a second-generation encode is to push quality up to protect what is left. It backfires: high settings make the encoder spend bytes reproducing the JPEG artefacts precisely, and you end up with a WebP that is larger than the JPEG it came from — the opposite of why you started. Around 80 usually lands smaller with no visible change.
Serve both, do not replace
The standard way to ship WebP is a picture element with the WebP first and the JPEG as fallback, so browsers that want it get it and everything else still works. Deleting the JPEG saves you storage and costs you a fallback — rarely a good trade for a public site.
What carries over
- Pixel dimensions
- Visual appearance at sensible settings
- A quarter to a third off the file size
What does not
- A little more detail — this is a second lossy pass
- Support in older email and desktop software
JPEG vs WebP at a glance
| Property | JPEG | WebP |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | No | Yes |
| Typical file size | 100% of an equivalent JPEG | 65-75% of an equivalent JPEG |
| Compatibility | Opens everywhere, including decades-old software | Supported by all current browsers and most apps |
| Usually comes from | Digital cameras and photo sharing | Websites optimising page weight |
Frequently asked questions
Are my JPEG files uploaded anywhere?
No. The decoder and encoder are WebAssembly modules that run inside this page. The network tab may show a codec downloading the first time you use a format, but no request contains your file. On supported browsers, a codec that has already been used is cached so the same conversion can work offline.
Is there a file size or quantity limit?
There is no limit imposed by us. The practical ceiling is your device’s memory, since the image has to be held uncompressed while converting. On a typical laptop, images up to around 100 megapixels convert without trouble.
Will converting to WebP lose quality?
WebP is a lossy format, so some data is discarded. At the default quality setting the difference is not visible at normal viewing sizes. If you need an exact copy of the pixels, choose PNG instead.
Does it work on a phone?
Yes. The same WebAssembly modules run on mobile browsers. Conversion is slower than on a desktop because phone CPUs are weaker, and very large images are more likely to hit memory limits.
Will converting from JPEG lose more quality?
A little, if the target is also lossy. The JPEG you start with has already discarded data, and a second lossy encode discards a bit more. At quality 80 or above that second loss is hard to spot, but it is exactly why you should keep the original rather than converting the same file back and forth.
Is WebP safe to use on a website?
Yes. Every current browser supports it, which covers roughly 97% of visitors. The remaining gap is old software rather than old browsers — a few desktop image viewers and older CMS upload forms still refuse it.