Nodes/ComfyUI-SettingsToText/Settings To Text
ComfyUI Node

Settings To Text

The node whose own README calls it 'shitty' — and that's honestly the whole review

By JVsup·Created 8 months ago·Updated 8 months ago· 0
Settings To Text
    • Result String
    settings_json[]

    Let's start with what the README says about itself, because it saves everyone time: "shitty ai-written node to extract basic settings in workflow." That's the author's own description, quoted verbatim. Most custom node READMEs oversell. This one undersells. And honestly? It's closer to the truth than the marketing.

    SettingsToText is a tiny utility node with one job: take a JSON blob of settings and render it as readable text right in the graph. One input, one output, no models, no dependencies, no API keys. It's the kind of node you add when you want the generation settings that went into an image visible as plain text on the canvas - for a screenshot, for a tutorial, for dumping a config into a chat, whatever.

    How it works

    The mechanism is as simple as the pack's reputation. You feed it a JSON string, it parses and formats it, and hands you a Result String back. Because it's flagged as an output node, that string renders in the node's own box on the canvas - you don't wire it anywhere. It just sits there being readable, which is the entire point.

    The one input that matters is settings_json, a single-line string field that defaults to "[]". That default is your tell: the author expects you to paste in a settings object (or whatever tool emitted the JSON you're inspecting). If you leave it as [], you get an empty array printed back at you, which is accurate but useless.

    What to actually feed it

    Since the README is this short, here's the practical picture:

    • Paste a JSON object into settings_json - the Result String output shows it back formatted as text.
    • Use it for eyeballing or copying settings, not for driving other nodes. It's a display node; that's the whole personality.

    That's the honest scope. This is not a workflow-automation workhorse.

    Installing it

    Standard custom-node fare, no surprises:

    cd ComfyUI/custom_nodes
    git clone https://github.com/JVsup/ComfyUI-SettingsToText
    

    Then restart ComfyUI (or hit the reload button in Manager). There's no requirements.txt to speak of, no model files to download, nothing heavy - a genuinely lightweight pack, which in an ecosystem where "dependency hell" is the #1 complaint is a real virtue.

    Where people get burned

    The README names the failure modes itself, and they're worth repeating because they're specific:

    • It does not play well with subgraphed nodes. If this node lives inside a subgraph in newer ComfyUI versions, expect it to misbehave. Keep it at the top level of your graph.
    • It refuses to work with math or logic nodes in general. Don't chain it off a math or logic node's output. It wants raw JSON, not a computed string. If it errors, that's the first thing to check.

    That's it. That's the whole troubleshooting list, because that's the whole node.

    The honest take

    This is a 0-impressions, borderline-never-discussed utility, and it exists because the author wanted a settings-to-text dump and made one. If you just need to display a string, ComfyUI's own Preview Text or whatever utility pack you already have does the same job with less attitude. But if you specifically want a settings-JSON → readable-text node that's tiny, dependency-free, and refreshingly upfront about its limits - this fits. Just take the README's warning seriously: keep it out of subgraphs, feed it clean JSON, and don't expect polish.

    You won't find much community guidance on it, because there isn't any. That's fine. It's the kind of node you install in thirty seconds, use once, and quietly forget - and for that specific job, it works.

    Categoryutils

    Inputs (1)

    NameTypeDefaultDescription
    settings_jsonSTRING[]

    Outputs (1)

    NameTypeDescription
    Result StringSTRING