Text [LP]

Not every node needs a clever explanation. This one's exactly what it says on the label - a box where you type multi-line text, and a STRING output that hands that text to whatever's next in your graph. The README calls it out plainly: "a simple node for entering multi-line text (similar to Prompt from other node packages)."

What it is and why you'd reach for it

You could type a prompt directly into a CLIP Text Encode's text field and skip this node entirely - plenty of workflows do exactly that. Where a standalone Text node earns its place is when you want that string to exist as its own thing in the graph rather than buried inside another node's widget: wire the same text into more than one downstream node without retyping it, feed it into one of this pack's own text-processing nodes (Text Replace, Text To List, the translation nodes) before it ever reaches a sampler, or just keep a sprawling graph legible by having a visible "here's where the text comes from" box instead of hunting through node internals to find where a string originates.

It's a source node, not a transform - nothing here validates, cleans, or modifies what you type. It's the plain multi-line counterpart to this pack's single-line String node, for whenever your text needs to span more than one line (system-prompt-style instructions, multi-sentence captions, anything you'd want to read comfortably wrapped rather than scrolling a single-line field).

The input and output that matter

There's exactly one field:

• TEXT (required, multiline, defaults to empty) - whatever you type.

Output: TEXT - the same string, unchanged, ready to wire anywhere a STRING input is expected.

Installing it

Through ComfyUI Manager, search "ComfyUI Level Pixel" or "ComfyUI-LevelPixel." Manual install:

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

Restart ComfyUI. No models, no dependencies - it's a UI widget.

Common issues & troubleshooting

Nothing downstream seems to receive anything. This node isn't an output node, so if its TEXT output isn't wired into something else in the graph, it simply won't execute or matter - unlike some of this pack's other text nodes (Text Choice Parser, Tag Remover) which are flagged to always run, this one only fires as part of a chain that actually consumes its result.

You want the text to vary per run instead of staying static. This node holds a fixed string you set by hand - it has no seed, no randomization, no template syntax. If you want prompt variety generated automatically (the old {this|that} bracket trick, for instance), this pack's Text Choice Parser is the node built for that; Text is deliberately the simplest possible source, not a generator.

Single-line vs multi-line confusion. If you only need one line and don't want the extra vertical space a multiline box takes up in the graph, this pack's plain String node (per the README, "a simple node for entering single-line text") is the leaner alternative for short values.