Optimize · Bulk processing
Batch Editor
One operation, every image. Resize, compress, convert, watermark or rename a whole folder — there's no 30-file cap here, because there's no server.
Built to delete the 30-file cap
If you've ever resized a product catalogue or compressed a wedding album online, you know the routine: upload 30 files, wait, download, repeat ten times — or pay. The cap exists because every image you upload costs the site server time. This batch editor moves the work to the only machine that should ever see your photos anyway: yours. Drop in 300 images and the only difference from 3 is how long your own CPU hums.
Five operations, one pass
- Resize — cap the longest side (perfect for web galleries), set an exact width, or scale by percent. Aspect ratio is always preserved.
- Compress — re-encode everything as JPG or WebP at your chosen quality and watch the per-file savings tally up.
- Convert — normalise a mixed folder to PNG, JPG, WebP, BMP or GIF in one go.
- Watermark — stamp your name or brand on every image, scaled to each photo's size, at any corner or centred.
- Rename — turn IMG_4023.JPG chaos into product-1.jpg, product-2.jpg with {n} and {name} patterns.
Each file shows its own progress and result size, failures are reported per-file without stopping the run, and the finished set downloads as a single zip — assembled in your browser too. For one-off edits with finer control, the dedicated resize, compress and watermark tools go deeper.
Common questions
Is there really no file limit?
None. Memory on your device is the practical ceiling — hundreds of normal photos are fine.
Do all files get the same settings?
Yes — that's the point of batch. Settings like watermark size scale relative to each image so results look consistent.
What happens to files that fail?
They're marked in the list and skipped; the rest of the batch continues and zips normally.