Many websites serve images as WebP because the files are smaller. When you right-click and save, you get the .webp file. Current browsers open it, but some older photo viewers, office software, print services and upload forms do not. Converting to JPG solves that.
Why you end up with WebP files
Quality and file size
Most WebP images on websites are already lossy. Converting to JPG decodes them and encodes again at quality 0.9, which adds a small second round of compression. At that quality the difference is rarely visible, but the JPG is often larger than the WebP, because WebP usually needs fewer bytes for the same look. The conversion is about compatibility, not size.
Transparency and animation
- Transparency: WebP can be transparent, JPG cannot. Transparent pixels are filled with white. Use WebP to PNG to keep them.
- Animation: animated WebP files convert to a single still image, taken from the first frame the browser draws.
Settings and output
- Quality: JPG is written at quality 0.9 where the format uses a quality setting. There is no slider on converter pages; use the Image Compressor if you want to choose the quality yourself.
- Size limits: images longer than 4096 px on either side are scaled down to 4096 px. If a converted file would be over 10 MB, it is reduced in steps until it fits.
- Batches: add several files; three are converted at a time. One file downloads directly, two or more come as a ZIP.
- Metadata: EXIF data (camera, date, GPS) and colour profiles are not carried into the new file.
Where the processing happens
Files are converted in your browser and are not uploaded.