No upload — runs in your browser

Convert JPG to WebP

Turn JPG photos into WebP files in your browser — the same picture at roughly two-thirds of the size, which is why most sites serve WebP today. Nothing is uploaded: your photos stay on your device. Free, no sign-up, no watermark, up to 20 files at a time.

90% · applies to every file you add

Drop JPG files here to convert to WebP

JPG in, WebP out — up to 20 files, 50.00 MB each. Nothing is uploaded.

What WebP actually saves you

WebP uses a newer compression method than JPG and reaches the same visual quality in roughly two-thirds of the bytes. On a photo-heavy page that difference shows up directly in load time: a gallery of twenty 200 KB JPGs becomes about twenty 140 KB WebP files, which is 1.2 MB less to transfer.

The conversion happens entirely on your device. Your browser decodes the JPG, paints it on a canvas and encodes the result as WebP — no round trip to a server, which also means no upload time and no waiting in a queue.

When to stay with JPG

Keep the JPG whenever the file has to leave the web: sending it to a print shop, attaching it to a form that only accepts .jpg, or opening it in an older desktop editor. WebP wins on size; JPG still wins on ubiquity.

How to convert JPG to WebP

The whole conversion runs on your own device, so there is nothing to sign up for and no queue to wait in: the browser decodes the JPG, paints it onto a canvas and writes the result back out as WebP.

  1. Add your JPGs

    Drop files onto the page or pick them from your device — up to 20 at a time, each up to 50 MB. Nothing is uploaded at this step or any other.

  2. Set the quality

    The slider defaults to 90%, where the WebP is visually indistinguishable from the source at normal viewing size. Lower it for smaller files, raise it for fine detail and small text.

  3. Convert and download

    Each file is converted on your device and offered as a download, one after another — the WebP never touches a server.

WebP, JPG and AVIF: which one to publish

Three formats cover almost every image on the web, and the choice is a trade of size against reach and encoding effort. JPG is the universal baseline; WebP is today's default for photographs; AVIF goes smallest but costs the most to produce.

FormatWhat it is good for
JPGOpens everywhere, from an old camera to a print shop, and is what an upload form expects by default. The safe fallback when the destination is unknown.
WebP25–35% smaller than JPG at the same quality, supported by every browser released since 2020, with optional transparency. The default for photographs on a site.
AVIFTypically another 20–30% smaller than WebP and strongest on large photo libraries — at the cost of slower encoding and narrower support.

After the conversion: where the WebP usually goes next

Converting is rarely the last step, and every tool below works the same way as this one: it runs in your browser, on your device, with nothing uploaded.

If you need to…Use
Shrink the file to an exact limitHit a target such as 100 KB or 1 MB — the requirement upload forms and marketplaces actually enforce.
Change the pixel dimensionsScale width and height for thumbnails, avatars and print, with or without keeping the aspect ratio.
Convert WebP back to JPGThe reverse direction, for software or a form that still insists on JPG.
Convert PNG to WebPThe same saving for PNG sources, where transparency is carried across instead of dropped.
Put several images into oneStack or grid pictures into a single file — handy for before/after comparisons.

Frequently asked questions

Does converting JPG to WebP lose quality?

Once. WebP re-encodes the picture, and because JPG is already an approximation the second pass adds a little loss. At the default 90% it is hard to see; below that, softness starts to show around edges and text.

Can every browser open the WebP files I get?

Yes. WebP is supported by Chrome, Edge, Firefox, Safari and Opera, and any browser released in the last decade will display it. The exceptions are old desktop software — a photo editor from before 2018 may refuse to open WebP, so keep the JPG if that is where the file is going.

How much smaller do the files get?

Usually 25–35% at the same visual quality. The saving is largest on photographs and smallest on flat-colour graphics or images that were already heavily compressed — a JPG saved at quality 60 will not shrink much further.

Is the resolution preserved?

Yes. The pixel dimensions are kept identical — a 4000×3000 photo stays 4000×3000. Only the encoding changes, so you never lose detail by resizing.

Can I convert several JPGs at once?

Yes — up to 20 files per run, each up to 50 MB. Everything runs on your own device, one file at a time, with no upload and no queue.

Are my images uploaded anywhere?

No. Decoding and encoding both happen inside your browser with the Canvas API and a Web Worker, so your photos never leave your device.

Should I convert to WebP or to AVIF?

WebP is the safer default and AVIF is the smaller file. WebP saves roughly 25–35% over the same-quality JPG and is understood by every browser released since 2020, so it is the pragmatic choice for a handful of images. AVIF compresses further — typically another 20–30% on top of WebP — but it takes noticeably longer to encode and support is narrower, so it earns its place mainly on a large photo library where bytes matter more than the extra processing time.

Does WebP keep transparency?

Only if the source had any. WebP carries an alpha channel that JPG does not, so converting a PNG or SVG to WebP preserves transparency — but a JPG has no transparency to begin with, which means the WebP you get back from a JPG is opaque too. A JPG can never gain an alpha channel by being converted; if you need see-through pixels, start from a PNG or SVG instead.

Will WebP make my page load faster?

Usually yes, and it is the reason the format exists. Image bytes are normally the largest part of a page's weight, so a 25–35% cut on the images shows up in load time and in Largest Contentful Paint, one of Google's three Core Web Vitals. The gain is proportional to how much of the page is images: a 200 KB hero photo falling to about 140 KB is measurable, while a 12 KB icon is not. Google's own study of WebP measured 25–34% smaller files at matched quality.

Can I convert the WebP back to JPG later?

Yes — the conversion is not one-way. Every modern browser can decode WebP, so you can feed the WebP back into a converter and write out a JPG again. The one thing to know is that each re-encode is lossy, so JPG → WebP → JPG carries a second generation of loss. If there is any chance you will need the original, keep the JPG you started from.

Other tools

Browse all Image tools →