ComfyUI Node

DP String Text

A plain text box that also takes an upstream string

By DesertPixelAi·Created 2 years ago·Updated about a year ago· 25
DP String Text
    • TEXT
    Widget_Input
    String_01

    The most boring node in this pack, in the best way - a text box you type into, that also outputs as a STRING you can wire anywhere ComfyUI expects text. If you've used any of the ecosystem's other basic text-utility nodes (there are a dozen packs that ship something like this), you already know exactly what this does. Its value is in being a single small, predictable building block rather than anything clever.

    How it works

    You type into the Widget_Input field directly on the node, and it comes out the other side as TEXT. There's also an optional String_01 input, which lets you feed a string in from upstream instead of (or alongside) typing it directly - useful when this node is sitting mid-graph collecting text from something computed earlier rather than being the very first node in the chain.

    This is a genuinely simple utility, and that's the point: a static piece of text, or a pass-through point for a dynamically generated one, with nothing else attached. It's the kind of node you reach for when you want a labeled, editable chunk of prompt text sitting visibly on your canvas rather than buried in a bigger node's widget.

    Inputs and outputs

    Required:

    • Widget_Input (multiline text, default empty) - type your text directly here.

    Optional:

    • String_01 (multiline text) - feed in a string from upstream instead of typing it.

    One output: TEXT (STRING).

    Installing it

    ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. Manual:

    cd ComfyUI/custom_nodes
    git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes
    

    Restart ComfyUI - no models, it's a text box.

    Where people get tripped up

    The only real point of confusion is figuring out what happens when both Widget_Input has text typed into it and something is wired into String_01 - since both are valid ways to give this node text, and the node ships with no description clarifying precedence, the safest habit is to only use one at a time. If you're building a graph where an upstream node is meant to be the source of truth, leave the widget blank and rely on the String_01 wire; if you're hand-typing, don't also connect something to String_01 expecting it to be ignored.

    Beyond that, this node has no formatting logic at all - no weight syntax, no trimming, no token counting. If you need any of that, look elsewhere in this pack: DP String Text With SDXL Weight adds attention-weight formatting, and DP Prompt Token Compressor handles trimming to a token budget. This one is deliberately just text in, text out.

    CategoryDP/text

    Inputs (2)

    NameTypeDefaultDescription
    Widget_InputSTRING
    String_01optSTRING

    Outputs (1)

    NameTypeDescription
    TEXTSTRING