How to Convert JPG to WebP — Every Method Explained (Free & Fast)

If your website serves JPG images, you are leaving performance on the table. Google's WebP format delivers 25–34% smaller file sizes at the same visual quality — and every modern browser supports it. A 200 KB product photo becomes 130 KB. Multiply that across a site with hundreds of images and you have a measurable boost in page speed, Core Web Vitals scores, and bandwidth savings.

This guide covers every method to convert JPG to WebP: a free browser-based tool that never uploads your file, Google's own cwebp command-line tool, Photoshop, GIMP, and WordPress plugins. We also cover quality settings, batch conversion, HTML fallbacks, and how much you can realistically expect to save for different image types.

Why Convert JPG to WebP?

WebP was created by Google in 2010 specifically to replace JPEG and PNG on the web. It uses the VP8 video codec for lossy compression and a derivative of the PNG predictor for lossless compression — producing images that are significantly smaller than equivalent JPGs.

Here is why the switch matters in practice:

• File size savings of 25–34%. Google's own benchmarks show WebP lossy images are 25–34% smaller than comparable JPEG images at the same SSIM (structural similarity) quality index. For lossless, WebP is 26% smaller than PNG.
• Largest Contentful Paint (LCP) improvements. LCP — the time until the largest image on a page finishes loading — is one of Google's Core Web Vitals signals used in search ranking. Smaller images download faster, directly improving LCP.
• Google's recommendation. Google Lighthouse and PageSpeed Insights explicitly flag JPG and PNG images with the audit "Serve images in next-gen formats" and recommend WebP as the fix. Passing this audit removes a common reason for failing the performance section of PageSpeed.
• Bandwidth savings. A site serving 500 images per day at an average of 200 KB each sends 100 MB of image data daily as JPG. Converting to WebP reduces that to roughly 65–75 MB — saving 25–35 MB per day in egress costs and faster load times for users on mobile or slow connections.
• Universal browser support. As of 2024, over 97% of global browser usage supports WebP: Chrome (since 2014), Firefox (since 2019), Edge, Opera, and Safari 14+ (September 2020). You can safely serve WebP to virtually all users today.

What Happens Technically During JPG to WebP Conversion?

Understanding the conversion process helps you make better decisions about quality settings and use cases.

JPG uses the Discrete Cosine Transform (DCT) compression algorithm. When you save a JPG, pixel data is converted into frequency coefficients, and low-frequency detail is preserved while high-frequency detail (fine texture, sharp edges) is discarded according to the quality setting. The result is a lossy file — some pixel data is permanently removed.

When you convert JPG to WebP in lossy mode, the file is decoded back to raw pixels and then re-encoded using the VP8 codec. VP8 is more efficient than DCT — it groups pixels into 4×4 or 16×16 macroblocks and uses inter-frame prediction techniques borrowed from video encoding to reduce redundancy more aggressively than JPEG's algorithm.

The practical implication: because you are decoding and re-encoding, there is a second generation of lossy compression. If your source JPG was already heavily compressed (quality 60 or lower), converting it to WebP at low quality will compound the artifacts. Always convert from the highest-quality JPG available, or better yet, from the original uncompressed source.

WebP also supports lossless mode — which performs lossless prediction and entropy coding (similar to PNG's DEFLATE but more efficient). Lossless WebP is 26% smaller than PNG on average, but it will always be larger than a lossy WebP for photographic content. Use lossless WebP for images that contain text, logos, or screenshots where every pixel must be exact.

Quality Setting Guide — What 80 vs 90 vs 100 Actually Means

Every WebP encoder accepts a quality parameter from 0 (maximum compression, lowest quality) to 100 (minimum compression, highest quality). Unlike JPG quality where the relationship between the number and file size is non-linear, WebP quality behaves similarly — higher numbers produce larger files with less compression artifacts.

Our recommendation: Start with quality 82 for most websites. Run a visual comparison between your source JPG and the WebP output at 100% zoom on screen. If you see no visible difference, that quality setting is your sweet spot. If you spot ringing or banding artifacts, bump up to 85.

Method 1: Convertlo Browser Tool — No Upload, Free, Batch Conversion

Method 2: cWebP Command-Line Tool

cWebP Command Syntax

# Convert a single JPG to WebP at quality 82
cwebp -q 82 input.jpg -o output.webp

# Lossless conversion (no quality loss)
cwebp -lossless input.jpg -o output.webp

# Higher quality (85) with slower but better encoding (method 6)
cwebp -q 85 -m 6 input.jpg -o output.webp

# Batch: convert all JPGs in current folder (Linux/macOS bash)
for f in *.jpg; do
  cwebp -q 82 "$f" -o "${f%.jpg}.webp"
done

# Batch: Windows PowerShell
Get-ChildItem *.jpg | ForEach-Object {
  cwebp -q 82 $_.FullName -o ($_.BaseName + ".webp")
}

The -m flag sets the compression method from 0 (fastest, larger file) to 6 (slowest, smallest file). For production pipelines where encoding time matters, use -m 4. For maximum compression offline, use -m 6. The default is -m 4.

Method 3: Squoosh by Google

Method 4: Adobe Photoshop

Method 5: GIMP — Free Alternative

Method 6: WordPress Plugins — Automatic Conversion

Batch Conversion — Converting Hundreds of JPGs at Once

If you have a large folder of images to convert — a product catalog, a photo library, a set of blog images — manual conversion is impractical. Here are the three fastest options for batch JPG to WebP conversion:

Lossy vs Lossless WebP — When to Use Each

Serving WebP with HTML Fallback — the <picture> Element

Even though over 97% of browsers support WebP, you may want to provide a JPG fallback for the small percentage of users on older browsers (primarily very old Safari on older iOS devices). The HTML <picture> element handles this elegantly — the browser picks the first format it supports and ignores the rest.

<!-- Serve WebP to modern browsers, JPG to older ones -->
<picture>
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="Description of the image" width="800" height="600">
</picture>

<!-- With responsive sizes for different viewports -->
<picture>
  <source
    srcset="photo-400.webp 400w, photo-800.webp 800w, photo-1200.webp 1200w"
    sizes="(max-width:600px) 400px, (max-width:900px) 800px, 1200px"
    type="image/webp">
  <img
    src="photo-800.jpg"
    srcset="photo-400.jpg 400w, photo-800.jpg 800w, photo-1200.jpg 1200w"
    sizes="(max-width:600px) 400px, (max-width:900px) 800px, 1200px"
    alt="Description of the image"
    width="800" height="600"
    loading="lazy">
</picture>

If you use a CDN (Cloudflare, Fastly, AWS CloudFront), you can configure it to automatically serve WebP to browsers that send Accept: image/webp in their request headers, without changing any HTML. Cloudflare's Polish feature and Cloudinary's f_auto parameter both do this automatically.

How Much File Size Will You Save?

Savings vary significantly by image content. Photographs with lots of color variation save more than flat-color graphics. Here are typical real-world results converting common image types from JPG to WebP at quality 82:

Real savings depend on the specific image and the quality of the source JPG. An already heavily compressed JPG (saved at quality 60) will show smaller savings because much of the redundant data is already gone. A high-quality JPG (quality 90+) has the most room to benefit from WebP's more efficient algorithm.

Frequently Asked Questions