How much smaller is WebP than JPEG in practice?

Google's figure is 25–34% at equal quality. That holds for fresh encodes from clean sources. Re-encoding an already-compressed JPEG yields less, sometimes nothing. Our tool shows the measured result per file, so you convert where it pays and skip where it doesn't.

Does converting JPG to WebP lose quality?

Any lossy re-encode costs a generation. The cost is small at sensible settings and invisible in normal viewing. The compare slider shows your file at 100% zoom before you commit. When the original photo or export exists, encode WebP from that instead of from the JPEG.

What WebP quality setting should I use for photos?

75–85 is the photographic sweet spot, and Auto picks within it per image. Beware the cross-format trap: WebP at 90 often lands near the source JPEG's size. Our reference measured 188.3 KB at q90 versus 110.9 KB on Auto. Higher numbers mostly buy bytes.

Do all browsers support WebP in 2026, including Safari?

Effectively all: about 97% globally. Safari has decoded WebP since 14 (2020), Chrome and Firefox for over a decade, Edge likewise. The stragglers are museum-grade browsers and a few embedded webviews. An img fallback covers them if you care.

Should I use WebP or AVIF for my website now?

Serve both in one picture element: AVIF first, WebP as the fallback. AVIF is smaller. Our reference photo measured 78.7 KB as AVIF versus 110.9 KB as WebP. If you must pick one, WebP's extra reach edges it for long-tail audiences, while AVIF wins on pure bytes.

How do I bulk convert JPGs to WebP for WordPress?

Drop up to 50 JPGs, download one ZIP with filenames preserved, and upload to the Media Library. WordPress has served WebP natively since 5.8. For ongoing automation rather than one-off migration, that is exactly what our API is for.

Can I upload WebP product images to Shopify?

Yes. Shopify accepts WebP uploads, and its CDN negotiates formats per visitor anyway. For product photography, the bigger wins are consistent dimensions and sensible quality. Batch-convert your masters here at one setting and every listing stays uniform.

How do I convert JPG to WebP under 100 KB?

Set Max file size to 100 KB in Advanced settings before converting. That is a hard cap, met by quality search and never overshot. It turns the converter into a compressor at the same time, which no other converter in this space offers.

Does WebP support transparency and animation?

Both. WebP carries alpha transparency, which matters when you convert from PNG rather than JPG, since JPG has none to preserve. It also carries animation as the modern GIF replacement. Converting a JPG produces a standard still WebP that every browser and CMS handles.

Will switching to WebP improve my Core Web Vitals?

If images dominate your LCP, yes. A hero that drops from 400 KB to 250 KB loads visibly earlier on slow connections. Convert the images in your critical path first. The per-file measured savings in the tool tell you exactly which conversions moved the needle.

How do I convert WebP back to JPG?

Use the reverse pair, WebP to JPG. It exists precisely because sharing WebP outside browsers still stings, and it converts singles or batches back to the format everything opens. Round-tripping costs a generation each way, so keep originals when you can.

What happens to my files?

We keep nothing. We process your files and wipe them automatically, never archive them, never reuse them. We strip EXIF from outputs by default, and one checkbox keeps it. No account is required.

blinkimg

Convert JPG to WebP

Convert a JPG to WebP to keep the same photo at a smaller file size for the web. Free online, no signup.

– / –

Drop images or browse

JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB

HEIC

PNG

JPEG

AVIF

WEBP

Advanced settings1 on

QualityAuto

SmallerAutoBetter

Auto tunes each image.

Max file size

A hard cap for “under 50 KB” portals.

Max resolution

Empty side keeps the ratio. Never enlarges.

Keep EXIF metadataOff by default. We strip camera and GPS data.

One real file, before and after

JPEG, 184 KB — A real result from this exact operation: 184 KB in, 108 KB out. Drop your own file and the meter reports yours.

WebP, 108 KB — A real result from this exact operation: 184 KB in, 108 KB out. Drop your own file and the meter reports yours.

The 25–34% claim, measured honestly

Everyone quotes Google's range. Nobody shows their own numbers. Here are ours, on a 188.3 KB reference JPEG:

Encode	Size	vs source JPEG
WebP (Auto)	110.9 KB	−41%
WebP (quality 80)	131.9 KB	−30%
WebP (quality 90)	188.3 KB	0%
AVIF (Auto), for comparison	78.7 KB	−58%

Re-encoding an already-compressed JPEG saves less than fresh encodes from clean sources. That is why the per-file readout in the tool matters more than any published range, ours included.

Note the q90 row: WebP at JPEG-style high quality can land at or above the source size. The cross-format quality trap in one line: WebP 80 ≈ JPEG 90 in appearance. Don't transfer the number, transfer the look.

