String List Editor

String List Editor is the friendliest way to hand a ComfyUI workflow a list of strings. One string per line in a multiline box, an Add button, and a drop zone that appends file paths when you drag files onto it. The backend then turns that text into a proper list: lines get trimmed, blank lines get dropped, and out comes a clean list of strings.

When you'd reach for it

Any time a workflow needs a list of prompts, file paths, tags, or model names and you'd rather type them than wire up a dozen text nodes. The drag-and-drop is the standout feature: drop a folder of images onto the node and every file path lands as its own list entry - an easy way to hand a batch loader an explicit file list without typing paths by hand.

How it works

The frontend gives you the textarea, the Add button (appends an empty line so you can keep typing), and the drop zone. The backend is deliberately simple: split the multiline text into lines, strip whitespace on each, discard empty lines, return the rest as a list with OUTPUT_IS_LIST declared - so the graph engine treats the output as a batch.

Inputs and outputs

• items_text (required, STRING, multiline) - the author's own tooltip says it all: "One string per line. Use the 'Add' button to append, or drop files to add their path(s)."
• * (output, declared list) - the list of trimmed, non-empty lines.

Installing it

Part of the comfy-ovum pack:

cd ComfyUI/custom_nodes
git clone https://github.com/sfinktah/comfy-ovum

Restart ComfyUI, or install via ComfyUI Manager → search "comfy-ovum". Light dependencies, no models.

The deprecated tag (read this before you build on it)

The pack's source marks StringListEditor as DEPRECATED = True - registered as "StringListEditorDEPRECATED(batch)". It's the old member of a three-way family, replaced by:

• StringBatchEditorOvum (ovum/lists/comfy) - the current batch variant, same split-and-trim behavior, output declared as a graph list.
• StringListEditorOvum (ovum/lists/python) - same input, but returns a real Python list object as a single value.

If you're starting a new workflow, use one of those. This node still runs, and it behaves like the batch variant, but it's the deprecated stepping stone - and since the newer variants are backend-simple, the drag-and-drop file-append UI is one of the things you'd actually lose by migrating. Worth knowing before you switch.

Common gotchas

• Blank lines and whitespace vanish. " foo " becomes "foo", and entirely blank lines are dropped. If you need to preserve leading/trailing spaces, this node will fight you.
• It splits on newlines, nothing else. No comma splitting, no quoting rules. What you type is what you get, one item per line.