Add Text Suffix (DEPRECATED)
The deprecated mirror of Add Text Prefix
- texts
Add Text Suffix (AddTextSuffix) does exactly what its name says: appends a suffix to the end of a text string. And - same story as its sibling Add Text Prefix - the "(DEPRECATED)" in its display name is the whole review. It's a legacy node from ComfyUI's dataset-processing tooling, still present so old graphs load, superseded by the current string-utility family. If you're starting a new workflow, don't reach for it; if you're reading this because an old graph loaded it, here's the 30-second migration.
The history: this node came from the batch/dataset text tooling where "add a suffix to all texts" was a caption-processing operation - you'd stamp , concept art onto every line of a training list. When core rebuilt its text utilities into the cleaner nodes_string family, suffix-adding got absorbed into Concatenate Text, and the old node got the deprecation flag.
How it works
One line under the hood: text + suffix. Your texts input ("Text to process") gets suffix ("Suffix to add") appended with no separator and no trimming. Want ", 4k" on the end? The comma and space live in the suffix string, your job to include. Inputs: texts, suffix. Output: the joined string, labeled texts ("Processed texts"). Nothing more - no flags, no whitespace handling. As with the rest of the deprecated dataset family, the plural labels are a leftover from the batch-caption era, not a sign that the socket carries a list.
What to use instead
The replacement is Concatenate Text (StringConcatenate), used in the other order: string_a = your text, string_b = "4k", delimiter = ", ". Same result, delimiter explicit, one current node instead of a legacy one. For multi-part or templated suffixes, Format Text (StringFormat) is the step up and handles the whole assembly in one node.
Common issues
Both deprecated text nodes share the same pitfalls, so this is quick: they expect you to hand-roll separators (no automatic ", "), and they're on a legacy code path that isn't maintained. If a saved workflow uses Add Text Suffix, swap it for Concatenate Text and move on. One thing to double-check when you do: make sure the delimiter ends up between the text and suffix, not glued onto the suffix with no space - the classic "oh right, I have to type the space myself" moment. That's the entire tax of using deprecated plumbing; the modern node makes the separator a named input instead of a character you're expected to remember, which is why the upgrade is worth the two minutes it takes.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| texts | STRING | Text to process. | |
| suffix | STRING | Suffix to add. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| texts | STRING | Processed texts |