Unpack Text

Unpack Text is the other half of Titled Text, and it's about as simple as a node gets. You feed it a titled_text string from a StringKit source and you get two outputs: title and prompt. That's it. One input, two outputs, no widgets to configure.

Why does this need to exist? Because Titled Text ships your title along with the prompt as hidden metadata on the string, not as visible text. That's great for keeping the two together without delimiter collisions, but it means you need a dedicated node to pull the title back off. This is that node. The prompt output is the body text you wire into your CLIP encoder; the title output is the short label you wire into a Build Path segment (hello, per-prompt output folders) or into Seed List so each prompt gets its own seed.

The one gotcha

The title output is not guaranteed to have content. If the string arriving in titled_text never carried a title - which happens the moment anything between Titled Text and here isn't a StringKit node - you get an empty string, silently. No crash, no red socket. A plain string from any other pack is accepted and just lacks the metadata. If your filename folders keep coming out blank, trace the path from Titled Text to here and look for a non-StringKit node in the middle.

Install

Part of the ComfyUI-StringKit pack (MIT, no dependencies - no models, no API, no GPU work). ComfyUI Manager: search ComfyUI-StringKit. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/luku756/ComfyUI-StringKit

Then restart ComfyUI fully - the pack ships frontend JS that hot reloads don't pick up. You'll find Unpack Text under the StringKit category.

Honestly, you could argue this node shouldn't exist and Titled Text should just have two outputs. But the single-string design is what lets the title survive a Loop Texts pass without breaking, so the pack pays for it here. It's three minutes to wire up and it makes your save folders self-organizing - worth the socket.