Batch image exports: order, previews and failed files

Reviewed 8 October 2026 · PixelDesk practical documentation

Batch processing is useful when several images need the same change. It is safest to start with two or three representative files, check their outputs, and then repeat the action for the remaining set. Different source shapes and transparency can produce different results with identical settings.

Choose one task for this batch

PixelDesk's batch tool offers Compress, Resize, Convert format and Text watermark. One selected action runs on each image. It is not a pipeline that crops, adjusts colors and resizes every file together.

For a mixed set, include a portrait, landscape and transparent graphic in your initial trial if those file types occur in the job. The sample set is useful for learning controls, but it is not a substitute for checking your own export requirements.

Check ordering and shared settings

1. Select up to 12 supported still images and inspect the displayed filenames.
2. Use the filename arrows if the order needs changing; file pickers may sort selections differently.
3. Choose the action and review its controls, output format and filename prefix.
4. Inspect the first-image live preview, then process the batch.
5. Check every successful output, including dimensions, file size, transparency and watermark placement.
6. Download individual results or the ZIP containing successful exports.

The preview describes the first image

A preview gives quick feedback, but it is not a promise that every file will look like the first one. A centered square crop can cut off a subject in a portrait source and a different subject in a landscape source. For a watermark, a fixed text size may look small on a large photo and large on a small one.

If composition varies significantly, split the job into groups with similar proportions or use the individual crop and watermark tools for the exceptions. Fit can retain a complete picture when padding is acceptable.

Account for memory, not just file count

Inputs are limited to 12 files, 20 MiB per file and 60 MiB combined. Successful archive output is limited to 120 MiB. A compressed file still needs decoded pixel memory during editing, so a phone may struggle with a set that fits the byte limits.

Close unnecessary browser tabs, reduce source dimensions or use a smaller batch if processing fails. Successful files remain available when another input fails. Cancel processing when the settings are wrong, then check the retained results rather than assuming a complete set was created.

Choose the output for its destination

JPEG flattens transparent areas onto the chosen background. PNG encodes the decoded pixels losslessly and ignores the quality slider. WebP can be useful when accepted by the destination. Compression may increase the size of an already efficient file; compare the actual bytes before replacing it.

Selected image contents stay in browser processing. Downloads are new copies; retain the source files and inspect the ZIP contents before sharing. For one combined overview instead of separate exports, use a contact sheet.

Prepared by Operance Labs · Report a documentation issue