jpg · webp · quality · local

Convert JPG to WebP for the web

Re-encode JPEGs as WebP for noticeably smaller files at the same visual quality. Adjust the slider and download locally.

JPG to WebP
Source
—
no file
Output
—
—
Quality
85%
webp
Saved
—
ratio
Quality:85%
input · image

image/jpeg · runs locally · nothing uploaded

output · preview
Preview appears here
Quick Start

How it works

Pick an image, tune the options, then download the result. Everything runs in your browser.

  1. 01

    Pick a JPG

    Drop or select a JPEG. It stays on your device.

    Files stay in memory as an HTMLImageElement — the original bytes are never uploaded, and EXIF metadata is preserved until you explicitly transform it.

    uploadcanvaslocaldecode
    input · bytesjpg · loaded
    photo.jpg
    loaded · decodedcanvas · ready
  2. 02

    Tune quality

    Adjust the slider — 85% is a common WebP web default.

    Encoder quality is exposed where the format supports it — JPEG and WebP get a 0–1 quality slider; PNG is lossless. Options re-render the canvas immediately.

    qualityoptionslive previewencoder
    quality · tunable85% · live
    encode(q=0.85)
    options applied · liveencoder · live
  3. 03

    Inspect savings

    WebP usually beats JPEG by 20–40% at equivalent quality.

    Pixel work runs on the Canvas 2D context — drawImage resamples with the browser’s bilinear filter and getImageData/putImageData back per-pixel passes.

    sizerenderCanvas 2Dpreviewpx-perfect
    savings · resampled0% · px-perfect
    jpg > webp
    preview · livepx-perfect
  4. 04

    Download WebP

    Save the WebP for faster web delivery.

    Downloads ship via a hidden anchor with an object URL — no server round-trip, and the file on disk is untouched. The output filename inherits a sensible suffix.

    exportdownloadblobclient-sideobject URL
    ok · blobready · saved
    photo.webp
    shipped · ready to shipsuccess
Pro tips

Browser-only image work that scales

Convert with quality control

JPEG/WebP let you pick a 0–1 quality. Default 0.92 is a good compromise of size and visible quality.

PNG isn’t free

Use PNG only for transparency or sharp edges. For photos, WebP is smaller at the same perceived quality.

Strip EXIF for privacy

Photo EXIF often contains GPS, camera model, and timestamps. Strip before sharing public uploads.

Watch the colour profile

Convert to sRGB before web export. Wide-gamut images render oversaturated in non-managed browsers.

AVIF when it’s available

AVIF beats WebP on size at the same quality. Detect support via <picture> with fallbacks.

Lazy-load below the fold

Add loading="lazy" on <img>. The browser handles scheduling — no IntersectionObserver needed.

Use Cases

When to use this tool

Common workflows it speeds up.

Web hero images

Cut hero photo size for faster loads. Decoded into a Canvas 2D context — original bytes never leave the tab, so you can process customer-uploaded photos, internal screenshots, or sensitive diagrams without privacy concerns.

px-perfect

Product galleries

Lighter image grids on e-commerce. Encoders expose quality 0–1 where the format supports it (JPEG, WebP); PNG and AVIF stay perceptually lossless. Pick 0.85 for web, 0.95 for archival, 0.7 for thumbnails.

quality-tunable

Blog posts

Smaller article images. Pair with the EXIF Stripper before sharing user-uploaded photos publicly. Camera serial numbers, GPS coordinates, and timestamps often hide in image metadata and leak more than the picture itself.

format-aware

CDN savings

Lower bandwidth bills. Output preserves colour profile (sRGB) so it renders consistently across browsers, monitors, and print pipelines. Wide-gamut workflows can opt into Display P3 for modern Apple devices.

EXIF-safe

Mobile optimization

Less data for users on the go. Re-runs only on option changes, never on window resize, so the canvas stays responsive on large images. drawImage uses the browser's bilinear filter for fast resampling.

client-side

PWA assets

Shrink offline cached images. Downloads as .png, .jpg, .webp, or .avif with the correct MIME so editors apply native handling on save. The filename inherits a sensible suffix derived from the input.

compression-ready
FAQ

Frequently asked questions

Yes — Chrome, Firefox, Safari 14+, and Edge all support WebP natively.
WebP is lossy at the chosen quality. At 85+ the difference is usually invisible.
Usually 20–40% smaller than JPEG at equivalent visual quality.
JPEG has no transparency to keep. For transparent sources use PNG to WebP.
No. Conversion happens locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!