Batch Save Multi

Batch Save Image writes one picture into one folder. Batch Save Multi writes up to eight - each with its own condition and its own destination, all derived from a single source file. If your night's sorting job is "refined versions into refined/, full-body shots into full/, close-ups into close/, everything the anatomy check hated into broken/", this is the node that does it in one pass instead of four save nodes with four routers.

How the slots work

slots decides how many slots are shown (1–8). Each slot has three things:

• image_N - the picture to save. Leave it unconnected and the slot copies the original file byte for byte, untouched. That's how you file the source alongside the variants you just generated without re-encoding it.
• gate_N - the condition. It accepts a BOOLEAN, an integer count (fires above 0), or a MASK, which fires when at least mask_min_area of the pixels are set (default 0.001, i.e. 0.1% of the frame - the right kind of number for a SAM3 aux mask on a small garment print). No gate wired means the slot always writes.
• subdir_N - the target folder, relative to base_dir, or to the source picture's own folder when base_dir is empty. Absolute paths work too. Defaults read refined, slot_2, slot_3… so rename them.

route decides what happens when more than one gate fires: all_matches writes to every slot that fired, first_match only to the first. Combined with gate ordering that's a cheap priority system.

The original, and the fallback

• fallback_dir (default unsorted) gets a copy of the original when gates are wired but none of them fired. Empty it and the node does nothing in that case instead.
• original decides the fate of the source file after the slots are written: keep, move, copy into original_dir (default done), or delete. The delete is permanent - no recycle bin, no undo.
• original_when is the safety catch worth knowing: on_match only handles the original when at least one gate fired, so pictures nothing has an opinion about stay exactly where they are. On a folder where most images won't match anything, that's the difference between a tidy run and a wipe.

The pack's own documentation adds one more reassurance about ordering: the original is handled last, and skipped entirely if a slot failed to write. An error in the middle never costs you the only copy.

Outputs and install

saved_paths (one path per line), matched (which slots fired, as text), matched_count, and report for the log or a sidecar. It's an output node, so it always executes.

cd ComfyUI/custom_nodes
git clone https://github.com/ping1979ping/comfyui-FVMtools

Restart, or install through ComfyUI Manager by searching comfyui-fvmtools. No extra dependencies for this node; source_path from Batch Load Image is needed for unconnected slots, for the original handling, and as the base for relative folders.

Where it bites

The image_N behaviour is genuinely surprising to read the first time: an unconnected image input is not "skip this slot", it's "copy the original". If you wanted a slot disabled, leave the gate unconnected and the image connected - or just don't wire the slot's folder into anything you care about.

delete plus original_when = always plus a folder that is also your archive is a combination that will eventually hurt. Test the routing on a copy of ten images first.

And mask_min_area is measured over the whole image, not over the subject. A mask that fires confidently on a small label inside a 4K frame can sit under 0.1% and be treated as a miss. Drop it to 0.0001 for small-region gates, or feed the gate a boolean verdict from a detector instead of the raw mask.