ImgSquash

JPG to WebP Converter

JPG is universal, but it is lossy and cannot store transparency. Converting to WebP gives you files roughly 25–35% smaller than JPG at the same visual quality — ideal for websites. Two limits push people off JPEG: it has no alpha channel at all, so there is no way to store a transparent background, and every re-save discards more detail. That second one accumulates — an image edited and re-saved a dozen times looks visibly worse than the original with no single step to blame. Images going onto a website, where the 25–35% saving over JPEG is bandwidth and Core Web Vitals rather than an abstraction. Drop your files below; everything runs locally through the Canvas API, with no upload, no size limit and no account. Check where the result has to open before you commit to a batch — every current browser reads WebP, but desktop and office software is patchier, so it is a format to publish in rather than to hand to somebody.

Drop images here

or click to browse — JPG, PNG, WebP, HEIC, AVIF, GIF, BMP, SVG

Private: files never leave your device

What a JPG file actually is

JPEG has been the default photographic format since 1992. It divides the image into 8×8 blocks and discards the high-frequency detail within each one, which is why it compresses photographs so well and why hard edges and flat colour — screenshots, logos, text — pick up the smeared halos known as ringing artifacts.

Almost every camera, scanner and non-Apple phone writes JPG, and it is what a website will hand you when you save an image. If a file came from somewhere and you have no idea what produced it, JPG is the safe bet.

What you get from WebP

WebP output uses lossy compression with a quality control, but unlike JPEG it can keep an alpha channel at the same time — one format for photographs and for graphics with transparency.

Every current browser reads WebP; Safari joined in version 14 in 2020, which was the last real holdout. Desktop applications are patchier, so it is a format to publish in rather than to archive in.

What changes when you convert JPG to WebP

Both formats are lossy, so this is a re-encode rather than a copy: the JPG is decoded to pixels and those pixels are compressed again as WebP. Detail the original already discarded cannot come back, and the second pass removes a little more. One generation at a sensible quality is not something you will notice, and WebP's efficiency means the result usually lands close to or below the original's size — a rare case where re-encoding does not cost you space.

There is no transparency to preserve — JPG files do not carry an alpha channel, so every pixel is opaque to begin with. Converting to a format that supports transparency does not create any; it only means you could add it later in an editor.

Frequently asked questions

Is this JPG to WebP converter really free and private?

Yes. Conversion happens entirely in your browser using the Canvas API — your JPEG photographs are never uploaded to a server, there is no file limit, no watermark and no sign-up.

Can I convert multiple JPG files at once?

Yes — drop any number of files and they convert in one batch. Use "Download all" to save the results as a single ZIP.

Does converting JPG to WebP lose quality?

Both formats are lossy, so this is a re-encode rather than a copy: the JPG is decoded to pixels and those pixels are compressed again as WebP. Detail the original already discarded cannot come back, and the second pass removes a little more. One generation at a sensible quality is not something you will notice, and WebP's efficiency means the result usually lands close to or below the original's size — a rare case where re-encoding does not cost you space.

Will a WebP file open on every device?

In a browser, yes — every current browser has supported WebP since Safari 14 in 2020. Outside the browser it is less certain: older desktop editors, some print workflows and a number of CMS uploaders still reject it. Use WebP for the web and JPG or PNG for anything you are handing to someone else.

I converted a JPG and re-saved it a few times — why does it look worse?

Every JPEG save re-runs the lossy compression, and the damage accumulates across generations. The fix is to keep one original and always export from it, rather than editing and re-saving the same JPG repeatedly.

Related conversions

JPG → PNGJPG → ICOPNG → WebPHEIC → WebPAVIF → WebPGIF → WebP

Advertisement