A LoRA is the quickest way to teach a big image model something new: a character style, a product look, an art style or a camera effect. The file is small, often just tens to a few hundred megabytes, and you can swap it in and out without touching the base model.
ComfyUI makes LoRAs easy once you know where the files go and how the Load LoRA node is wired.
This guide shows how to use LoRAs in ComfyUI step by step, how to stack several of them, the strength settings that actually matter, model-only LoRAs for Flux, Wan and other newer models, and fixes for every common error.
- Folder: put LoRA files (
.safetensors) inComfyUI/models/loras/, then press R or restart. - Node: add Load LoRA between Load Checkpoint and your KSampler / CLIP Text Encode nodes. Wire both MODEL and CLIP through it.
- Strength: start at 0.7 to 1.0 for
strength_modelandstrength_clip. Lower it if the image breaks or looks over-cooked. - Trigger words: most LoRAs need a trigger word in your positive prompt. Check the model page.
- Multiple LoRAs: chain Load LoRA nodes one after another and lower each strength.
- Flux, Wan, Qwen-Image and similar: use LoraLoaderModelOnly, which patches only the MODEL.
What a LoRA Does
LoRA stands for Low-Rank Adaptation. Instead of retraining the whole model, a LoRA stores a small set of extra weights that nudge the base model towards something specific.
When ComfyUI loads a LoRA, it patches those weights into the model (and usually the text encoder) for the current run. The base checkpoint file on disk never changes, so you can use one checkpoint with dozens of different LoRAs.
Common uses include:
- Styles: watercolour, pixel art, 3D toy, film photo, anime styles.
- Characters and mascots: your own made-up character kept consistent across images.
- Concepts and objects: a product, a vehicle design, a clothing style.
- Helpers: detail enhancers, lighting LoRAs, and speed LoRAs that cut the number of steps (Lightning, Turbo and distillation LoRAs).
- Control and editing: newer models ship LoRAs for pose, depth or edge control, like the MOSS-Image control LoRAs.
LoRA Types and Which Node to Use
| File type | Typical models | Node to use | Notes |
|---|---|---|---|
| Standard LoRA | SD 1.5, SDXL, Pony, Illustrious | Load LoRA (LoraLoader) | Patches MODEL and CLIP |
| LyCORIS (LoCon, LoHa, LoKr) | SD 1.5, SDXL | Load LoRA | Loads the same way, no extra node needed |
| Model-only LoRA | Flux.1, Wan 2.x, Qwen-Image, HunyuanVideo, newer DiT models | LoraLoaderModelOnly | Text encoder is not patched |
| Speed / distillation LoRA | Lightning, Turbo, pDMD style LoRAs | Usually LoraLoaderModelOnly | Needs fewer steps and low CFG; follow the model card |
| Control / editing LoRA | Model-specific | As the model card says | Often needs a reference image input too |
ComfyUI’s own LoRA tutorial confirms that LoRA variants such as LoCon, LoHa and LoKr can be loaded with the regular Load LoRA node.
Step 1: Download a LoRA That Matches Your Model
- Check your base model. Open your workflow and note the checkpoint, for example an SD 1.5 model like DreamShaper 8 or an SDXL model.
- Search a model site. CivitAI and Hugging Face are the two big LoRA libraries. Filter by base model (SD 1.5, SDXL, Flux.1 D, Wan and so on).
- Read the model page. Note the trigger words, the recommended strength and any sampler or CFG advice.
- Prefer
.safetensors. Avoid old.ckptor.ptfiles from unknown uploaders, since those formats can contain code. - Check the licence. Some LoRAs ban commercial use. That matters if you sell images or use them on a monetised site.
The official ComfyUI LoRA example uses the DreamShaper 8 checkpoint (SD 1.5) with the blindbox_V1Mix LoRA, which turns prompts into cute 3D toy figures. It is a good first test because the effect is obvious.
Step 2: Put It in the Right Folder
| Install type | LoRA folder |
|---|---|
| Portable (Windows) | ComfyUI_windows_portable\ComfyUI\models\loras\ |
| Manual / git install | ComfyUI/models/loras/ |
| Comfy Desktop | <your base path>/models/loras/ (the folder you chose at install) |
| Shared folder with A1111/Forge | Add it to extra_model_paths.yaml under loras: |
After copying the file, press R in ComfyUI (refresh) or restart it. The file should now appear in the lora_name dropdown. Subfolders are fine; they show up as folder/file.safetensors.
New to ComfyUI? Our ComfyUI install guide covers Desktop, Portable and manual installs, and the ComfyUI beginner’s guide explains every core folder.
Step 3: Build the Load LoRA Workflow
Start from the default text-to-image workflow (Workflow > Browse Templates, or the default graph). You only add one node.
- Add the node. Double-click the canvas, search Load LoRA and add it.
- Connect MODEL. Drag the
MODELoutput of Load Checkpoint into themodelinput of Load LoRA. - Connect CLIP. Drag the
CLIPoutput of Load Checkpoint into theclipinput of Load LoRA. - Rewire the sampler. Connect the
MODELoutput of Load LoRA to themodelinput of KSampler. - Rewire the prompts. Connect the
CLIPoutput of Load LoRA to both CLIP Text Encode nodes (positive and negative). - Pick the file and strengths. Choose your LoRA in
lora_name, setstrength_modelandstrength_clipto 1.0 for a first test. - Run. Add the trigger word to your prompt and press Queue (Ctrl+Enter).
The order is always: Load Checkpoint → Load LoRA → (KSampler + CLIP Text Encode). VAE still comes straight from the checkpoint (or your separate VAE loader).
Step 4: Trigger Words and Prompting
Most LoRAs are trained with one or more trigger words. Without them, the effect is weak or missing.
- Put the trigger word first or near the start of the positive prompt.
- Keep the rest of the prompt simple on your first try, so you can see what the LoRA adds.
- Do not type
<lora:name:1>. That is Automatic1111 syntax. Core ComfyUI ignores it; the node does the loading. - Style LoRAs often work without a trigger word, but adding the style name still helps.
Example prompt for the blindbox test: chibi, full body, a girl in a yellow raincoat holding an umbrella, standing on a street, cute 3d toy, blind box style, soft studio lighting.
Strength Settings Explained
Load LoRA has two sliders. They do different jobs.
| Setting | What it changes | Starting value | Tip |
|---|---|---|---|
strength_model |
How strongly the image model (UNet / DiT) is changed | 0.7 to 1.0 | Main control for the look |
strength_clip |
How strongly the text encoder is changed | Same as model, or a bit lower | Affects how trigger words are understood |
| Negative values | Pushes away from the LoRA effect | -0.5 to -1.0 | Works with “slider” LoRAs (detail, age, lighting) |
| Above 1.0 | Exaggerates the effect | 1.1 to 1.3 max | Often causes burnt colours and broken anatomy |
A good habit: run the same seed at 0.4, 0.7 and 1.0 and keep the lowest value that still gives you the look you want. Lower strength keeps more of the base model’s quality.
How to Use Multiple LoRAs
You can stack LoRAs by chaining Load LoRA nodes. The ComfyUI docs show exactly this pattern.
- Add a second Load LoRA node.
- Chain it. Connect the MODEL and CLIP outputs of the first Load LoRA into the model and clip inputs of the second.
- Connect the last node only. The final Load LoRA’s MODEL goes to KSampler and its CLIP goes to both text encoders.
- Lower the strengths. With two LoRAs try 0.6 to 0.8 each; with three, 0.4 to 0.6 each.
- Add both trigger words to the positive prompt.
Stacking a style LoRA with a character LoRA works well. Stacking two strong style LoRAs often fights, giving muddy images. If that happens, lower the weaker one or drop it.
Model-Only LoRAs (Flux, Wan, Qwen-Image)
Newer models use large separate text encoders (T5, UMT5, Qwen and others). Most LoRAs for these models only change the image or video model, so you use LoraLoaderModelOnly.
- Load the diffusion model with Load Diffusion Model (or a GGUF loader, see our GGUF in ComfyUI guide).
- Add LoraLoaderModelOnly and connect the MODEL output into it.
- Send its MODEL output to the sampler (KSampler, or the model input of your guider / ModelSamplingFlux / ModelSamplingSD3 node).
- Leave CLIP alone. The text encoder loader connects to CLIP Text Encode as before.
- Chain more LoraLoaderModelOnly nodes the same way if you need several.
Speed LoRAs (Lightning, Turbo, distillation) are usually model-only too. They change the sampler settings you need: fewer steps and CFG around 1. Always follow the model card. Our Qwen-Image-Edit Lightning guide and P-H3-Image 2-step LoRA guide show real examples.
Organising a Big LoRA Collection
- Use subfolders by base model:
loras/sd15/,loras/sdxl/,loras/flux/,loras/wan/. It stops you picking the wrong family. - Rename files to include the trigger word, for example
sdxl_watercolor_trigger-wtrclr.safetensors. - Keep a notes file next to each LoRA with the source URL, strength and licence.
- Share folders with Forge or A1111 using
extra_model_paths.yamlinstead of copying gigabytes twice. - Delete what you never use. Hundreds of files slow the dropdown and waste disk space.
Want to make your own? See how to train a LoRA with the Kohya GUI, or train inside ComfyUI with ZenTrainer.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| LoRA not in the dropdown | Wrong folder or no refresh | Check models/loras, press R or restart; check extra_model_paths.yaml |
| No visible effect | Not wired to KSampler, no trigger word, or wrong model family | Make sure KSampler takes MODEL from Load LoRA; add the trigger; match the base model |
| “lora key not loaded” warnings in the console | LoRA made for another model or architecture | Use a LoRA for your exact base model; a few warnings with partial matches can be harmless |
| Burnt, oversaturated or noisy images | Strength too high or too many LoRAs | Lower to 0.5 to 0.8; remove one LoRA |
| Faces or hands get worse | Low-quality or overtrained LoRA | Lower strength; try another version of the LoRA |
| Out of memory after adding LoRAs | Large LoRAs on top of a big model | Use a GGUF or FP8 model, lower resolution, close other GPU apps |
| A1111 prompt tags do nothing | ComfyUI does not read <lora:...> |
Use Load LoRA nodes instead |
| Speed LoRA gives grey or blurry images | Wrong steps or CFG | Use the step count and CFG from the LoRA’s model card |
Still stuck after an update? See how to update ComfyUI safely, since old builds sometimes miss LoRA support for new models.
My Take
LoRAs are the best value upgrade in ComfyUI. Learn the one-node pattern first: Load Checkpoint, Load LoRA, then the sampler and prompts. After that, stacking and model-only LoRAs are small steps.
Keep strengths modest, always add trigger words, and organise files by base model. That avoids nine out of ten “my LoRA doesn’t work” problems.
FAQ
Where do LoRA files go in ComfyUI?
In ComfyUI/models/loras/. Press R or restart ComfyUI so they appear in the Load LoRA node.
What strength should I use for a LoRA?
Start at 0.7 to 1.0 for both strength_model and strength_clip, or the value on the LoRA’s page. Lower it if the image looks overdone.
How many LoRAs can I use at once?
There is no hard limit. Two or three is common. Lower each strength as you add more, or they will fight each other.
Do I need trigger words in ComfyUI?
Usually yes. Most character and concept LoRAs need their trigger word in the positive prompt. Style LoRAs often work without one.
What is the difference between Load LoRA and LoraLoaderModelOnly?
Load LoRA patches both the model and the CLIP text encoder. LoraLoaderModelOnly patches only the model, which is what Flux, Wan and most newer model LoRAs need.
Can I use SDXL LoRAs with SD 1.5 or Flux?
No. A LoRA only works with the model family it was trained on. Mixing families gives warnings and little or no effect.
Do LyCORIS, LoHa and LoKr files need a special node?
No. ComfyUI’s regular Load LoRA node loads them.
Can I use LoRAs with video models?
Yes. Wan and other video models have their own LoRAs, loaded with LoraLoaderModelOnly. See our ComfyUI image to video guide.




