Build a repeatable batch image workflow

Choose the order before choosing the quality

Image operations are not always interchangeable. Cropping before resizing changes the pixels used for the final aspect; converting to JPG before a transparency-dependent step can flatten the background; compressing before another canvas operation can add an unnecessary lossy generation.

A dependable web recipe usually resizes first, converts once, applies final compression, then removes metadata. Add a watermark at the point where its size and placement are easy to predict.

Preflight the batch instead of failing halfway

PixHandy checks file count, byte size, decoded dimensions, output geometry, recipe schema and required watermark assets before execution. Source-dependent warnings explain transparency loss or redundant steps while there is still time to edit the plan.

One unusually large image can need far more memory than the rest. Keep browser tabs under control and split a batch when the preflight says the combined work is unsafe.

Save the plan, not the private images

The saved browser recipe contains operation settings, not your source images. Exported recipe JSON is portable and versioned, so it can be reviewed before import and reused on another device without a PixHandy account.

Image-watermark assets must be supplied again when an imported plan depends on one. This keeps the recipe portable and text-only.

Verify output as a set

Download a few individual results before creating the ZIP, then inspect the archive manifest and one image from each important source category. Focused batch watermarking applies one shared treatment; privacy blur deliberately keeps separate reviewed regions for every image.

• Confirm dimensions and aspect ratio.
• Check transparency or the chosen JPG background.
• Read small text and watermarks at final size.
• Compare total input and output bytes without treating size as the only quality measure.