Morphio
Menu

Bulk PNG to WebP and Other Image Batches

For bulk PNG to WebP, start with the PNG conversion route and select your PNG files there. JPG/JPEG and AVIF use their own routes, so choose the source format before adding a batch.

Choose the format you already have

PNG to WebP

For screenshots, graphics and images with transparent pixels. Keep a source copy when sharp edges or exact colors matter.

Convert PNG files

JPG or JPEG to WebP

For photographs and other opaque images. Changing the format cannot recover detail previously discarded by JPEG compression.

Convert JPG files

AVIF to WebP

For static AVIF images. This route does not promise animated AVIF decoding or preservation of features outside the supported image path.

Convert AVIF files

Convert one source format at a time

  1. 1

    Sort by actual image format

    Separate PNG, JPG/JPEG and AVIF inputs. Renaming a suffix does not change the encoded image, so investigate a file that is rejected despite its name.

  2. 2

    Open its conversion route

    Select the corresponding files on that page. Processing begins automatically after selection; follow the current size, count and usage information shown there.

  3. 3

    Check each completed result

    Review the per-file status and preview. Save the results, then reopen a representative photograph, transparent graphic and any file that looked unusual.

Several outputs, not one animation

Bulk PNG to WebP produces a separate result for each supported input. A folder of numbered PNGs does not automatically become an animated WebP, and this page does not offer a frame order or timing editor.

Grouping files is useful for organization, but it does not make their output sizes equal. Dimensions, image content and the selected direction determine the result. There is no promise that every WebP will be smaller than its source or meet a particular kilobyte target.

Check the features you need to keep

Look closely at transparent edges, small lettering and gradients. PNG alpha and opaque JPG input have different requirements; an opaque source does not gain useful transparency simply because the destination supports it. Metadata handling also depends on the target path rather than a universal preserve-all rule.

Keep failed items separate from completed ones. A corrupt image or a file above the current limit needs its own resolution; do not infer success from another result in the same batch.

When another app needs JPG or PNG

If the destination later rejects your WebP, convert WebP to JPG for an opaque image or convert WebP to PNG when a static image needs transparency. Save the originals as well so repeated format changes do not become your only editing source.

Questions and answers

Practical answers for this task.