ScarlotSoft String to Text

ScarlotSoft String to Text is the thinnest node in the ScarlotSoft suite, and it wants to be. You type a single line of text into the string field, it hands the exact same string out of the STRING output. That's it. No joining, no transforming, no tokens. The entire reason it exists is to turn a widget value into a wire.

In the plumbing layer this is the "primitive value node" pattern (see the KB's node-plumbing doc): one source of truth, fanned out to many consumers. Type a seed, a filename fragment, a fixed quality tag once, and wire it to five places - then change it in one spot instead of five. ComfyUI core ships PrimitiveString for exactly this, and if you already have the ScarlotSoft pack installed, this node is that idea wearing the suite's dark theme. If you're deciding between them purely on function, they're the same thing; this one is a single-line field (no multiline), which is actually the right shape for a short value you want to distribute.

The one input is string (single-line, empty by default), and the output is STRING - wire it into any text slot by converting the target widget to an input. It is not an output node, so it won't show anything on its own; it's a passthrough in the middle of the graph.

Install

Same pack, same steps. ComfyUI Manager → search "ScarlotSoft" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/scarlotsoft/ComfyUI_ScarlotSoft

Restart ComfyUI. Zero dependencies, zero models, zero downloads.

The honest take

There's a reason this article is short, and it's not a lack of enthusiasm: this node is a convenience clone of a core primitive, and the honest advice is that if core PrimitiveString is already in your palette, you're not gaining anything by swapping. Where it earns its place is as part of the suite - the same author, the same look, one less pack if you're consolidating onto ScarlotSoft's utility nodes. Its single-line restriction is a feature for short values (a LoRA trigger word, a checkpoint nickname) and a limitation for anything longer - for multiline prompt fragments you want the suite's String Concat or the multiline field on a CLIP Text Encode instead. It does one thing, does it exactly, and costs you nothing to keep around.