Convert JPG to WebP — a third off every photo

A photo gallery, a portfolio, a product catalogue — hundreds of JPGs, every one of them carrying about a third more weight than it needs to. Re-encoding JPG as WebP keeps the visual quality and drops 25–35% of the bytes, and Scalir does it for the whole library at once: drag the folder in, let your own CPU do the work, download the WebP set. No uploads, no queue, no per-file limits.

Preconfigured for JPG → WebP at full size — tweak anything below.

Drop images here

or

Choose files

JPG, PNG, WebP, AVIF, HEIC, GIF, TIFF, BMP · processed on your device, never uploaded

Max size (MB)

Target file size — we compress just enough to fit under this. Output format Auto keeps the original, switching to WebP only when it helps. Or force one format (AVIF is the smallest, but slower to encode).

What a 30% cut means at scale

Typical JPG → WebP savings, multiplied by a real site.

Scenario	Before (JPG)	After (WebP)
One 2 MB photo	2 MB	~1.4 MB
A 40-image gallery page	~25 MB	~17 MB
Portfolio of 300 photos	~450 MB served	~310 MB served
10,000 product views a month	~20 GB bandwidth	~14 GB bandwidth

Batch-convert a photo library

Add the JPGsFiles or an entire folder — the queue takes hundreds at a time.
One click, all coresWebP output is preset at original dimensions and top-of-ladder quality; the batch encodes in parallel on your machine.
Ship the WebP setZIP download or save-to-folder, with your choice of file naming — prefixes, suffixes, slugs, sequential numbers.

When to keep JPG

Not everything should convert. Email attachments, print workflows, photo-lab submissions and anywhere you cannot control the receiving software are still JPG territory. The rule of thumb: if a browser displays it, serve WebP; if a human or a machine you do not control opens it, send JPG.

Scalir converts on your device either way — this page presets WebP output, and the reverse conversion is one click away when you need it.

Frequently asked questions

How much smaller is WebP than JPEG?

At the same visual quality, WebP is typically 25–35% smaller than JPEG. Across a page with many images that is often the difference between a slow load and a fast one.

Should I use WebP instead of JPEG on my website?

For web pages, almost always yes — smaller files, faster loads and support in every modern browser. Keep JPEG for email attachments, print workflows and services that do not accept WebP.

Does converting JPG to WebP lose quality?

Both are lossy formats, but Scalir converts at the top of its quality ladder by default, keeping the result visually identical to the source. Use the before/after preview to inspect any image at any quality.

Can I convert WebP back to JPG later?

Yes — the reverse converter is one click away, and it runs the same way: locally, in bulk, for free. Keep your original JPGs as masters if you want a lossless-history archive. Convert WebP to JPG