One image is a click; two hundred images is a workflow problem. Product catalogs, event photos, scanned archives, and website migrations all eventually demand batch processing — and it does not require desktop software or trusting a server with your files.
Batch-capable tools
These converters accept multiple files in one run, processing sequentially in your browser: Compress Image, PNG to JPG, JPG to PNG, JPG to WEBP, WEBP to JPG, and HEIC to JPG. Select a folder’s worth, set the quality once, and download the results as they finish.
Batch strategy
Sort by destination first. Web images, print images, and archive masters need different treatments — separate them before processing, not after. Test on three files. Run a small sample at your chosen settings, inspect, then commit the full batch. Sequence the operations: convert format → resize → compress, per the optimization pipeline.
Browser batch limits, honestly
Local processing means your machine does the work: a 500-photo batch on an old laptop will take time, and enormous originals consume memory. For thousand-file jobs, break into batches of 50–100. The reward for the constraint is absolute: as the safety guide explains, files that never upload can never leak.