How to Batch Convert Images to WebP

Converting a folder of images one at a time is repetitive, especially when every file needs the same format and dimensions. The LeetTools Image Converter can process a mixed batch of PNG, JPEG, WebP, and AVIF files in a browser. Choose WebP once, apply one quality setting and optional resize limit, then download the results separately or together in a ZIP.

Each supported source is decoded and rendered as a new still image. The batch shares one format, quality setting, and resize limit. For animation, explicit lossless encoding, or other export controls, choose a workflow that supports those requirements.

Choose a batch workflow

Google's cwebp manual documents an explicit -lossless option and a command for each input file. Use a script to apply it to a batch when you need that control. Its documented inputs do not include AVIF, and it does not support animated PNG or WebP input.

Batch-convert images to WebP

1. Open the Image Converter.
2. Drag images into the drop area or choose Add Images. You can add more than one selection to the same queue.
3. Under Output Format, select WebP.
4. Set Quality for the whole batch. The current default is 86%, and the available range is 5% to 100%.
5. Keep Original to retain each image's pixel dimensions, or select Resize and enter a maximum edge from 64 to 8000 pixels.
6. Select Convert Images and keep the tab open while the queue is processed.
7. Review each result's dimensions, file size, and displayed size change.
8. Use Download beside an individual image, or choose Download ZIP to save the complete batch as converted-images.zip.

Each output keeps the source basename and replaces its extension with .webp. For example, header.final.png becomes header.final.webp. If two items would have the same name inside the ZIP, the ZIP builder adds a numeric suffix so one result does not overwrite the other.

Choose a WebP quality setting

WebP as a format supports both lossy and lossless compression, as well as transparency. The current converter does not provide a separate lossless switch. Its quality slider passes a value to the browser's Canvas encoder, which then decides how to encode the WebP.

Start with the 86% default and inspect representative results rather than assuming one number is correct for every image. Lower values can reduce file size but may introduce visible changes around fine text, hard edges, gradients, or detailed textures. Higher values may retain more detail but can produce a larger file.

The quality value is a preference, not a cross-browser measurement. The HTML Standard explicitly allows implementations to interpret “quality” somewhat differently. A file created at 80% in one browser is therefore not guaranteed to match the bytes, appearance, or size produced at 80% in another browser.

Selecting 100% also does not request the format's mathematically lossless mode. If lossless WebP is a requirement, use an encoder that exposes an explicit lossless option and verify the output, rather than treating the end of this slider as a lossless guarantee.

Resize the batch by maximum edge

Choose Original when the existing pixel dimensions are required. Choose Resize when the images are larger than the destination needs—for example, when preparing photos for a site that displays them at a smaller size.

The maximum-edge option preserves aspect ratio. For a 4000 × 2000 image with a 1600-pixel maximum edge, the output is 1600 × 800. An image already within the limit is left at its original dimensions; the converter does not enlarge it to reach the selected value.

The same maximum applies independently to each file, so portrait and landscape images can remain in one batch. Their longest sides are limited while their proportions are retained.

Resizing and compression solve different problems:

• Resize reduces the number of pixels when a source exceeds the selected maximum edge.
• Quality controls the preference passed to the WebP encoder.
• Using both can reduce output size more than changing either setting alone, but the result still needs visual inspection.

What the conversion preserves—and what it does not

The converter creates a new still image from rendered pixels. It is not a container-level copy of the original file.

The official WebP container specification defines optional animation, color-profile, EXIF, and XMP chunks. Support for those features in the format does not mean a Canvas redraw carries them from the source. In particular, the HTML rules for creating an ImageBitmap from animated image data use a default image or a single frame, so this tool should not be used to preserve an animated WebP or animated AVIF.

Re-encoding an image that is already WebP can introduce another lossy generation and may make the file larger. Keep the source files until the new batch has been checked and accepted by the destination workflow.

Browser support and AVIF input

The file picker accepts PNG, JPEG, WebP, and AVIF MIME types, but the converter does not bundle a separate decoder for every format. The browser must be able to decode each selected source. AVIF input is therefore the most likely of the listed types to vary with browser capability; a file can be allowed by the picker and still fail during decoding.

WebP display support and WebP Canvas export are also separate capabilities. Google's current WebP overview lists native WebP support in major browsers, while the Canvas API asks the browser to serialize the rendered bitmap in the requested type. The HTML Standard permits PNG output when a requested Canvas format is unsupported. Image Converter checks the returned format and reports an error if the browser substitutes PNG, so it does not download a PNG with a .webp extension. Use a browser that can encode WebP, and test one result in the intended viewer or publishing system before converting a large batch.

An unreadable or unsupported source is marked with an error when files are added and is skipped when the valid items are converted. An error that occurs later during conversion can stop that run. Remove the problematic item, confirm that the browser can open it, or convert it to another supported input format before retrying.

Understand the 48-megapixel output limit

Each converted output is limited to 48 million pixels. The check uses output width multiplied by output height, not the compressed file size. An 8000 × 6000 output is exactly 48 megapixels, while an 8000 × 8000 output is 64 megapixels and is rejected.

The maximum-edge control allows values up to 8000, but that range does not override the 48-megapixel rule. If a nearly square image still exceeds the limit at an 8000-pixel edge, choose a lower maximum edge and run the batch again.

The 48-megapixel check is not a promise that every smaller job will fit in memory. The browser may hold decoded source pixels, Canvas data, output blobs, previews, and ZIP data during the workflow. Very large files or a long queue can still exceed the resources available to the tab. Split a heavy job into smaller batches or use a desktop encoder when browser memory becomes the limiting factor.

What local processing means

The selected source bytes and converted outputs stay in the browser-side conversion workflow. Image decoding, resizing, Canvas export, result previews, and ZIP creation happen on the device; LeetTools does not receive those image files to perform the conversion.

The page can still make normal website requests for code, fonts, analytics, or other site resources. “No upload” describes how the converter handles the selected image data, not a claim that opening the web page creates no network traffic.

Verify the WebP batch

Before deleting originals or publishing the converted files:

1. Open several outputs, including the smallest and largest source images.
2. Confirm the expected dimensions and check that portrait and landscape files kept their proportions.
3. Zoom in on text, faces, gradients, and transparent edges for compression artifacts.
4. Compare the displayed output size with the source size; WebP output is not guaranteed to be smaller for every image.
5. Test one file in the actual CMS, app, or recipient workflow that will consume it.
6. Download and open the ZIP before discarding the individual results or source files.

If the destination requires PNG instead, use the WebP-to-PNG workflow. If several screenshots need to become one canvas rather than separate converted files, use the Image Stitcher before or after choosing the final delivery format.

The practical recommendation

Use Image Converter for a reasonably sized batch of PNG, JPEG, WebP, or browser-decodable AVIF images when one WebP quality setting and an optional proportional resize are enough. Download one representative output first, verify its appearance and compatibility, then save the complete ZIP. Use a dedicated desktop encoder for lossless-mode control, animation, metadata-preserving work, or batches that exceed browser resources.