Join Text (Legacy)
The boring two-string join — deprecated, but it still gets the job done
- str
Some nodes do heavy lifting. Join Text (Legacy) does exactly one thing: it takes two strings, slaps a separator between them, and hands you the result. That's it. If you've ever glued a quality tag onto a base prompt with ", ", you already understand the entire concept. It's the text version of a + sign.
The "(Legacy)" in the name is doing honest work, though. In the current Sage Utils the node is flagged as deprecated - the pack has since moved to multi-string join variants that take more than two inputs. The node still works fine and still shows up in search, but the author is telling you where the newer stuff is. For a beginner who just needs to combine two text fields, "legacy" shouldn't scare you off; it means "stable and simple," not "broken."
How it works
You feed it str1 and str2, pick a separator (default ", "), and it joins them: str1 + separator + str2. There's one extra switch, add_separator_to_end, which appends a trailing separator when on. That's for the classic "prompt list with a comma at the end so the next thing can just append" pattern - slightly unusual, but if you know you want it, it's there.
The output is a single STRING called str, which you can wire anywhere text goes: a CLIP Text Encode's positive prompt, a metadata node, a text display.
The inputs in practice
Four inputs, two of which you'll touch:
str1/str2- the two strings, both multiline.separator- the glue, default", ". Change it to a space, a newline,and, whatever fits the target field.add_separator_to_end- trailing separator toggle, default off. Leave it off unless you have a reason.
When you'd reach for it
It's the kind of node you grab in the middle of a workflow when you realize two text sources need to meet: a subject from one node and a style tag from another, a positive prompt assembled from a base plus a LoRA keyword. It's not exciting, but it's often exactly what makes a graph work without reaching for a full text-concatenation toolkit.
One tip if you're new to Sage Utils: because this one's deprecated, ComfyUI's newer interfaces may visually dim it or nudge you toward the replacement. Don't fight that - the pack's Join Text-with-more-inputs nodes do the same job with room to grow. If you only ever need two strings, either one is fine.
Installing
Part of Sage Utils, so the standard install:
cd ComfyUI/custom_nodes
git clone https://github.com/arcum42/ComfyUI_SageUtils.git
cd ComfyUI_SageUtils && pip install -r requirements.txt
Restart ComfyUI (or install via ComfyUI Manager by searching "Sage Utils"). No models, no extra dependencies worth mentioning.
The honest verdict
If you're building a fresh workflow today, you'd probably pick the non-legacy join node in this pack instead. But if you've loaded an older workflow that references this one, it'll keep running without complaint. Sometimes the most useful tool in a node suite is the one that does so little it can't possibly break - this is that node.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| separator | STRING | , | Separator string used between inputs. |
| add_separator_to_end | BOOLEAN | false | Add separator to the end of the joined string. |
| str1 | STRING | First string to join. | |
| str2 | STRING | Second string to join. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| str | STRING | Output value for str. |