Show Text
The Debug Node That Shows You What Your Strings Actually Say
- STRING
ComfyUI has a frustrating gap: strings flow between nodes invisibly. You build a chain of text manipulation and have no idea what's actually coming out the end until the sampler runs and the image looks wrong. ZSQShowText is the three-second fix - wire any string into it and the value appears right on the node, like a little display widget for your data.
How it works
It's about as simple as a node gets. ShowText takes one input, text (any STRING you can wire in), and its notify function pushes the value into the node's UI. The clever bit for a "display" node: it's set up with list mode (INPUT_IS_LIST/OUTPUT_IS_LIST), so it'll happily display a whole batch of strings - exactly what you want when you're debugging a BatchPromptJson or a prompt-list workflow that feeds multiple generations.
What you get
One input, one output. The output is the same text it received, passed through, so you can drop it into a chain without disrupting the flow - debug in place rather than re-wiring. Set it as a terminal node and the text shows up in the node's body as the graph runs. It's the string equivalent of putting a voltmeter on a wire.
When it saves you
Every time you're joining prompts, running regex replacements, or feeding strings into a ConnectionString and aren't sure of the format. A five-second sanity check before the sampler runs beats a full generation cycle to discover your separator was wrong. It's also genuinely handy for inspecting the positive output of the pack's BatchPromptJson before you commit a 100-prompt batch to GPU.
Installing it
It ships in windfancy/zsq_prompt. Search "zsq_prompt" in ComfyUI Manager and install, or:
cd ComfyUI/custom_nodes
git clone https://github.com/windfancy/zsq_prompt
then restart ComfyUI. Expect the pack's heavy requirements to install alongside, even though this node needs nothing beyond what ComfyUI ships. And if Manager flags zsq_prompt as conflicting with something, that's the pack's generic class names colliding in the manager's index - ignore unless you're genuinely running both.
Verdict
A tiny node with zero ambition and real value. Every workflow-building session eventually needs to see a string, and this is the cheapest way to look.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |