Create List

Most ComfyUI nodes process one thing at a time. Lists change the game: feed a node a list of prompts or images and it processes them in a batch, which is how you run a prompt sweep or a whole gallery through one graph instead of copying nodes. Create List is the supply line for that pattern - it takes several inputs and joins them into a single list output that anything list-aware can consume. It ships with ComfyUI core, no install, and it's a 2026 addition.

The search aliases give away the intent: "Image Iterator," "Text Iterator," "Iterator." This node exists to feed iterators. If you've ever stacked a dozen prompt variations by hand, this is the node that turns that into data.

How it works

The inputs are autogrowing - you start with a couple of sockets and add more as you need them. Every input must be the same type, and the node concatenates them into one list on the output. The key mechanism detail: each input socket is itself expected to carry a list, and the output is the concatenation of all of them.

That "lists in, one list out" detail is the thing to wrap your head around. If you have one prompt per input socket and feed a single string, you're feeding the wrong shape - the node wants each input to be a list (even a one-element list), and it joins the lists together. The output preserves the type, so a list of strings in gives a list of strings out, and the same for images or numbers. Keep everything the same type; the node's match-type wiring is there to enforce it.

Inputs and outputs

One autogrow input group, inputs, where you add sockets for each list you want to combine. One output, list - the merged list of the same type.

Where people get burned

The most common failure is shape mismatch: feeding a bare value where a list is expected, or feeding lists of different types. The error message will be about types, but the actual problem is usually "I thought I was adding single items." Remember the rule - concatenation, not wrapping. If you want to wrap a single value into a list, that's a different operation than joining lists.

Second: type consistency matters more than you'd think. A list of images and a list of masks are both lists, but they're different lists to ComfyUI, and the downstream iterator will reject the mixture. Keep one type per node instance.

Third: don't over-list. If you only ever run one prompt, this node is ceremony. It pays off the moment you're doing variations - prompt sweeps, batch img2img, multi-seed runs - where the alternative is a graph that's physically too big to read. That's the case for most utility nodes: they exist to keep your workflow readable, not to generate anything themselves.