Image batch processing pipeline

No. The entire pipeline runs locally in your browser; images are never uploaded — good for processing large sets of private photos.

In a fixed order: resize → watermark → round → final encode/compress, with each step individually toggleable. This ensures the watermark sits on the resized image and compression happens last for the best quality-to-size tradeoff.

JPG has no alpha channel, so the rounded-away areas fill with black. To keep transparent rounded corners, set the final format to PNG or WebP.

There's no artificial count limit — your device's memory and time are the constraints; more and larger images take longer. For very large images, enable the “limit max width” step first.