Image converter · JPG to WebP JPG to WebP converter: lighter photos for your site
WebP usually stores a photo in fewer bytes than JPEG at a similar visual quality. Add your JPGs, compare the result with the original and download WebP files ready for your website. Nothing is uploaded.
- Stays on your device
- Built for page speed
- Batch and ZIP download
Convert JPG to WebP
Output is set to WebP at quality 80 and the original size. Type a max width to shrink camera photos as well.
80 is a good starting point for photos.
Lowers quality step by step until the file fits. Works for WebP, JPEG and AVIF.
JPEG has no transparency, so transparent areas are filled with this colour.
Only when format and dimensions stay the same.
No images yet. Choose, drop or paste images, or try the sample photo.
Before
—
After
—
Saved
—
Before and after
Drag across the image or use the slider. Left of the line is the original, right is the compressed version. Zoom in on edges, text and skies, where compression shows first.
What resizing does to a 12-megapixel phone photo
A 4032 × 3024 photo shrunk to fit a square limit. Pixel count drives file size and decoding memory, so resizing usually saves more than any quality setting.
| Max width and height | Output size (px) | Pixels removed | Memory once decoded |
|---|---|---|---|
| Original | 4,032 × 3,024 | — | 46.51 MB |
| 2,560 px | 2,560 × 1,920 | −60% | 18.75 MB |
| 1,920 px | 1,920 × 1,440 | −77% | 10.55 MB |
| 1,200 px | 1,200 × 900 | −91% | 4.12 MB |
| 800 px | 800 × 600 | −96% | 1.83 MB |
Decoded memory = width × height × 4 bytes (one byte each for red, green, blue and alpha), whatever the file size. File sizes depend on the picture, so the tool measures them instead of guessing.
Version v1.0Updated Update history
What to expect from JPG to WebP
The saving depends on the photo and on how the JPG was saved. The tool measures it for each file.
Size and saving
Camera photos usually shrink noticeably. A JPG that was already compressed hard may save little, or grow; the row turns red then.
A second lossy step
The JPG has already lost some detail and WebP compresses again. Convert from the best JPG you have, not a copy of a copy.
Quality 80
A common starting point for photos on the web. Compare at real size and go lower until you see a difference.
Dimensions
Conversion keeps the pixel size. A 4000-pixel photo is still too big for most pages: set a max width of 1600–1920.
Removing EXIF and GPS data comes with the conversion: the WebP contains only pixels.
Convert JPG to WebP in three steps
The page opens with WebP output, quality 80 and no size limit.
-
1
Add the JPG files
Click to choose, drop them on the box or paste a photo. Up to 60 at once.
-
2
Set quality and size
Keep quality 80 or adjust it in the comparison view; type a max width if the photos come straight from a camera.
-
3
Download
Download each WebP or a ZIP of all of them, named like the originals with .webp.
Why smaller images make the largest paint faster
Largest Contentful Paint (LCP) is the time until the biggest image or text block in the viewport is drawn. web.dev splits it into four parts: time to first byte, resource load delay, resource load duration and element render delay. When the largest element is an image, its file size sets the load duration.
- Good LCP: 2.5 seconds or less for at least 75% of page visits (web.dev)
- File size depends on pixel count × bytes per pixel; resizing cuts the first, quality and format the second
- This tool draws each image onto a canvas, scales it in steps of at most half for sharper results, then calls
canvas.toBlob(type, quality) - Compression does not fix a slow server or a late-discovered image: set
widthandheight, do not lazy-load the LCP image and considerfetchpriority="high"
| Format | Type | Transparency | Best for |
|---|---|---|---|
| WebP | Lossy or lossless | Yes | Website photos and graphics; supported by current browsers |
| AVIF | Lossy | Yes | Smallest files for photos; shown only if your browser can encode it |
| JPEG | Lossy | No | Email, upload forms and anything that refuses WebP |
| PNG | Lossless | Yes | Screenshots and UI that must stay pixel-exact; rarely gets smaller |
One phone photo, three decisions
A 4032 × 3024 photo for a blog post whose content column is 800 CSS pixels wide.
| Step | Decision | Result |
|---|---|---|
| 1. Dimensions | 800 px column × 2 for sharp screens → max width 1600, or 1920 for a full-width hero | At 1920: 1920 × 1440, 77% fewer pixels |
| 2. Format | WebP at quality 80 for the page; keep a JPEG copy only if a platform rejects WebP | Typically a large saving on photos; the tool shows the exact size |
| 3. Check | Compare at real size; look at sky gradients and fine text | Lower the quality until artefacts appear, then step back |
| Memory | Decoded size of the original vs a 1200-pixel version | 46.51 MB vs 4.12 MB: what a phone must hold in memory to paint it |
Pixel counts and memory are exact arithmetic; compressed file sizes depend on the picture, so measure them with the tool rather than trusting a rule of thumb.
Where image compression goes wrong
Most oversized images on websites are not under-compressed; they are simply too big.
Uploading the camera original
A 4000-pixel photo shown 800 pixels wide makes every visitor download and decode five times the pixels in each direction. Resize before you compress.
Re-compressing a JPEG again and again
Every lossy save adds artefacts. Keep the original and compress from it, not from the last exported copy.
Saving photos as PNG
PNG is lossless, so photos stay huge. Use PNG for flat screenshots; for photos use WebP, AVIF or JPEG.
Lazy-loading the main image
loading="lazy" on the largest image above the fold delays LCP. Lazy-load images further down the page instead.
See whether your images slow real visitors down
Compressing images is the fix; real-user data tells you which pages need it. TapCub's script measures the same Largest Contentful Paint this page explains, on your visitors' devices.
Core Web Vitals at p75
LCP, INP and CLS for each page at the 75th percentile, the same threshold web.dev uses, collected from the first page load of each visit.
Learn moreSlowest pages first
Pages and templates sorted by LCP, so you compress the images that cost the most visitors first.
Learn morePages and sources together
Compare speed with traffic and conversions on the same pages to decide where an image fix matters.
Learn moreImage compression questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I convert JPG to WebP?
Add the JPG photos here. Output is already WebP at quality 80; each photo converts as soon as it loads, and you can download the batch as a ZIP.
Is WebP better than JPG for websites?
For most photos WebP gives a smaller file at similar visual quality, and current browsers all display it. Keep a JPG where a platform does not accept WebP.
Why did my WebP come out larger than the JPG?
The JPG was probably already heavily compressed. Lower the quality, set a max width, or keep the original JPG.
Does JPG to WebP remove EXIF data?
Yes. The output contains only pixels, so GPS location, camera model and date taken are removed. Rotation is applied to the pixels first.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Measure the speed your visitors actually get
Add TapCub's script and see LCP, INP and CLS for every page from real visits, next to traffic and conversions.