Convert JPG to WebP

Drop your JPGs below. WebP is already selected, and each photo is encoded at the lowest quality that still clears a measured target. Up to 16 MB a file as a guest or 32 MB with a free account. Free. No account, no watermark.

  • WebP already selected
  • Works in every current browser
  • Quality searched per photo
Compression Level
None
No compression, only apply settings on image
Lossless
Without any visual change in the image quality
Ultra
Max compression with some quality loss
Smart
Balance between the image quality and compression
Change Format Will allow you to convert images to different extensions
Auto WEBP AVIF PNG JPG Auto tries every format your image can be saved as and gives you the smallest one
Resize Will allow you to change the width, height or scale of images
Keep EXIF Will allow you to preserve meta data in images
Maximum file size is 16 MB per image and supported formats are: PNG, JPG, JPEG, WEBP, GIF, HEIC, HEIF, TIFF, TIF
Guests get 10 images a day, 10 left today. A free account gets 40 a day.
Delete this image?
The image and its optimized copy will be removed from storage. This cannot be undone.

Rename this image
Choose the name the optimized image downloads with. Its format stays the same.

Uploaded as

Rename the selected images
Each image gets this name and a number, counted in the order they were uploaded. Their formats stay the same.

Share this image
Choose the compression level that suits your images
Level What it promises What happens Pick it when
Lossless
Not one pixel changes in a JPEG, PNG or GIF The file is repacked, never re-encoded. JPEGs get an optimised Huffman table and progressive scan, PNGs a tighter deflate pass, GIFs a lossless gifsicle run. A lossy WebP has no repack step, so it is re-encoded at the highest quality the level allows. A sideways phone JPEG is rotated losslessly on the way through and keeps its colour profile. The one exception to the promise is a PNG or WebP tagged with a wide-gamut profile such as Display P3: its colours are converted to sRGB, so the values change but the picture doesn't. Logos, line art, anything you'll edit again, or when the file is evidence.
Smart
No visible change, targets 40 dB PSNR and a perceptual score of 70 A quality search runs per image and stops at the lowest quality that still clears the PSNR target. That answer is then scored on the SSIMULACRA 2 scale, because an average over every pixel lets a mostly flat picture through at a quality its detail doesn't deserve, and when it falls under 70 the search moves back up until it doesn't. Photos and graphics end up at different qualities because they need different ones; an image that cannot reach the targets inside the quality ceiling is encoded at the ceiling. Almost everything on a website. This is the default for a reason.
Ultra
Smallest file, targets 34 dB PSNR and a perceptual score of 50 The same two-stage search with lower targets. Fine texture softens a little; edges and text stay sharp. Thumbnails, backgrounds, email images, anything shown small or blurred anyway.
None
No compression at all Only the resize, conversion or metadata setting you chose is applied. An untouched upload comes back byte for byte. You only wanted to resize or convert, and quality is someone else's decision.

Measured, not estimated

What JPG to WebP saved on five real photos

The five JPG photographs from our showcase, converted to WebP by the pipeline your upload goes through. Look at the landscape and the food photo at Smart before you convert a whole site.

Sample Original Smart Ultra
Fjord 1800 by 1200 832 KB JPG 563 KB 32.3% smaller 297 KB 64.4% smaller
Raspberries 1800 by 1200 342 KB JPG 60 KB 82.4% smaller 25 KB 92.7% smaller
Night skyline 1800 by 1200 427 KB JPG 201 KB 53% smaller 78 KB 81.8% smaller
Canoe at dusk 1800 by 1200 387 KB JPG 101 KB 74% smaller 42 KB 89.2% smaller
Café interior 1800 by 1200 356 KB JPG 80 KB 77.6% smaller 41 KB 88.5% smaller

Sources are 1800 by 1200 JPGs at quality 92. Metadata stripped, no resize. At Smart, the landscape and the food photo came out slightly larger as WebP than they do as a recompressed JPG, which is why the full tool has an Auto format.

Is it worth it

Usually smaller. Not always.

The common claim is that WebP is 25 to 35 percent smaller than JPG. That's an average, and averages hide things. At the same measured quality, WebP won clearly on three of our five photos and lost narrowly on two. Modern JPEG encoders have closed much of the gap.

What WebP still gives you: good results at low qualities, where a JPG falls apart into blocks, and one format for photos and graphics alike. At Ultra it beat the recompressed JPG on all five samples.

Iminify runs cwebp at its slowest, most thorough setting on all but very large photos, and searches the quality per photo, measuring each candidate against your upload. A JPG source is never encoded above quality 95. Past that, a WebP only spends bytes preserving the JPG's artefacts.

