Text

Let's get the awkward part out first: this node is deprecated. As of the June 2026 core update it's literally renamed "Text String (DEPRECATED)" in the node list. It still works - old workflows load it fine, its output is a perfectly good STRING - but ComfyUI is telling you to use the multiline text node instead, and it's right.

PrimitiveString is the single-line text primitive: one value input (a STRING, multiline: false), one STRING output, pass-through execute. Historically it was the plain "Text String" node in the utilities/primitive family - the one the frontend spawned when you converted a single-line text widget to an input. Then the multiline version showed up, and it immediately made sense why a single-line box existed at all: someone had to be the old one.

Why it got deprecated

Prompts are rarely one line. They're paragraphs with weights, emphasis, and the occasional stray newline, and the multiline node (now Input Text) handles all of it in a resizable box. A single-line input turns a serious prompt into a scrollbar nightmare. So core flipped: the multiline node got promoted to the Essentials tab and became the default text-input node, while the single-line one got the deprecated sticker in June 2026 (in the latest dev builds it's actually been resurrected and renamed "Text", but on the current stable you'll see the deprecation marker).

When you might still hit it

Two cases, both real:

• Legacy workflows. Anything saved before mid-2026 may reference it. It loads, it runs, nothing breaks. The deprecation is a label, not a landmine.
• Convert to input. Convert a single-line string widget on some node to an input and the primitive that materializes can be this one. That's not a bug - it's matching the widget's type - but you'll probably want to swap it for the multiline version if you're typing more than a few words.

What to do instead

Use Input Text (PrimitiveStringMultiline) for anything human-written: prompts, negative prompts, style templates. Same STRING output, same wiring into CLIP Text Encode or String Concatenate - just a bigger, friendlier box.

How you get it

Ships with ComfyUI core, no install. The backend primitive nodes landed in March 2025; the single-line string was part of that original batch. No model files, nothing to download.

Common issues

• "Why does my prompt lose its formatting?" Because this is the single-line node - newlines don't survive, or rather, it's one line by construction. That's the deprecation in action. Grab the multiline node.
• "Text String" vs "Text String (Multiline)". If you're on an older version, these two names sit right next to each other in the menu and it's easy to click the wrong one. The multiline one is the one you want for prompts.
• Nothing to troubleshoot, really. It's a pass-through. About the only failure mode is wiring STRING somewhere expecting CONDITIONING - same mistake as with Input Text - and that's a wiring error, not a node error.

It's the node the family grew out of. If a workflow hands you one, let it run and don't panic; but when you're building fresh, reach for Input Text and skip the archaeology.