Skip to main content

JPG to WebP converter

Convert JPG images to WEBP format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

This pair is a recompression, and it is worth being clear about what that means. Your JPEG is decoded back into pixels - artifacts and all - and then compressed again by a different codec. The second pass cannot restore anything, and in principle it can add its own errors on top of the first encoder's. In practice WebP is efficient enough that at the default quality of 90 the result looks like the JPEG while weighing noticeably less, which is exactly why sites migrate their photo libraries this way.

Key facts about JPG to WebP converter

Key facts about JPG to WebP converter
Nature of the changeA full re-encode between two lossy codecs: JPEG's DCT blocks are decoded, then VP8 intra prediction compresses the pixels again.
Generation lossReal but usually invisible at quality 90. Each further round trip between lossy formats compounds, so keep the original JPEG as your master.
Typical size deltaA 20-40 percent reduction against the source JPEG at matching visual quality; a 1.2 MB photo commonly lands between 700 and 900 KB.
Chroma handlingLossy WebP stores colour at half resolution in both directions, much as a typical JPEG does, so saturated red edges are the first place to look for softening.
TransparencyWebP supports alpha, but a JPEG has none to give - the output is opaque, and converting does not create a cut-out.
MetadataCamera tags, GPS position and the colour profile are not transferred; the WebP contains the pixels and nothing else.
HEIC inputiPhone .heic and .heif files are accepted here too, decoded to JPEG data in the tab first and then encoded as WebP.
Browser supportEvery browser in current use decodes WebP, and both Windows Photos and macOS Preview open it. Some older desktop tools and upload forms still do not.
BatchTwenty files per run at up to 500 MB each, with multiple results bundled into converted-webp-files.zip.

What happens to your file

Both halves of the round trip happen inside this tab: the browser's JPEG decoder produces the pixels, a canvas holds them, and canvas.toBlob with image/webp calls the WebP encoder that ships inside your browser. Nothing is queued, nothing is stored and no image bytes appear in any network request - the only reason a conversion takes time is the CPU work in front of you. Metadata is not stripped by a separate pass either; it simply never reaches the canvas.

About this tool

  1. 1

    Load the JPGs

    Drop up to twenty .jpg, .jpeg, .heic or .heif files. Mixed batches are fine, and the HEIC ones simply take a moment longer.

  2. 2

    Pick a quality

    90 is the default. For photo galleries, 80 usually saves a further chunk of bytes while staying hard to tell apart at normal viewing size.

  3. 3

    Downscale oversized photos

    A 4000-pixel-wide camera file displayed at 1600 px wastes bandwidth no codec can recover; the presets fix that before encoding.

  4. 4

    Convert and compare the numbers

    The result panel reports the original and new sizes and the percentage saved, so you can see whether the trade was worth it.

Specs & compatibility
Input and outputTakes .jpg and .jpeg only (image/jpeg) and returns .webp with the image/webp type; any other extension is refused before decoding.
Conversion pathJPG to WEBP runs in three steps: an <img> element decodes the JPEG, baseline or progressive, in the browser; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/webp type returns the finished file.
Browser supportThe JPEG side decodes in every browser ever shipped, while writing the WebP works in Chromium browsers and Firefox, and where the type is unsupported the canvas specification makes the browser return PNG bytes under the .webp name.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the WEBP encode, max-dimension presets from 3840 down to 200 px resize the JPG first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty JPG files per run at 500 MB each; one result downloads as a single WEBP, several as converted-webp-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized JPG fails before any WEBP bytes exist.
  • Avoid converting the same picture back and forth between JPG and WebP - each pass is another generation of loss, and the damage accumulates quietly.
  • If the JPEG was already saved at a low quality, converting it gains little: WebP has to spend bits reproducing the existing blockiness.
  • Serving WebP with the original JPG as a fallback source in a picture element covers the handful of old clients that cannot decode it.
  • For screenshots and text-heavy images, pushing the slider to 100 switches Chromium's encoder into lossless mode, which is sharper than any high-quality lossy setting.
  • Cutting page weight on a site whose photography is currently served as JPG.
  • Shrinking a large batch of camera exports before uploading them to a portfolio or a shop.
  • Meeting a theme or a plugin that expects WebP assets without installing anything locally.
Technically yes, since one lossy codec is decoded and another re-encodes the result. At the default quality of 90 the difference is very hard to see on photographic content, because WebP spends its bits where the eye looks. The practical rule is to convert from your best original once, rather than converting a file that has already been through several passes.
Typically 20-40 percent below the source JPEG at comparable quality, with the largest wins on images the original encoder saved generously. A JPEG that was already squeezed to a low quality has little slack left, and the WebP may end up close to the same size or even slightly larger.
The format supports alpha, but the conversion has nothing to work with: a JPEG is opaque by definition, so every pixel arrives fully solid. WebP transparency is only useful when the source already has it, such as a PNG export or a design file.
No. The image is redrawn to a canvas before encoding and a canvas has no metadata, so camera model, exposure settings, timestamps and GPS coordinates are all absent from the WebP. If you need those preserved, a format conversion of this kind is not the right approach.
AVIF usually produces a smaller file at the same visual quality, but it encodes far more slowly and can only be written by Chromium browsers here. WebP encodes almost instantly, works in every browser on this page, and is accepted by more desktop software. For a large batch on a deadline, WebP is the pragmatic answer.

Related tools

View all

Need the opposite? Try WEBP to JPG

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy