JPG to WebP Converter | Free, in Your Browser

Original	—
Scaling	Lanczos-3, then an optional sharpening pass
Metadata	EXIF and GPS removed by re-encoding

Opens on WebP output. For photographs on a website this is generally the right move: WebP is usually 25 to 35 per cent smaller than JPEG at a quality nobody can tell apart, and browsers have handled it for years.

It is a lossy hop from a lossy file. The JPEG is decoded to pixels and re-encoded, so a little more is thrown away. At a sensible quality that is invisible; at a low one, or repeated, it is not. Convert from the largest original you have rather than from a JPEG that has already been through this a few times.

Keep the JPEG. Not everything outside a browser reads WebP, and the original is the only thing you can convert from again without stacking another round of loss on top.

How to use it

Choose a JPG file, the largest original you have. Nothing is uploaded: it is read in this tab.
Leave the quality near 80 for a photograph on a web page, and shrink the width to the size it is shown at.
Press Download, compare the size with the JPG, and keep the original.

Questions

How much smaller will the WebP be?

Usually 25 to 35 per cent for a photograph at matched quality, sometimes more. The saving is largest on big, detailed images and smallest on ones that were already compressed hard, where there is little left to take out.

Should I delete the original JPEG?

Not if you can help it. Anything outside a browser may refuse the WebP, and the JPEG is the cleaner source for any future conversion. Every extra hop between lossy formats costs a little more and none of it comes back.

Does the WebP keep the photo's EXIF and GPS data?

No. The picture is decoded to pixels and encoded afresh, and the camera data, the date and any GPS position in the JPG are not carried over. For photographs going on a public web page that is usually what you want. If you need the metadata kept, this is not the tool for it.

Can I upload WebP to WordPress, Shopify or social media?

WordPress accepts WebP uploads since version 5.8, and most modern site builders and shops take it. Social networks and messaging apps vary and some convert whatever you upload to their own format anyway, so for those the JPG is the safer file to send. It is on your own website that WebP pays off.

Should I shrink the picture as well?

Usually, and it saves more than the format does. A photograph straight off a phone is around 4000 pixels wide, and a web page rarely shows one wider than 1600, or twice that for sharp screens. Set the width here and the conversion and the resize happen in one pass.

JPG or WebP: what changes when you convert

	JPG	WebP
Compression	Lossy	Lossy here; the format can also be lossless
Size, same visible quality	Baseline	Usually 25 to 35 per cent smaller
Transparency	No	Yes
Browsers	All	All current ones, Safari since 2020
Outside the browser	Everything	Patchy: older editors, Office versions and upload forms refuse it
Camera metadata	Kept by the camera	Not carried over by this conversion

WebP earns its place on web pages, where every kilobyte is paid for in load time by every visitor. Anywhere else, in a document, an email or a print shop, the JPG is the file that will simply open, which is why it is worth keeping alongside.

The other conversions

The same tool opening on a different output format. Any of them will convert to any of the three once you are there.

Your data stays on your device

Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. You can load this page once, go offline, and it still works.

This page makes no requests at all, to anywhere. That is not a promise in the copy: it is a Content-Security-Policy header your browser enforces, and connect-src on it is none. Open the network tab and watch nothing happen.