LoRA Syntax → Path (LoraManager)

A small, sharp utility. You hand it LoRA Manager's <lora:name:strength> syntax, and it gives you back the actual file paths those entries resolve to. That's the entire node. It's a translator between the pack's friendly shorthand and the on-disk reality.

Niche, but it solves real problems. Sometimes you need the raw path - to feed a node from another pack that expects a filename rather than the manager's syntax, to log or display exactly which files a syntax string points at, or just to confirm a piece of syntax resolves to the file you think it does before a long run. It's the debugging companion to the text-driven loaders: when a LoRA "isn't loading," this tells you whether the name even maps to a file.

Remember where the syntax comes from in the first place: you browse your collection in the LoRA Manager UI at http://localhost:8188/loras, right-click a LoRA, and hit "Copy LoRA syntax." That gives you the <lora:name:strength> string with the preset strength already filled in. This node is what you use when you want to go the other direction - from that friendly string back to the concrete file on disk.

How it works

You give it a multiline lora_syntax string. For each <lora:...> entry it looks up the matching LoRA in the manager's index and emits the file path. Multiple entries in, multiple paths out (as a string). It doesn't apply anything to a model or touch your image - it's pure lookup.

Inputs and outputs that matter

• lora_syntax (STRING, multiline, required) - the <lora:name:strength> text, typed in or wired from a Text node or a loader's setup.

One output: paths (STRING) - the resolved file path(s). Route it into whatever needs a real path, a display node, or a logger.

How to install it

Via ComfyUI Manager: search lora-manager, Install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/willmiao/ComfyUI-Lora-Manager.git
cd ComfyUI-Lora-Manager
pip install -r requirements.txt

then restart. Light install, nothing to download.

Common issues & troubleshooting

A syntax entry resolves to nothing. That's the useful answer, not a failure - it means the name in your syntax doesn't match any LoRA the manager has indexed. Fix the name (autocomplete in a loader is the easy way to get it exactly right) or rescan your folders so the file is known.

Paths look different from what I typed. The syntax uses the LoRA's display name; the path is where the file actually lives, subfolders and all. That's expected - the whole job of the node is to bridge those two.

I fed it a prompt, not LoRA syntax. This only understands the <lora:...> form. Plain prompt text or wildcards won't resolve to paths here.