FormatDrop
How-To Guide

How to Convert JPG to WebP

Switching from JPG to WebP can cut your image file sizes by 25–35% with no visible quality difference to most viewers. Smaller images mean faster page loads, better Core Web Vitals, and lower bandwidth costs. All modern browsers support WebP.

Step-by-step instructions

  1. 1

    Squoosh app (easiest, browser-based)

    Open squoosh.app. Drag your JPG into the browser window. In the right panel, select 'WebP' from the codec dropdown. Set quality to 80 (a good default). Compare the left (original JPG) and right (WebP) panels — zoom in to check for quality differences. Click the download button to save the WebP file.

    Go to converter
  2. 2

    cwebp command-line (single file)

    Install the WebP tools from Google. On Mac: `brew install webp`. Run: `cwebp -q 80 photo.jpg -o photo.webp`. The quality range is 0–100; 75–85 is the sweet spot for photos. Check file size: `ls -lh photo.jpg photo.webp` to compare sizes.

  3. 3

    Batch convert a folder of JPGs

    On Mac/Linux Terminal: `for f in *.jpg; do cwebp -q 80 "$f" -o "${f%.jpg}.webp"; done`. On Windows (PowerShell): `Get-ChildItem *.jpg | ForEach-Object { cwebp -q 80 $_.FullName -o ($_.BaseName + '.webp') }`.

  4. 4

    FFmpeg (if already installed)

    FFmpeg can convert images too: `ffmpeg -i input.jpg -quality 80 output.webp`. For batch: `ffmpeg -pattern_type glob -i '*.jpg' output_%03d.webp`. Note: FFmpeg's WebP output may differ from cwebp — test quality before using in production.

Why convert JPG to WebP?

Converting JPG to WebP is a standard web optimization technique that reduces image bandwidth by 25–35%. With all major browsers now supporting WebP, there's no compatibility reason to keep JPG for new web projects.

Your files never leave your device

FormatDrop runs the conversion engine entirely inside your browser using WebAssembly. No file upload. No server. Nothing stored. You can verify this by opening DevTools → Network tab and watching: zero upload requests.

Frequently asked questions

Is WebP always smaller than JPG?
Not always, but usually. WebP is typically 25–35% smaller than JPG at equivalent visual quality. Very low-quality JPGs (high compression) can sometimes be smaller than the equivalent WebP, but at quality levels that produce good-looking images, WebP almost always wins on file size. The advantage is most pronounced for complex photos with smooth gradients.
Should I replace all my JPGs with WebP?
For web delivery, yes — WebP is the better format for modern browsers. Keep the original JPG files as masters (don't delete them). Serve WebP to modern browsers and provide JPG as a fallback using the `<picture>` element. Many CDNs and image optimization services (Cloudflare Images, Imgix, Cloudinary) auto-convert to WebP based on browser support.
What quality setting should I use for JPG to WebP conversion?
Quality 80 is the standard recommendation for photos: it produces images indistinguishable from the original JPG to most viewers at 25–35% smaller size. Quality 75 is acceptable for background images or thumbnails where quality is less critical. Quality 90+ preserves fine detail for images that will be closely inspected. Always compare before and after — zoom to 100% and inspect for artifacts.
Convert JPG to WebP Now — Free

No account. No upload. Works in any browser.