Enviral Load LoRA (Deprecated)

ComfyUI's native Load LoRA has one infuriating limitation: the lora_name dropdown can't be fed by a string. So when a workflow needs to apply a LoRA chosen earlier in the graph - from a Custom Combo, a text splitter, a filename list - you're forced into duplicate loader nodes or manual edits.

Enviral Load LoRA keeps the exact feel of the native loader but opens up that one socket. It's a drop-in Load LoRA: model and clip in, patched model and clip out, strength_model / strength_clip sliders. The difference is lora_name accepts a linked string as long as it resolves to a LoRA ComfyUI actually knows.

How it works

Under the hood it applies the LoRA the same way ComfyUI's own loader does - model.clone(), patch the model and clip with the LoRA weights, hand back the patched pair. The list in the dropdown comes from folder_paths.get_filename_list("loras"), so it reflects everything ComfyUI has registered, including extra_model_paths.yaml paths.

The resolution order for a linked string: exact name, then case/path-normalized, then unique path suffix. Crucially, validation happens before execution, so a bad name fails the graph with a clear message rather than silently applying the wrong LoRA.

The inputs that matter

• model / clip - the diffusion model and text encoder to patch. Wire from your loaders.
• lora_name - dropdown or linked string. This is the whole point.
• strength_model / strength_clip - how hard the LoRA bites. Default 1.0 is often too strong for style LoRAs; 0.5–0.8 is the common starting range, and you can go negative to subtract the LoRA's effect.

Outputs: patched model and patched clip, straight into KSampler.

Install

Part of the Enviral Design Node Pack. ComfyUI Manager: search "Enviral Design Node Pack". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/EnviralDesign/comfyUI-enviral-design-node-pack

then restart. No extra dependencies - it reuses ComfyUI's own LoRA application code.

Common gotchas

The string you feed has to be a known LoRA path - matching a filename is not enough if that file isn't registered with ComfyUI (drop it in your loras folder and refresh first). And remember the linked string replaces the dropdown entirely, so keep one source of truth per loader. If your workflow applies the same LoRA to every run, the native loader is honestly fine - this node's payoff is when the LoRA becomes a variable, which is also what Enviral LoRA Name plus a native loader gives you. Pick whichever flavor fits your graph.