Text Split (Delimiter)

There's a whole class of ComfyUI workflows that are secretly about lists: a comma-separated prompt variant string, a newline-delimited set of negative prompts, a filename list you want to iterate over. To use those in the graph you need to split the string apart - and most text-splitter nodes make you think about output sockets that don't exist yet.

Text Split (Delimiter) is the boring, dependable version: split on a delimiter, get up to twenty named parts (part_1…part_20), a remainder bucket for overflow, and a count. Fixed socket layout, no dynamic outputs, no surprises when you reload a saved workflow.

How it works

Plain string splitting with sensible defaults and one nice escape hatch: the delimiter field understands \n, \r\n, \r, and \t as escape sequences, so you can split on newlines or tabs just by typing the escape. Behavior is controlled by three toggles:

• output_count - how many leading parts get their own socket before overflow lands in remainder. Default 4.
• strip_parts - trims whitespace around each part (default on; you almost always want this).
• skip_empty - drops empty parts after splitting (default on, so trailing commas don't create phantom empty slots).

Whatever remains after the visible parts is re-joined with the delimiter into remainder, so nothing is ever lost. count tells you how many parts existed in total.

The inputs that matter

• text - the string to split.
• delimiter - what to split on. , by default; \n is the other common choice.
• output_count - number of leading part sockets.

Outputs: part_1 through part_20, remainder, and count. The parts that exceed output_count still exist as sockets - they just come back empty and the overflow goes to remainder.

Install

Part of the Enviral Design Node Pack. ComfyUI Manager: search "Enviral Design Node Pack". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/EnviralDesign/comfyUI-enviral-design-node-pack

then restart. No extra dependencies.

When you'd reach for it

The natural pattern: a Custom Combo or a text file feeds a big comma-separated string, this node splits it, and the parts drive things like Enviral Sampler Name, Enviral LoraName, or prompt text encoders per pass. It's also the handiest way to feed a batch of filenames into a loader. The fixed-socket design is deliberate - dynamic outputs are clever until a saved workflow reloads with different count and every wire points at nothing. The trade-off: if you need more than twenty parts, you need a different tool, because twenty is the hard cap here.