LoRA Stack to String converter

A tiny, single-purpose utility: it takes a LORA_STACK - the bundle a LoRA Stacker builds - and turns it into plain text listing the LoRAs and their weights. That's it. It doesn't apply anything or change your image; it just converts a stack you can't read into a string you can.

Small as it is, it sits at a strong average search position, which tells you people go looking for exactly this: a way to get their LoRA list out of the node graph and into text.

Why you'd reach for it

The LORA_STACK type is a bundle meant for other nodes to consume - you can't eyeball it. This node makes it human-readable so you can do useful things with the list:

• Bake it into your image metadata or a filename so you know which LoRAs made a given output.
• Drop it into a text/notes node for a caption or a record of the run.
• Feed it into a prompt or a show-text node while you're dialing in a stack, so you can see what's actually loaded.

It's the kind of node you don't think about until you're three LoRAs deep and can't remember what's in your stack.

The reason this matters more than it sounds: the Efficiency pack encourages big LoRA stacks precisely because they're cheap to build, and a shared workflow with five LoRAs in a stacker is opaque to whoever opens it next - including you, a month later. Baking the list into the saved image's metadata or filename means the recipe travels with the picture. When someone asks "how'd you make this," the answer is embedded in the file instead of lost in a graph you've since rewired.

The inputs and outputs

There's exactly one input, lora_stack, which takes the LORA_STACK output from a LoRA Stacker (or any node that emits one). The single output is a LoRA string - text you wire into whatever consumes strings: a Save Image with metadata, a text display, a prompt concat, and so on.

That's the entire node. No settings, no gotchas in the configuration.

Installing it

ComfyUI Manager → search Efficiency Nodes for ComfyUI, or:

cd ComfyUI/custom_nodes
git clone https://github.com/jags111/efficiency-nodes-comfyui

Restart after. Nothing else to install for this node.

Common issues

The only real "problem" is expecting it to do more than it does - it's a display/record helper, not something that affects generation. If you wire its string somewhere that ignores it, nothing happens, and that's correct behavior.

Otherwise it inherits the pack's install-level issues: if it doesn't show up in the node list, check the console for IMPORT FAILED (often a pip freeze non-zero-exit error), and update ComfyUI, your packages, and the node. This pack has a habit of breaking on ComfyUI frontend updates; updating it to the latest commit is the standard fix.