Convert JPG and PNG to WebP
Make lighter images for your website by turning JPGs and PNGs into WebP, lossy or lossless.
- Processed on your device. Your photos are never uploaded. How we know
- Free, no sign-up, no watermark
Drop JPG/PNG images to convert to WebP
Drop files, paste with Ctrl+V, or choose them from your device.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents. What happens to your files
How to convert images to WebP
Every byte an image saves is a byte your visitors don’t have to download, and WebP is one of the simplest ways to save them. Google designed it for the web: it handles photos with lossy compression, graphics with lossless compression, and transparency in either mode.
This converter runs Google’s own libwebp encoder in your browser. Drop in product shots, blog images or interface screenshots, pick lossy or lossless, and download WebP files ready to upload to your site or content system.
- 1
Load JPGs or PNGs
Drag in a single hero image or a whole media folder. Files are recognized by their contents, so odd extensions don’t matter.
- 2
Pick lossy or lossless
Use lossy (quality 80) for photographs. Switch to lossless for logos, icons, diagrams and screenshots with text.
- 3
Download WebP files
Save them individually or as one zip, then upload them in place of the old JPGs and PNGs.
What this tool does
- Lossy WebP, quality 80 by default
- Lossless mode for graphics and screenshots
- Transparency kept in both modes
- Input: JPG, PNG, AVIF, HEIC or WebP
- Whole folders at once, zipped
- Embedded color profile retained
- Location or all metadata removed
Worked example: a photo and a logo
Measured with libwebp, the encoder this page uses, in Node:
| Source | Before | WebP |
|---|---|---|
| Test photo, 1600 × 1200 JPG | 398,618 bytes | 102,892 bytes, lossy quality 80 (−74%) |
| Flat-color graphic with transparency, 640 × 480 PNG | 3,484 bytes | 944 bytes, lossless (−73%) |
For comparison, re-saving the same photo as a quality-80 JPG gave 115,774 bytes, so the WebP was about 11% smaller at the same setting number (the two quality scales are not identical, so always judge by eye). The graphic tells the other half of the story: in lossy mode it grew to 5,136 bytes, bigger than the original PNG. Flat colors belong in lossless mode. (1 KB = 1,000 bytes.)
How the WebP encoder treats your image
Your JPG or PNG is decoded to pixels in a Web Worker and handed to libwebp, compiled to WebAssembly. In lossy mode, MDN explains, WebP uses predictive coding based on the VP8 video codec: it predicts each block from its neighbors and stores only the difference, at a precision set by the quality slider. In lossless mode it instead finds and reuses repeating data, so every pixel survives exactly.
Transparent areas are carried into the WebP in both modes, and the color profile is embedded so colors match the original. Choose what metadata to keep; for public web images, removing it all is usually the tidy choice.
Lossy or lossless: pick by what’s in the picture
Photographs: lossy. Natural texture hides small errors, and the savings are large. Google reports lossy WebP files as 25–34% smaller than comparable JPEGs at equal SSIM quality.
Logos, icons, charts, screenshots: lossless. Sharp edges and flat color compress very well without loss, and Google puts lossless WebP at about 26% smaller than PNG. To cut sizes further, first scale images to the width your layout actually shows with the image resizer. The guide to compressing images for the web has a full checklist.
Browser support and fallbacks
Google lists native WebP support in Chrome, Safari, Firefox, Edge and Opera, and MDN describes WebP as broadly supported in the latest versions of major browsers. For a typical website you can serve WebP directly. If you also need to reach very old browsers or software, keep the original JPG or PNG and offer both with the HTML <picture> element, which lets the browser pick the first format it understands.
Want even smaller files for modern browsers? Compare the result with AVIF from the same image, and read our format comparison before choosing.
Good to know
- Lossy mode can enlarge simple graphics. Our test logo grew from 3,484 to 5,136 bytes; lossless shrank it to 944.
- Converting an already-compressed JPG adds a second round of loss. Start from the highest-quality original you have.
- Not every app opens WebP files for editing. Keep your originals as the master copies.
- Animated GIFs aren’t accepted here; this tool converts still images.
- Images above 50 megapixels (24 on phones) trigger an offer to resize to 6000 px on the long edge first.
What happens to your files
Processed on your device. Your photos are never uploaded. PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
Unpublished product photos and client artwork can be converted here before launch without leaving your machine: libwebp runs as WebAssembly in your browser tab. The WebP files are created in memory and saved through your browser’s normal download. PixWrench receives no copy.
Related tools and guides
Questions people ask
What quality should I use for WebP?
The default of 80 suits most photos on websites. Go higher for large hero images where detail matters, and use lossless mode for graphics and text.
Does WebP support transparency?
Yes, in both lossy and lossless modes. Transparent areas from your PNG are kept.
Do all browsers support WebP?
Current versions of Chrome, Safari, Firefox, Edge and Opera all display it. For very old software, offer a JPG or PNG fallback with the <picture> element.
Should I use WebP or AVIF?
AVIF is often smaller still, but encodes much more slowly. WebP is quick to make and very widely supported. You can serve both, with AVIF first and WebP or JPG as the fallback in a <picture> element.
Can I convert WebP back to JPG or PNG?
Yes, with WebP to JPG or WebP to PNG.
Will converting to WebP help my page speed?
Smaller images download faster, and in our test the WebP was 74% smaller than the JPG it came from. How much your page gains depends on how much of its weight is images.
Sources and review
- Google for Developers — An image format for the Web (WebP)
- MDN — Image file type and format guide (WebP)
- MDN — The picture element
Page reviewed by the PixWrench team · How it works · Changelog · Report a problem