Nodes/LF Nodes/Load LoRA tags
ComfyUI Node

Load LoRA tags

...> prompt and actually get the LoRA

By lucafoscili·Created 2 years ago·Updated 2 years ago· 50
Load LoRA tags
  • model
  • clip
  • ui_widget
  • model
  • clip
get_civitai_infotrue
tags

You know those prompts people share with <lora:name:0.8> tags baked in? In A1111 that syntax applies the LoRA automatically. In ComfyUI it's just text - the tag does nothing unless a node parses it. LF_LoadLoraTags is that parser. Feed it a prompt full of LoRA tags and it reads them out, applies each LoRA to your model and CLIP, and hands you back the patched pair. One paste, done.

Here's what it does mechanically. The tags input is a multiline string where each tag looks like <lora:example:1.0> - the name of a LoRA file in your models/loras folder, optionally followed by a weight. The node walks the text, picks out every <lora:...> token, and loads each one with the weight you specified (defaulting to 1.0 when no weight is given). It needs a model and a clip input because that's what a LoRA patches - you hand in the checkpoint's MODEL and CLIP, you get patched versions back on the model and clip outputs, ready for the positive prompt or KSampler.

The input that deserves a decision: get_civitai_info, on by default. When it's on, the node tries to fetch the LoRA's metadata from the CivitAI API so the frontend can show you a proper info card instead of a bare filename. It's a nice touch, but it means network calls on every execution, and CivitAI's API doesn't have data for every file - that's a known, universal complaint about CivitAI metadata fetching in ComfyUI tools. If you're offline, on a metered connection, or running a batch where you don't need the cards, flip it off. The node works fine without it.

The usual gotchas, in order of how often people hit them:

  • The name must match a file on disk. The tag refers to whatever's in your loras directory; a tag that names a model you never downloaded silently applies nothing or errors.
  • Only <lora:...> is handled here. Embeddings in the same prompt (<embedding:...>) and plain text pass through untouched - this node patches the model, it doesn't rewrite your prompt. If you want embedding pairs handled too, look at LF_LoraAndEmbeddingSelector from the same pack.
  • The weight inside the tag wins. <lora:foo:0.6> applies at 0.6. There's no separate weight input, so edit the tag itself to tune.

Where this shines is portability: you grab a workflow or a prompt from a tool that uses A1111-style tags, and the model actually comes along. It's a small node, but it removes a genuinely annoying manual step - and it's the reason LF Nodes gets recommended on r/comfyui when people want to reuse prompts that carry LoRA tags.

Install is the usual LF route - Manager → search "LF Nodes", or clone https://github.com/lucafoscili/comfyui-lf into custom_nodes. No models to download for the node itself; the LoRAs it loads are yours. Note the repo is now legacy (frozen Feb 2025) with development moved to lucafoscili/lf-nodes - same node there, and worth using for new installs.

Category✨ LF Nodes/Configuration

Inputs (5)

NameTypeDefaultDescription
get_civitai_infoBOOLEANtrueAttempts to retrieve more info about the models from CivitAI.
modelMODELThe main model to apply the LoRA to.
clipCLIPThe CLIP model to modify.
tagsSTRINGText containing LoRA tags, e.g., <lora:example:1.0>
ui_widgetoptKUL_CARDS_WITH_CHIP

Outputs (2)

NameTypeDescription
modelMODEL
clipCLIP