Image Batch Splitter (Inspire)

When you generate four images at once, ComfyUI hands them to you as a single batched IMAGE - one wire carrying all four. Usually that's fine. But sometimes you want them apart: send image 1 down one branch, image 2 down another, composite them into a grid, or run different post-processing on each. Image Batch Splitter is the node that pulls a batch into individual images so you can route them separately.

It's a plumbing node, plain and simple, but it fills a real gap - ComfyUI's default is to keep batches fused, and once you want per-image branching there's no clean built-in way to fan them out. This is that fan-out.

How it works

You give it a batched IMAGE and a split_count, and it divides the batch into that many separate outputs. Per the pack's docs, the node adds one output slot for each split_count, and anything beyond the count spills into a "remained" output - so with split_count of 4 and a batch of 6, you get four individual images plus a remainder batch of the extra two. Each output carries the IMAGE type, ready to wire wherever you need it.

The inputs and outputs that matter

• images - the batched IMAGE to split.
• split_count (default 4) - how many individual outputs to create. Set this to how many images you want peeled off into their own slots. The node's output slots update to match.

The output type is IMAGE - one per split, with the leftover going to the remainder slot. Wire each to its own downstream branch: separate save nodes, an image-combiner for a grid, per-image upscales, whatever you're routing.

Installing it

Ships in the Inspire Pack by Dr.Lt.Data, author of ComfyUI Manager and the Impact Pack - mainstream, well-kept tooling. Via ComfyUI Manager: search ComfyUI Inspire Pack, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Inspire-Pack

then restart. No dependencies or downloads. There's a LatentBatchSplitter (Inspire) sibling that does the same thing for LATENT batches if you need to split before decoding.

Common issues

My batch is bigger than split_count and I lost images. They're not lost - they're on the remainder output. Check that slot, or raise split_count to match your actual batch size so every image gets its own slot.

split_count is bigger than my batch. Then some output slots have nothing to emit. Match split_count to how many images you actually generated to avoid empty branches.

I wanted to keep them together. Then you don't need this node - leave the batch fused. Splitter is specifically for when you need per-image routing; if your downstream handles batches fine, skip it.

Nodes won't load after install. Check the terminal log - the recurring Inspire Pack cause is a version mismatch. Update Inspire Pack and Impact Pack together and restart.