PDFJadoo › Blog › JPG to WebP for Website Speed

JPG to WebP: the cheapest speed your website will ever buy

The direct answer: drop the JPG, choose the quality — High (92%), Balanced or Smaller — and the same photo comes back as WebP, typically 25–35% smaller at comparable visual quality, with any transparency kept. JPG to WebP is the site-owner's tool in this family: a page carrying ten photographs carries their weight on every visit, on every phone, on every metered connection — and image weight is usually the largest single component of a page. The saving's mechanism is a generation gap: JPG's compression dates from 1992 and works on independent 8×8 blocks, while WebP predicts each block from its neighbours and stores only the correction — prediction is why the same picture costs fewer bytes. The tool's own calibration is the practical one: at the High setting (92%) photos look identical to the eye; Balanced is the working default for page images; Smaller is for thumbnails and previews. The honest boundary is compatibility, and it is the mirror of the WebP rejection story told elsewhere on this blog: browsers read WebP universally now, but email clients, upload forms, Word documents and print shops still reject it — the website gets WebP, the world's paperwork keeps JPG.

Free, in your browserFiles never uploaded25–35% lighter · High 92% · web-only destination
PDFJadoo logoBy the PDFJadoo Team6 min read
Diagram: a JPG photo becoming a smaller WebP for a web page, with a weight comparison
Same photo, same look, a third fewer bytes — multiplied by every visitor.

Where the bytes go

The direct answer: a photograph's JPG spends its bytes describing every block of the picture from scratch; WebP's predictive coding describes most blocks as “like the neighbour, except this much” — and the exception lists are shorter than the full descriptions. The gain is largest on smooth photographic content (skies, skin, gradients — prediction's home ground) and smallest on noisy or already-tiny images. One quotable calibration guards the expectations: WebP quality numbers are not JPG quality numbers — the same slider value in the two formats is not the same fidelity — so judge the output with your eyes at the size it will display, not by matching numbers across formats.

The compounding is the site owner's real argument: a third off one photo is a rounding error; a third off every photo on every page, for every visitor, is load time, data cost and the Largest Contentful Paint figure search engines measure — paid once, at conversion, and collected forever.

What not to convert

The direct answer: images whose destination is not a browser — email attachments, form uploads, office documents, print — stay JPG, because the rejection family is real: the same compatibility wall that makes WebP-to-JPG a flagship tool guards those doors. Convert for the web you control; keep the universal format for everywhere you do not. The master's discipline from the sibling article applies unchanged: the JPG (or PNG) original stays filed as the source; WebP is a delivery copy.

Convert JPG photos to WebP, step by step

The direct answer: drop one photo or a whole batch, pick the quality for its job — High for heroes, Balanced for body images, Smaller for thumbnails — convert, and download singly or as a ZIP.

Step 1 — drop your JPG image, or a batch, onto JPG to WebP. Conversion runs entirely on your device.

Step 2 — pick the quality. High (92%) for the images a page is judged by; Balanced as the working default; Smaller when size outranks fidelity.

Step 3 — press Convert to WebP. Transparency, if a source ever carries it, is kept — WebP holds alpha, unlike JPG.

Step 4 — download each file, or the batch as a ZIP. Check one at its real display size: identical to the eye is the standard, and it is checkable in seconds.

Step 5 — publish the WebP, file the JPG. The page gets the light copy; your archive keeps the universal master.

The screenshot exception

The direct answer: interface screenshots and text-heavy graphics are PNG's home ground — WebP's lossy mode can soften their edges — so convert photographs to WebP and leave pixel-exact graphics in PNG (or use PNG to WebP for their dedicated path). Format choice follows content, not fashion.

A third off every photo, every page, every visitor — forever.

High, Balanced or Smaller per image's job; batches as ZIP; the JPG master stays filed.

Open JPG to WebP

A worked example: the slow product page

The direct answer: a small shop's category page carrying fourteen product JPGs totalling 3.1 MB converts to WebP at Balanced and lands at just over 2 MB — the page's image weight down by a third, its load on a mid-range phone visibly snappier, with no photograph distinguishable from its original at display size. The walkthrough's discipline: the hero image went at High, the grid at Balanced, the thumbnails at Smaller — quality allocated by the job each image does, not sprayed uniformly. The JPGs stayed in the archive; two of them were later needed for a print catalogue, where the WebP copies would have been refused at the door — the boundary, met in practice.

Edge cases

Already-small images. A 30 KB JPG may save only a few KB — conversion effort follows weight; optimise the heavy pages first.

CMS and platform limits. A few older site builders and marketplaces still refuse WebP uploads — the allow-list problem in reverse. Test one upload before converting the catalogue.

Animated or layered sources. This path is for still photographs; GIF-family animation has its own articles and its own honest limits in this batch.

Before you finish: the 60-second check

Fair questions

How much smaller is WebP than JPG?

Typically 25–35% fewer bytes at comparable visual quality, because WebP predicts each block from its neighbours instead of describing every block independently. The gain is largest on smooth photographic content.

Which quality setting should I use?

High (92%) for images a page is judged by — photos look identical to the eye. Balanced as the working default for body images, and Smaller for thumbnails and previews where size outranks fidelity.

Can I convert a whole batch?

Yes — drop as many JPG files as you like. Each converts with the same settings; download them one by one or all together as a ZIP.

Does WebP keep transparency?

Yes — transparent areas of the source stay transparent in the WebP, one of its advantages over JPG, which cannot hold alpha at all.

Where should I NOT use WebP?

Anywhere the destination is not a browser you control: email attachments, upload forms, office documents and print still reject WebP. Keep JPG for the world's paperwork; WebP for your pages.

Is my image uploaded?

No — the picture is decoded and re-encoded entirely on your device; your files never leave it.

Tool behaviour — the High (92%) / Balanced / Smaller quality settings, transparency kept, batch conversion with ZIP download, and on-device processing — is from PDFJadoo's own JPG to WebP page. Checked 18 November 2026.

Keep reading