Nodes/ComfyUI-EreNodes/Prompt to LoRA Stack
ComfyUI Node

Prompt to LoRA Stack

Name:0.8> text into a real LORA_STACK

By Erehr·Created about a year ago·Updated 2 days ago· 69
Prompt to LoRA Stack
    • lora_stack
    prompt

    Here's the friction point of the whole EreNodes pack: its nodes are prompt tools, so LoRAs end up as <lora:name:strength> text inside a string. ComfyUI's LoRA loaders don't read strings. Prompt to LoRA Stack is the bridge - it scans a prompt string for <lora:...> tags and emits a proper LORA_STACK that stack-compatible loaders can consume. That's what makes the pretty Gallery node actually useful for loading, not just for looking.

    What it is

    A tiny, focused parser from the ComfyUI-EreNodes pack (Erehr, mid-2025). You wire in any prompt text - from a Gallery, a Multiline, a wildcard output, or a hand-typed string - and it extracts every <lora:...> tag into the (lora_name, model_strength, clip_strength) tuple format that stack-style loaders expect. The README lists three compatible destinations: Efficiency Nodes, ComfyRoll Custom Nodes, and LoRA Manager. If you don't use stack loaders, the author's suggested alternatives are prompt-reading loaders that consume the text directly (LoRA Tag Loader, Impact Pack's Wildcard Encode, PCLazyLoRALoader).

    How it works

    It's one regex pass. It accepts the three forms LoRA tags come in:

    • <lora:name> → strength defaults to 1.0
    • <lora:name:model_strength>
    • <lora:name:model_strength:clip_strength>

    Negative strengths parse fine (handy for LoRA suppression). If a name doesn't already end in .safetensors or .pt, the node appends .safetensors for you - because stack loaders look files up by filename against your models/loras directory. The name is passed through normpath, so subfolder-relative paths work as long as they match the folder layout under your loras directory.

    Inputs and outputs

    • prompt - the STRING to scan. A forced input, so wire it from any text source in your graph.
    • Output - one lora_stack. Plug it into a stack loader's lora_stack input (Efficiency's LoraLoaderStacked, ComfyRoll's LoraLoader, or LoRA Manager's stack node), and load the model normally - the loader will apply every LoRA in the stack.

    Installing it

    ComfyUI Manager: search "EreNodes", install, restart. Or manually:

    cd ComfyUI/custom_nodes
    git clone https://github.com/Erehr/ComfyUI-EreNodes.git
    

    Restart; the node is under EreNodes. No extra dependencies - the pack declares only safetensors, already bundled with ComfyUI.

    Gotchas

    Two things bite people. First, this node only extracts; it doesn't remove. The <lora:...> text is still in your prompt string, so if you also feed that same string to a CLIP Text Encode, the encoder sees literal angle-bracket garbage. Keep a cleaned string for the text encoder, or use a loader that reads LoRAs straight from the prompt. Second, there's no existence check - if you reference a name that isn't in your loras folder, the stack loader simply fails to find the file at runtime. The name in your tag must match the filename on disk, extension included.

    CategoryEreNodes

    Inputs (1)

    NameTypeDefaultDescription
    promptSTRING

    Outputs (1)

    NameTypeDescription
    lora_stackLORA_STACK