Skip to converter

JPG to WebP converter

This page re-encodes a JPEG photo as WebP, which usually gives a smaller file for the same-looking picture on a web page. It is a second lossy pass over pixels that were already compressed once, so the goal is a size win you can actually see in the preview - not a format upgrade that quietly degrades the photo.

Compression is lossy; very fine detail can soften at lower quality.

Drop files here or JPG, up to 25 MB each, 10 at a time
    Add a file to start.

    Processed on your device. Files aren’t sent anywhere.

    No sign-up. Nothing to install.

    Why move a JPEG to WebP at all

    WebP compresses photographic regions harder than JPEG, so a hero photo or a gallery image often drops a lot of weight while still looking the same at normal zoom. It also supports transparency, which JPEG does not - useful when you are replacing a PNG elsewhere, though a JPEG input has no alpha to preserve.

    The honest caveat: you are recompressing lossy data. Block artefacts and soft edges already present in the JPEG get re-encoded, and the second pass can add ringing around sharp edges. Convert a copy, view it at 100% zoom, and keep the JPEG if the WebP looks worse.

    • Good fit: photos on a site, blog images, product shots, background imagery
    • Poor fit: images with fine text, technical line drawings, anything you will edit later
    • If the JPEG is a camera original, treat it as the master and convert only the delivery copy

    Generational loss, explained plainly

    Each lossy encode throws information away. JPEG→WebP means the decoder reconstructs an approximation of the photo and the WebP encoder then approximates that approximation. Nothing from the original camera file is recovered; this route cannot undo the JPEG that was already made.

    Browser-side encoding

    The encode uses your browser's WebP encoder. If the browser cannot produce WebP, the page tells you the format is unsupported here instead of uploading the photo. Decoding JPEG is universally supported, so the input side is safe.

    Choosing a quality that does not mush the photo

    Quality runs 40 to 100 and defaults to 85. It is handed to the encoder as a setting; it is not a percentage of the original detail retained, and it has no effect on PNG output.

    For photos coming from a JPEG, staying at 85 or above is usually the safe choice, because you are already carrying first-generation artefacts. Lower values shrink the file but make skin tones blotchy and edges haloed.

    • 85-100: safest for photos, especially faces and skies
    • 70-80: decorative images where a little softening is acceptable
    • 40-60: thumbnails and placeholders
    • There is no custom background colour option on this route - JPEG input has no transparency to fill

    Size is not guaranteed to shrink

    Some JPEGs - noisy film grain, high-detail textures, already aggressively compressed files - encode to a WebP that is the same size or larger. Compare byte sizes before swapping files; this converter reports what it produced and promises no ratio.

    Scaling in the same pass

    Size is a segmented choice of Original, 75%, 50% or 25%, not a slider. Original keeps the pixel dimensions; the other steps scale the drawing with high-quality smoothing before encoding.

    Downscaling usually saves more bytes than lowering quality. A 4000px camera JPEG resized to 50% for a page column is both lighter and cleaner than a full-size low-quality WebP.

    • Original: dimensions unchanged, encoding only
    • 75%: modest trim for large photos
    • 50%: typical page-width images
    • 25%: thumbnails; text and faces lose legibility

    Limits on this route

    Up to 10 files per batch, each up to 25 MiB. The pixel ceiling is 40 megapixels, and the engine rejects an image only when both the source and the scaled output exceed it - so a 6000x7000 source downscaled to 50% still converts, while a huge source kept at Original size does not.

    What comes out of the converter

    The output is a new WebP named after your original file with the extension changed, plus reported output width and height. EXIF, GPS, camera settings and ICC profile labels are not copied, which is often desirable for privacy on published photos.

    Your source file is never modified; the result is downloaded separately.

    • Kept: pixels, output dimensions, file name stem
    • Lost: EXIF, GPS, camera model, colour profile metadata
    • Not available here: custom background colour, animation, batch zip, server-side processing

    Batch conversion locally

    Add several JPEGs and the same quality and size settings apply to all of them; each WebP downloads on its own. Everything runs in this tab, so there is no upload, no queue and no account.

    Questions

    Does JPG to WebP restore quality?
    No. Both formats are lossy, so this is a second compression pass over already-compressed pixels. Detail discarded by the original JPEG cannot be recovered.
    Will the WebP be smaller than my JPEG?
    Usually for photos, but not always. Noisy textures and heavily compressed JPEGs can produce an equal or larger WebP. Check the actual file sizes before replacing anything.
    Is transparency preserved?
    JPEG has no alpha channel, so there is nothing transparent to carry over. WebP does support transparency, which matters when the source is PNG rather than JPEG.
    What quality value should I use?
    Keep the default 85 for photos, or go higher if the subject has faces or smooth skies. Values below 70 tend to blur fine detail and blotchy gradients.
    Are camera details kept?
    No. The output is drawn from pixels, so EXIF, GPS and colour profile metadata are not transferred into the WebP file.
    Do files leave my computer?
    No. Decoding, scaling and encoding happen in your browser; nothing is uploaded and no sign-up is needed.

    Share this converter

    More sharing options