Process many images at once — resize, compress, convert, rename
Apply one set of operations to a whole folder of images and download the results as a single ZIP. Every file is processed on your device; nothing is uploaded.
or drag & drop images here, or paste from your clipboard
PNG, JPG, WebP, AVIF, GIF, BMP, TIFF, HEIC, SVG
Your images are processed on your device and are not uploaded to PNGful.
How it works
- 1
Add your images
Drop a whole selection at once — mixed formats and sizes are fine. Each file appears in the queue with its own status.
- 2
Configure the operations
Combine resizing, compression, format conversion, metadata removal and renaming. The same settings apply to every file in the batch.
- 3
Run the batch
Files are processed a few at a time to keep memory in check. Watch per-file progress, retry anything that fails, or remove files you don't need.
- 4
Download the ZIP
When the batch finishes, download everything as one ZIP — or save individual files if you only need a few.
Common uses
- Shrinking a whole shoot of photos before archiving or sharing
- Converting a folder of mixed formats into consistent JPGs or WebPs
- Resizing product photos to a store's required dimensions in bulk
- Stripping metadata from every photo before publishing a set
- Renaming event photos into a clean numbered sequence
- Preparing dozens of blog or CMS images with one set of rules
How batch processing stays fast and stable
Processing a hundred images in a browser is mostly a memory problem: decoding a single large photo can take hundreds of megabytes of RAM. PNGful solves this with bounded concurrency — only a few files are decoded and processed at any moment, and each one's memory is released before the next begins. Big batches don't crash the tab; they just take proportionally longer.
Every file in the queue has its own status, so a batch is never all-or-nothing. If one image fails — a corrupt file, an unsupported variant — the rest keep going, and the failed entry shows an error with a retry button. You can also remove files from the queue at any point, before or after processing.
Renaming happens as part of the same pass. Add a prefix or suffix to every filename, or switch to sequential numbering to turn a jumble of camera filenames into a clean, ordered set like photo-001, photo-002 and so on. The final ZIP contains the renamed, processed files exactly as you configured them.
Good to know
- There's no hard cap on file count, but very large batches are limited by your device's memory and simply take longer — the bounded queue trades speed for stability.
- One set of settings applies to the whole batch; files needing individual treatment are better served by the single-image tools.
- Animated GIFs and animated WebPs are processed as a single still frame.
- The ZIP stores images without further compression — they're already compressed, so expect the ZIP to be about the sum of its files.
Your images stay private
Your images are processed on your device and are not uploaded to PNGful.All processing happens locally using your browser's own image engine — there is no upload step, no server-side queue, and nothing to delete afterwards. Read more in our privacy policy.
Frequently asked questions
How many images can I process at once?
There's no hard cap. The queue processes a few files at a time and releases memory between them, so the practical limit is your patience rather than your RAM — hundreds of images work fine, they just take longer. If an individual file is too large to decode safely, the tool tells you instead of freezing.
What happens if one file fails?
The rest of the batch continues unaffected. The failed file is marked with an error in the queue, and you can retry it — useful for transient memory pressure — or remove it and download everything else. A single bad file never costs you the whole batch.
Does the ZIP compress my images further?
No. JPG, PNG and WebP files are already compressed, so re-compressing them inside the ZIP would waste time for almost no savings. The ZIP stores your images as-is; it's a convenience for downloading many files at once, not an extra compression step.
How does renaming work?
You can add a prefix or suffix to every original filename, or replace names entirely with sequential numbering (photo-001, photo-002, …) in the order the files appear in the queue. Extensions are set automatically to match the output format, and the names you see in the queue are the names inside the ZIP.
Are my images uploaded anywhere?
No. Every operation — resizing, compression, conversion, metadata removal, renaming, even building the ZIP — happens locally in your browser. Nothing leaves your device at any point.
Was this tool helpful?