WebP Converter: JPG & PNG to WebP

1. Drop your files on the upload area or click it to browse. You can add up to 20 images per batch, up to 25 MB each; JPG, PNG, BMP, GIF and AVIF files are accepted.
2. Leave the format on WebP. PNG and JPG are also available as output if you need to go the other way.
3. Set the quality slider. It runs from 10% to 100% in steps of 10 and starts at 80%. Use Apply to All to give every image the same settings, or adjust a single image on its own card.
4. Click Convert All, then compare the original and converted sizes shown for each file.
5. Download files one by one, or all of them as a single ZIP.

The conversion is done by your own browser, so nothing is uploaded. Two practical consequences: pixel dimensions stay exactly as they were, and metadata such as EXIF camera data is not carried over to the new file. To change dimensions first, use the image resizer.

There is no single correct number. Start from the table, convert, and look at the result at the size it will be displayed.

The slider affects WebP and JPG output. PNG is lossless, so the quality value makes no difference when PNG is the output format. Avoid converting the same picture several times: each lossy pass removes a little more detail, so always start from the original.

Current browsers all display WebP, so most sites can use it directly in a normal <img> tag. If you must support very old browsers or other software that reads your HTML, the <picture> element lets the browser choose the first format it understands:

<picture>
  <source srcset="/images/team-photo.webp" type="image/webp">
  <img src="/images/team-photo.jpg" alt="Our team at the 2025 conference"
       width="1200" height="800" loading="lazy">
</picture>

• The alt, width and height attributes go on the <img>, not on <source>.
• Setting width and height reserves space and prevents layout shift while the image loads.
• Do not use loading="lazy" on the main image at the top of the page; it delays the largest element.
• Keep the file name descriptive. Google indexes WebP images the same way as JPG and PNG.

AVIF is the newer format. At the same visual quality it often produces smaller files than WebP, especially for photos at low bitrates, and it supports HDR and wide colour. WebP encodes and decodes faster and has been supported for longer, including by older phones, image editors and content management systems.

A sensible rule: use WebP as your default because it works almost everywhere with no extra effort. Add AVIF as an extra <source> above the WebP one if your site is image-heavy and your build pipeline or CDN can generate it for you. This tool can read AVIF files where your browser supports the format, but it writes WebP, PNG or JPG only.

Animated GIFs

The converter draws each image once, so an animated GIF comes out as a still picture of its first frame. Keep the GIF, or better, replace it with a short muted video.

Small PNG icons and logos

A PNG icon of a few kilobytes has little left to save, and a lossy WebP version can soften its edges. For logos and icons, SVG is normally the best choice; for favicons, use PNG files from the favicon generator.

Images that are already heavily compressed

Re-encoding a low-quality JPG at a high WebP quality can give you a file that is no smaller, or even larger, with no visual gain. Check the size shown after conversion and keep the original if it wins.

Files meant for email, print or social sharing previews

Some email clients, print workflows and link-preview scrapers still expect JPG or PNG. For those uses, keep a JPG and compress it with the image optimizer instead.

If the output is not really WebP

Because your browser does the encoding, the result depends on it. A browser that cannot encode WebP hands back a PNG instead. The tool checks what the browser really produced: it tells you when that happens and saves the file with the matching .png extension rather than a misleading .webp one. If you see that message, convert in a current version of Chrome, Edge or Firefox.