What survives

What a JPG keeps on its way to WebP

  • EXIF, when you switch it on

    Stripped by default. With Keep EXIF on, the block is attached to the WebP after the encode, capture date and GPS included.

  • The right way up

    Sideways phone photos are turned upright before the orientation tag is removed.

  • Colours

    Display P3 and CMYK are converted to sRGB instead of dropped.

  • A lossless copy isn't possible

    A JPG is already lossy, so there's nothing lossless to preserve. Even at Lossless the photo is re-encoded, at a high quality. For a bit-exact smaller file, compress the JPG as a JPG.

When not to

When to skip this conversion

  • Your photos are detailed and you only need Smart. A well-compressed JPG can match WebP there, and it opens everywhere.
  • The images are going into email. Several mail clients still don't show WebP.
  • You can serve AVIF. It was smaller than WebP on every photo in our tests.

How to

JPG to WebP in three steps

  1. 1

    Drop your JPGs

    WebP is already chosen under Change Format.

  2. 2

    Pick a level

    Smart for no visible change. Ultra when the image is shown small, where WebP's lead is widest.

  3. 3

    Compare, then download

    The Compare view has a pixel difference map if you want proof, not an impression.

Questions

JPG to WebP questions

From the blog

What we've measured so far

We run the encoders on real photos and screenshots and publish the numbers: when WebP beats AVIF, what quality 80 means in each encoder, and how many kilobytes an image on a web page should weigh.

All posts
ComfyUI's Flux Dev example render of a fox-eared girl in a maid dress holding a cake, captioned: 1,215,064-byte PNG to 125,684-byte WebP, and the workflow still loads in ComfyUI.

ComfyUI PNG to JPG loses the workflow. WebP and AVIF can keep it

ComfyUI's Flux Dev example image is a PNG of 1,215,064 bytes, and the two text chunks holding its prompt and workflow take 12,240 of them. The rest is 1024x1024 pixels stored without loss. Across the 92 PNGs in ComfyUI's examples repository that carry a workflow, the text was no more than 3.32 percent of any file, with a median of 0.62 percent. Converting to JPG shrinks the file, but ComfyUI's own loader can't read a workflow back out of a JPG. A WebP or AVIF can keep it, at about a tenth of the size. We took the text-to-image examples of ten models from ComfyUI's examples repository, made smaller copies several ways, and dropped the copies back onto ComfyUI 0.37.0's canvas to see which ones still held the workflow.

6 min read
Bar chart of mozex.dev's image bytes at Lighthouse's phone size: 63.7 KB in 2 files before scrolling, 653.5 KB in 9 files after, and a worked-out 107.1 KB with its own images resized and re-encoded for the phone and the hidden one skipped.

How to find large images on a website: three tools gave us three different lists

On 22 September 2026 we loaded mozex.dev, the site of Mozex Labs, which runs Iminify, at the phone size Lighthouse emulates, and listed its images three ways: Chrome's network log, Lighthouse and a console snippet. Before any scrolling, Chrome had fetched 2 image files, 63.7 KB. After we scrolled to the bottom, it had fetched 9 files, 653.5 KB. Lighthouse's phone runs requested 7 and never the two heaviest, 340.8 KB between them. The browser's own timing data put one image at 0 bytes. So the list you can trust comes from Chrome's Network panel, taken after a scroll. Every method here works on one page at a time, so run it on the pages you care about most.

8 min read
Bar chart of one photograph in bytes: 852,461 as served, against Lighthouse's target of 45,084 at its phone slot and encodes of 47,876 (JPEG), 46,320 (WebP) and 41,735 (AVIF).

Improve image delivery in Lighthouse: what it replaced and how it counts savings

PageSpeed Insights ran Lighthouse 13.5.0 on our home page on 22 September 2026 and flagged "Improve image delivery" in the mobile report: "Est savings of 1,300 KiB". All of it came from one photograph. The fjord shot in our before-and-after comparison is on the page twice, as the 832.5 KiB original and as our own compressed copy at 555.3 KiB. Both files are 1800x1200, and the report says they're displayed at 637x425. Three later runs that day said 1,359 KiB and 364x243. If your old notes say "Serve images in next-gen formats" or "Properly size images", this is where they went: Lighthouse 13 folded four image audits into this one insight. And its savings aren't measured: each figure is arithmetic on bytes and pixels. We reproduced every number in that insight, made the file it asks for, and traced one reason the same page gets two answers.

8 min read

Convert your JPGs to WebP

Drop a photo, open Compare and judge the result with your own eyes.

Convert JPG to WebP Open the full tool