String to List

ComfyUI widgets are great for one value at a time, but plenty of nodes want a list - batch parameters, a run of sizes to sweep through, several filenames. Typing those into separate individual widgets doesn't scale past two or three entries. String to List takes one delimited string and splits it into a proper list output you can wire straight into anything expecting one.

How it works

Split a string on a delimiter, and - per the pack's own README - coerce each resulting piece into a typed value rather than leaving everything as raw text. That's what the wildcard output type is doing: a * output in ComfyUI adapts to whatever socket you plug it into, so feeding this node's output into something expecting integers should hand over actual integers, not string fragments that happen to look like numbers.

The default value in the text field is itself a hint at the intended use: 128, 128, 256, 96 - a comma-separated run of numbers, the kind of thing you'd want for a series of pixelation sizes, target widths, or frame counts to test through a batch run rather than one at a time.

The inputs and outputs that matter

• text (default 128, 128, 256, 96) - the string to split.
• delimiter (default ,) - whatever separates your values. Change it if your data uses semicolons, pipes, or anything else.

Output: list (wildcard type, is_list: true) - the split, typed result.

How to install it

Search "Link Comfy Nodes" in ComfyUI Manager and install from there. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/Mister-Link/link-comfy-nodes
pip install -r link-comfy-nodes/requirements.txt

Restart ComfyUI. Plain string parsing - nothing extra to install for it specifically.

Common issues & troubleshooting

Stray whitespace around the delimiter. The default text has a space after every comma (128, 128, ...). If a downstream node is choking on values that look almost right, an unparsed leading space on a split piece is a common culprit - either match your delimiter carefully to include the space, or clean the source string before it reaches this node.

A piece doesn't parse as the type you need. If you're feeding the list into something expecting integers and one entry in your string isn't numeric, expect an error at that point rather than the entry being silently skipped - check the source string for typos or stray non-numeric characters if a downstream node fails right after this one.

Empty entries from a trailing or doubled delimiter. A string ending in your delimiter, or with two delimiters in a row, will likely produce an empty piece in the split - trim trailing delimiters and check for accidental double-commas if your list comes out one entry longer than expected.