Split Batch 🆎

Split Batch 🆎 cuts an IMAGE batch in two at a frame index you pick, and sends each half down its own wire. Frames 1 through index come out as a, everything after as b. It's the surgical counterpart to the pack's Merge Batches - and the natural workflow shape is the one you can't build with a single processing node: first half of a clip through one treatment, second half through another, then rejoin. Different upscale strengths per scene, different denoise for the opening frames, peel the leading frames of a batch off for a sanity preview while the rest goes to the heavy stage.

The indexing convention is the one thing to get right. It's one-based and inclusive - frame 1 is the first frame, and index is the last frame that lands in a. So index = 10 on a 20-frame batch gives you frames 1–10 as a and 11–20 as b. That matches how people actually count frames, and it's the same convention the pack uses across its other frame-facing nodes, so you won't be translating between conventions as you move through a workflow.

How it works

An images input (a BHWC IMAGE batch) and an index integer (one-based, default 1). The outputs are a (frames 1 through index) and b (the rest). The node validates before it slices: the batch needs at least two frames, and the index has to land between 1 and count−1 so that both sides come out non-empty. If you ask for a split that would leave one side with zero frames, it refuses with a message telling you the valid range - a zero-frame IMAGE batch is invalid on any downstream wire, so refusing beats handing you a broken batch.

Install

ComfyUI Manager is the easy route: search for ComfyUI-AusBoss under Custom Nodes and hit Install, then restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ausboss/ComfyUI-AusBoss.git

Restart ComfyUI and Split Batch 🆎 sits under 🆎 AusBoss/Utility. No extra Python dependencies. Minimum ComfyUI 0.27.1, and hard-refresh with Ctrl+Shift+R after frontend updates.

Common issues

The one-based indexing is the thing people trip on if they're used to zero-based code - index = 10 means ten frames in a, not "the 10th frame onward." And the hard constraint: both sides must keep at least one frame, so a single-frame batch can't be split and an index at the very edge of the batch will error. If you want a slice that can leave an empty side (say, "everything after frame 3 of a 4-frame batch"), this node won't do it - but for real clips that's almost never what you want anyway. Pair it with Merge Batches to rejoin the two halves after their different treatments; they'll concat cleanly as long as the treatments didn't change the frame size.