ComfyUI Node

Show Text

See what a node is actually outputting

By clhui·Created 2 years ago·Updated 11 months ago· 9
Show Text
    • STRING
    text
    text2

    Half of debugging a ComfyUI workflow is answering "what is this node actually spitting out?" Strings are invisible in a graph - a prompt gets built, an upstream node transforms it, a value flows down a wire, and you have no idea what it says until it's baked into an image. Show Text fixes that. Wire a string into it and it prints the text right on the node face, where you can read it. Simple, and one of the first utilities you'll wish you had.

    This is a rebuild of the classic "Show Text" node that pythongosssss's Custom-Scripts made a staple. The clh version does the same thing: it's a window into your text.

    How it works

    It's a display node with a pass-through. You feed it a string, it renders that string in a text area on the node so you can see the actual content after execution, and it also passes the text back out so you can keep the chain going. Because it's an output node, it forces itself to run and show its contents even when nothing's wired to its output - which is exactly what you want from a debug readout. Drop it anywhere you're unsure, run, read.

    The everyday uses: check what a prompt-building chain (a JoinStringMulti, a template node, a wildcard) actually produced before it hits your encoder. Read the duplicate_report or log_output from the pack's duplicate-checker node. Eyeball the string coming out of a JavaScript clh node. Anywhere text is flowing and you can't see it, this makes it visible.

    The inputs and outputs that matter

    • text - the string to display. This is the one you wire from upstream.
    • text2 (multiline) - a second text field, so the node can show two strings at once (or you can type a note in one and pipe a value into the other).

    Output is a STRING (delivered as a list). Wire it onward if you want the displayed text to continue downstream - the node doesn't consume the string, it just shows it in passing.

    Installing it

    ComfyUI Manager: search Clh Tool for ComfyUI, install, restart. Or by hand:

    cd ComfyUI/custom_nodes
    git clone https://github.com/clhui/ComfyUi-clh-Tool
    

    then restart ComfyUI. If a manual clone doesn't surface the node, check the ComfyUI startup console for a missing-dependency line - Manager installs a pack's requirements for you, a bare git clone leaves that to you. (A display node like this rarely needs anything special.)

    Common issues

    The one that trips people: the text only fills in after the node runs. Show Text displays a string that flowed through during execution, so before you hit queue the box is empty - that's normal, not broken. Run the graph, then read it.

    Second, it shows text - it does not modify it. If the string looks wrong, this node is the messenger, not the culprit. Trace back to whatever built the string and fix it there; Show Text is doing its job by faithfully showing you the mess. That's the entire point of it as a debug tool: it tells you the truth about what's on the wire, so you can find where things actually went sideways. Keep one parked next to any prompt-assembly chain and you'll spend a lot less time guessing.

    CategorysimpleTool_clh/utils

    Inputs (2)

    NameTypeDefaultDescription
    textSTRING
    text2STRING

    Outputs (1)

    NameTypeDescription
    STRINGSTRING