Convert up to 200 queued images with shared browser-side settings, download one ZIP, and verify entry count, filenames, dimensions, and sample quality.
What this page is for
Batch conversion applies one shared output configuration to multiple image files and packages multi-file results into a ZIP archive.
Keep batch settings consistent across files that share the same delivery requirement.
Large source images can use significant memory during conversion.
Use a dedicated converter for files that need different settings from the rest of the batch.
Batch conversion applies one shared output setup to a group of still images and places the results in a ZIP. It is useful when a collection needs the same format and maximum dimensions, while the dedicated converters remain better for one-off files that need individual attention.
How to convert your file
1Add a representative subset first and remove any file that does not preview correctly.
2Choose PNG, JPG, or WebP and set the shared dimensions and quality.
3Check the naming pattern so files will remain distinguishable inside the ZIP.
4Create the ZIP, keep the tab open, and inspect several outputs before processing the full collection.
Export settings
Shared settings
Every file receives the same output format, quality, maximum dimensions, and appearance adjustments.
File limit
The interface accepts up to 200 items, but practical capacity also depends on pixel dimensions and available memory.
Naming
Use the original base name or a pattern containing {name}; a fixed name can create collisions inside a batch.
ZIP output
Packaging avoids a separate download prompt for every converted image.
Batch check
Count the ZIP entries and compare that count with the successful inputs. Check for duplicate names, then open samples from the largest, smallest, portrait, landscape, and transparency-sensitive sources.
Before you download
Large batches and high-resolution sources can exceed browser memory even when the item count is below 200.
One settings profile is applied to every file; mixed requirements should be split into separate batches.
Animated files are treated as still images and browser-dependent input formats can fail to decode.
Questions and answers
Can each image use different settings?
No. Split the files into separate batches or use a dedicated converter for individual treatment.
Why can a batch slow down?
Each source must be decoded, rendered, encoded, and held for ZIP packaging in the same browser session.
Are the source images added to the ZIP?
No. The archive contains the converted outputs created by the selected settings.