How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.

The WordPress / Shopify migration, step by step

For a one-off migration: batch 50 originals here → one ZIP → upload to the Media Library. WordPress serves WebP natively since 5.8, and Shopify accepts it and negotiates via CDN. We preserve filenames so re-linking is mechanical. Convert in priority order: hero and above-the-fold images first, gallery pages second, thumbnails last or never. Ongoing automation, where every new upload converts without you thinking, is the job of the API and the WordPress plugin. They share this exact engine.

Or skip a generation: WebP vs AVIF in 2026

The same source measured 110.9 KB as WebP and 78.7 KB as AVIF. AVIF is simply the smaller format now, at ~95% browser support to WebP's ~97%. The professional answer is both, via <picture>: AVIF source first, WebP second, original as the img fallback. JPG to AVIF runs the same batch flow for the first rung.

When not to convert

The saving measured under ~10%? The JPEG was already well-compressed. Keep it. A format change for single-digit savings isn't worth the re-encode.
Email attachments and documents? Office, email clients and print pipelines still prefer JPEG. WebP is a web-delivery format. Keep JPEG for interchange.
The original export still exists? Encode WebP from the original, not from the JPEG. That is one lossy generation instead of two.

Questions, answered

Short answers specific to this page. The tool above settles most of them in a second.

How much smaller is WebP than JPEG in practice?: Google's figure is 25–34% at equal quality. That holds for fresh encodes from clean sources. Re-encoding an already-compressed JPEG yields less, sometimes nothing. Our tool shows the measured result per file, so you convert where it pays and skip where it doesn't.
Does converting JPG to WebP lose quality?: Any lossy re-encode costs a generation. The cost is small at sensible settings and invisible in normal viewing. The compare slider shows your file at 100% zoom before you commit. When the original photo or export exists, encode WebP from that instead of from the JPEG.
What WebP quality setting should I use for photos?: 75–85 is the photographic sweet spot, and Auto picks within it per image. Beware the cross-format trap: WebP at 90 often lands near the source JPEG's size. Our reference measured 188.3 KB at q90 versus 110.9 KB on Auto. Higher numbers mostly buy bytes.
Do all browsers support WebP in 2026, including Safari?: Effectively all: about 97% globally. Safari has decoded WebP since 14 (2020), Chrome and Firefox for over a decade, Edge likewise. The stragglers are museum-grade browsers and a few embedded webviews. An img fallback covers them if you care.
Should I use WebP or AVIF for my website now?: Serve both in one picture element: AVIF first, WebP as the fallback. AVIF is smaller. Our reference photo measured 78.7 KB as AVIF versus 110.9 KB as WebP. If you must pick one, WebP's extra reach edges it for long-tail audiences, while AVIF wins on pure bytes.
How do I bulk convert JPGs to WebP for WordPress?: Drop up to 50 JPGs, download one ZIP with filenames preserved, and upload to the Media Library. WordPress has served WebP natively since 5.8. For ongoing automation rather than one-off migration, that is exactly what our API is for.
Can I upload WebP product images to Shopify?: Yes. Shopify accepts WebP uploads, and its CDN negotiates formats per visitor anyway. For product photography, the bigger wins are consistent dimensions and sensible quality. Batch-convert your masters here at one setting and every listing stays uniform.
How do I convert JPG to WebP under 100 KB?: Set Max file size to 100 KB in Advanced settings before converting. That is a hard cap, met by quality search and never overshot. It turns the converter into a compressor at the same time, which no other converter in this space offers.
Does WebP support transparency and animation?: Both. WebP carries alpha transparency, which matters when you convert from PNG rather than JPG, since JPG has none to preserve. It also carries animation as the modern GIF replacement. Converting a JPG produces a standard still WebP that every browser and CMS handles.
Will switching to WebP improve my Core Web Vitals?: If images dominate your LCP, yes. A hero that drops from 400 KB to 250 KB loads visibly earlier on slow connections. Convert the images in your critical path first. The per-file measured savings in the tool tell you exactly which conversions moved the needle.
How do I convert WebP back to JPG?: Use the reverse pair, WebP to JPG. It exists precisely because sharing WebP outside browsers still stings, and it converts singles or batches back to the format everything opens. Round-tripping costs a generation each way, so keep originals when you can.
What happens to my files?: We keep nothing. We process your files and wipe them automatically, never archive them, never reuse them. We strip EXIF from outputs by default, and one checkbox keeps it. No account is required.

Related conversions

Every route in and out runs on the same engine and the same rules. Each card is its own page.

Ready when your file is

Drop it in above. The meter reports the exact saving before you download anything.

Compress now