Load Lora

This is WAS's take on the LoRA loader. Functionally it does what core ComfyUI's LoraLoader does - applies a LoRA on top of your model and CLIP so the style, character, or concept the LoRA was trained on comes through in your generations. The reason the WAS version exists is a small but genuinely handy twist: the pack's loaders "also output a string that contains the name of the model being loaded," per the README. So along with the patched model and CLIP, you get the LoRA's filename as text.

Why care about a name string? Automation and bookkeeping. You can feed that name straight into a Save Text File, bake it into your output filename via WAS's token system, or stamp it onto the image - so months later you actually know which LoRA made a given picture. If you've ever stared at an old output wondering what was loaded, this solves that.

How it works

A LoRA is a small set of weight adjustments trained on top of a base model. Load Lora reads a .safetensors LoRA from your models/loras folder and merges its adjustments into the model and CLIP passing through it - typically with separate strengths for the model side and the text-encoder side, the same two-knob setup the standard loader uses. The patched model and CLIP come out the other end for your sampler and prompt encoding, and the extra output carries the LoRA's name as a plain string.

The inputs and outputs that matter

• Model and CLIP in - the pipeline to apply the LoRA to.
• A LoRA selection - which .safetensors file from your loras folder to load.
• Strength - how strongly to apply it. This is the knob you'll adjust; too high and the LoRA overpowers everything, too low and it barely registers.
• Model + CLIP out, plus a name string out - the patched pipeline, and the LoRA's filename as text.

Honest note: this exact node isn't broken out in the WAS README's node list and I don't have a schema for its precise fields, so I'm describing it from the pack's stated "loaders also output a name string" behavior and standard LoRA-loading, not inventing specific widget labels or defaults.

How to install it

Part of the WAS Node Suite:

• ComfyUI Manager: search was-node-suite-comfyui, install, restart.
• Manually: cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui/, then pip install -r requirements.txt against your ComfyUI Python, and restart.

No extra download for the node itself - but the LoRA files you load need to already be sitting in ComfyUI/models/loras.

Common issues

The most common non-issue mistaken for a bug: your LoRA "isn't showing up" in the dropdown. That's almost always placement - the file has to be in ComfyUI/models/loras, and you usually need to refresh or restart after dropping a new one in. Second, a LoRA trained for one base family (SD 1.5) applied to another (SDXL, or a newer architecture) will either do nothing or make a mess; match the LoRA to your checkpoint's family.

If the effect is too strong - blown-out style, mangled anatomy - pull the strength down before you blame the LoRA. Many are trained hot and want a value well under 1.0. And since this is the WAS loader specifically: core ComfyUI's built-in Load LoRA does the same core job, so unless you specifically want that name-string output for filenames or logging, either one is fine. Reach for the WAS one when the bookkeeping matters.

And the pack caveat: WAS Node Suite has been retired since December 2023 - used everywhere, unmaintained. If a ComfyUI update makes every WAS node vanish with an "Import Failed", that's suite-level dependency drift, not this node. Re-run requirements.txt against the correct Python environment (or the bundled install.bat) and restart.