JPG to WebP

1. Add your JPG photos. Use the drop area of the upload box or its browse link. The box lists JPG as its accepted type, covering .jpg and .jpeg endings, and takes up to 10 files per run.
2. Set Quality. With Output format on WebP, this is the option that counts. It takes a number from 50 to 100 and starts at 85. A lower number gives a smaller file with more visible compression, and a higher one keeps more detail.
3. Skip Background for transparency. A JPG has no transparent areas for it to fill, and WebP keeps transparency anyway, so the setting does nothing for this pair.
4. Select Convert to WebP. The photos are sent to private storage with upload progress measured in bytes. Then our servers convert them one by one while the page counts how many are finished.
5. Sign in, then compare sizes. Google or an emailed code gets you in at no cost, and there is no password. Each WebP is listed with its type and size, so you can set it against your original before you download or save anything.

Both formats are lossy and suit photographs. WebP is the newer one, and it can often store the same picture in a smaller file, which is why site owners like it. JPG is the safer choice when a picture has to open everywhere.

• Convert for pages and apps that show WebP. Current web browsers display it, so a blog, shop or portfolio can use WebP to cut the weight of its images.
• Keep the JPG for other destinations. Print orders, older software and many upload forms still expect JPG, and a WebP can be refused there.
• This is a second round of compression. The JPG has already lost detail, and WebP compresses it once more. Quality numbers from different formats are not directly comparable, so 85 in WebP does not mean the same thing as 85 in JPG. Judge the pictures, not the numbers.
• Smaller is common, not guaranteed. Unlike Compress image, Convert image does not check whether the result is smaller. Compare the sizes in the result list and keep the JPG if the WebP is not worth it.
• Hold on to the original. Your JPG is the best copy you have of that picture. Treat the WebP as something made for a particular use.

• WebP output is always lossy here. There is no lossless WebP option, and even at 100 the file is lossy.
• No transparency appears. The WebP is as opaque as the JPG it came from. To make part of a photo see-through, cut it out in an image editor.
• Grayscale turns into ordinary color data. A black-and-white JPG is saved as a regular color WebP, so the picture looks the same but is not stored as grayscale.
• Upright photos, RGB colors. A rotation flag is applied to the pixels and not written to the new file. A CMYK JPG is converted to RGB through its embedded profile when it has a usable one, and some colors can shift slightly. A multi-picture JPG, which some phones save with a depth map, is converted from its main picture.
• Details inside the JPG are left out. EXIF and XMP data, comments, the camera model and any location are not copied, and a color profile that matches the picture is kept. If a copyright notice stored in the file matters to you, keep your original, because it will not carry over.
• Names and runs. beach.jpg becomes beach.webp, one WebP per photo, with nothing zipped. A single damaged or oversized photo causes the whole run to fail. So does a photo more than 16,383 pixels on a side, which WebP cannot store; the run stops with a message explaining the limit.
• Limits. Each run takes up to 10 JPG files totaling no more than 25 MB, and each photo can be up to 40 megapixels. Pro, at $9.99 a month, suits people who convert often or save many files; the per-run limits stay the same.

To keep a JPG and only make it smaller, try Compress image, or reduce its dimensions with Resize image.