WebP is mainly a delivery format: it exists so web pages can ship smaller images. This tool re-encodes your JPG as lossy WebP at quality 85. That is a second round of lossy compression on an image that was already compressed, so the sensible workflow is to keep your original JPG and use the WebP as a copy for the website.
or use the button below to add files
Drag & drop a file here
or use the button below to choose a file
File selected
Accepts JPG · up to 20 MB each
Processing your file…
This usually only takes a moment.
Your file is ready
·
Your file is processed on our server and deleted automatically afterward — see the privacy note below.
Overview
About JPG to WebP
What happens to your image
The JPG is decoded and re-encoded as lossy WebP at quality 85. This tool has no lossless WebP mode and no quality slider. Width and height are unchanged. A JPG has no transparency, so the WebP is fully opaque; nothing is added. Sideways-stored phone photos are rotated upright using their EXIF flag, and the EXIF data itself, including any GPS position, is not carried into the WebP.
How much smaller? Two local examples
| Test image (generated for this test) | JPG | WebP at quality 85 |
|---|---|---|
| 1200 × 800, gradients and noise | 392 KB | 257 KB (about 34% smaller) |
| 1000 × 600, gradients and noise | 244 KB | 165 KB (about 32% smaller) |
These figures come from images we generated and converted locally with this tool. They are examples only: not a benchmark, not a typical customer result and not a guaranteed ratio. The saving depends on the image and on how the original JPG was encoded. If the WebP you get back is not meaningfully smaller than the JPG, there is no reason to use it.
The quality cost, honestly
Because the source is already a lossy JPG, the WebP is a lossy copy of a lossy file. At quality 85 the difference is often hard to see at normal viewing size, but fine texture, skin and text in photos are where you should look, at 100% zoom. If it matters, keep the original.
Where WebP works and where it does not
Current versions of Chrome, Edge, Firefox and Safari display WebP. The trouble starts outside the browser: older desktop software, some email clients, print services and upload forms that validate file extensions. If the destination says "JPG or PNG", do not upload a WebP. Sites that need both commonly serve WebP with a JPG fallback.
When to keep the JPG
- Archiving, printing, or sending to people whose software you do not know
- Any upload form that lists accepted formats without naming WebP
- When the WebP comes out about the same size as the JPG
The JPG vs PNG vs WebP guide covers where each format makes sense. If you want a smaller JPG without changing format, see the JPG compressor.
Compatibility
Supported Formats
Accepts JPG and JPEG (.jpg, .jpeg). Output is a static WebP. Limits: 20 MB per file, 12,000 px per side and 40 megapixels.
Guide
How to Use JPG to WebP
- Choose a JPG or JPEG file (up to 20 MB).
- Click "Convert JPG to WebP".
- Download the WebP and compare its size with the original. Keep the JPG as your master copy.
Highlights
Features
- Lossy WebP at quality 85 One fixed setting. There is no lossless mode and no slider.
- Original untouched Your JPG is not modified. You download a separate WebP file.
Applications
Use Cases
- Producing a lighter copy of a photo for a web page, while keeping the JPG as the master
- Testing whether WebP actually saves bytes on a particular image before changing a site's assets
- Meeting a platform recommendation to serve WebP images
Good to Know
Limitations
Output is always lossy WebP at quality 85. There is no lossless option, no quality control and no animation. Because the source is already a JPG, the file is compressed lossily twice. EXIF data and embedded colour profiles are not carried over, and no colour conversion is applied before the profile is dropped, so an image in a wide-gamut space such as Adobe RGB or Display P3 can look different afterwards.
Files are processed on our servers and are not shared with third parties. Files are deleted as soon as processing or download finishes. Any leftover temporary file is removed automatically by our cleanup process within the configured retention period (60 minutes). See our Privacy Policy for full details.
Support
Frequently Asked Questions
Will converting JPG to WebP reduce quality?
A little, yes. The WebP is a second lossy pass over an already compressed JPG. At quality 85 it is often hard to see at normal size, but check detailed areas at 100% zoom if quality matters.
How much smaller will my WebP be?
It depends on the image. In our local tests, two generated images came out about 34% and 32% smaller. That is an example, not a benchmark: check the actual result and do not assume a fixed percentage.
Can I count on every browser and app opening WebP?
Current Chrome, Edge, Firefox and Safari can display it. Older software, some email clients, print services and upload forms may not. If a destination lists accepted formats, check that WebP is on the list.
Should I delete the original JPG after converting?
No. Keep it. The JPG is the better master, and you can create new WebP copies from it later. Converting WebP back to JPG adds another lossy pass.
Does the WebP get a transparent background?
No. A JPG has no transparency, so the WebP is fully opaque.
Keep Going
Related Tools
- JPG to PNG Convert a JPG to a lossless PNG copy. It will not look sharper, and it will be larger.
- WebP to JPG Convert a static WebP to JPG for apps and sites that refuse WebP. Transparency becomes white.
- PNG to WebP Convert a PNG to lossy WebP at quality 85 while keeping transparency.
- JPG Compressor Re-save a JPG at fixed quality 75 for a smaller file. Pixel dimensions stay the same, and some files do not get smaller.
- WebP Compressor Re-encode a static WebP as lossy WebP at fixed quality 75, keeping transparency. Lossless and already-small files can get larger.
- Image Resizer Resize a JPG, PNG or WebP to a width or height in pixels. The aspect ratio is locked unless you unlock it.