Automatic1111 LoRA Not Showing | Quick Fixes That Work

When LoRA cards or names stop appearing in Automatic1111, it feels like half of your model library just disappeared. You know the files are on disk, Stable Diffusion runs fine, yet the LoRA tab is empty or only shows part of your collection. This guide walks through the real causes people hit with automatic1111 lora not showing and the step-by-step checks that bring those models back.

Most LoRA visibility problems fall into a short list: the files sit in the wrong folder, Extra Networks filters hide them, the LoRA extension or tab is disabled, the model type does not match your checkpoint, or a recent update left broken settings behind. Instead of reinstalling everything, work through the checks below from fastest to slowest.

Symptom	Likely Cause	Quick Action
No LoRA cards at all	Wrong folder or LoRA tab hidden	Confirm models/Lora path and Extra Networks settings
Only some LoRAs appear	Version filters or hidden directories	Change LoRA filters and refresh the tab
LoRA name shows but has no effect	Wrong base checkpoint or broken file	Match LoRA type to model and test with a clean prompt

Why Your Automatic1111 LoRA Not Showing Issue Happens

Automatic1111 treats LoRA files as “extra networks.” The WebUI scans one or more folders at startup, builds a list of LoRA files, then shows them in the LoRA tab and on the Extra Networks panel. If any step in that chain fails, the interface has nothing to display even though the models sit on disk.

The common failure points are straightforward. The LoRA safetensors sit in the wrong directory, often next to checkpoints instead of inside the Lora folder. Extra Networks settings may hide models by version or by directory state. Some updates ship with new defaults for “hidden directories” and “always show all networks,” so a tweak that once looked harmless can suddenly clear the LoRA list after an upgrade.

Another cause is model mismatch. SD 1.5 LoRAs, SDXL LoRAs, and special forks like anime tunes are trained against different base checkpoints. Automatic1111 can tag LoRAs with metadata and may hide those that do not match the active model when certain filters are on. In other cases the card appears, yet the LoRA never loads into the pipeline because the checkpoint type is wrong, the file is corrupted, or a third-party extension intercepts the load.

Finally, configuration files sometimes break after a large version jump. If Extra Networks or LoRA options move between versions, your old config.json and ui-config.json files can leave the LoRA extension disabled or the tab hidden. That is why “delete config and restart” comes up so often in GitHub threads when users report automatic1111 lora not showing across an entire install.

Check That Your LoRA Files Sit In The Correct Folder

If Automatic1111 cannot see your safetensors, no amount of settings tweaking will help. The first check is boring but effective: confirm that every LoRA file lives in the LoRA models directory the WebUI actually scans.

Default LoRA Folder Paths On Local Installs

On a normal desktop install, the LoRA directory sits under the main WebUI folder. In most setups that path is similar to stable-diffusion-webui/models/Lora/. Some older guides placed LoRA files under the main Stable-diffusion checkpoint folder, which worked for a while, then stopped working once the project tightened directory rules in later versions.

1. Open Your WebUI Folder — Locate the main stable-diffusion-webui directory on your drive.
2. Find The Models/Lora Directory — Open models, then confirm that a Lora subfolder exists. Create it if needed.
3. Move LoRA Files Into Lora — Place every .safetensors and .ckpt LoRA file into this single Lora folder instead of scattering them across other model folders.
4. Remove Extra Copies — Delete or archive stray copies of the same LoRA in other directories so the WebUI only has one path to scan.

Paths On Cloud Hosts And One-Click Installs

Managed services often mount the LoRA folder under a custom root. ThinkDiffusion, RunPod templates, and similar setups point Automatic1111 to a mapped models/Lora folder inside a user data area. Many users drag files into the wrong place in the container, which leaves the LoRA tab empty even though disk usage jumps.

1. Check The Host’s Docs — Open your provider’s help page and search for “LoRA folder” or “models/Lora path” to find the correct directory for that template.
2. Upload Directly To The Mapped Folder — Use the built-in file browser or SSH to copy LoRA files into that exact directory path.
3. Restart The WebUI Session — Stop and start the web UI from the control panel so it rescans the LoRA directory.

Once the folder path is correct and the WebUI restarts, many “LoRA not showing” reports resolve instantly, especially on fresh installs where every other setting still sits at default values.

Fix Hidden Or Missing LoRA Tabs In The Interface

Even with perfect folder paths, LoRA cards can vanish when Extra Networks settings hide the tab or filter out cards. Automatic1111 gives you fine control over which network types appear, but the checkboxes and filters can be confusing after an update.

Reveal The LoRA Tab And Enable The Extension

1. Open Settings — In Automatic1111, click the Settings tab at the top right of the interface.
2. Go To Extra Networks — In the left sidebar, choose Extra Networks. Look for a section that lists network types, including LoRA.
3. Enable The LoRA Entry — Make sure the LoRA option is ticked so the WebUI knows to scan and render LoRA cards.
4. Apply And Restart — Click Apply settings, then hit Reload UI or restart the WebUI process to load the LoRA extension cleanly.

On some versions, Extra Networks also controls whether the LoRA tab appears as a top-level tab next to “txt2img” and “img2img.” If the extension checkbox is off, the entire tab can disappear, which leads users to think the feature was removed.

Clear Filters That Hide Existing LoRA Cards

When the LoRA tab is visible but only shows a fraction of your files, filters are usually the culprit. Extra Networks ships with options for version compatibility and for hiding cards that sit in directories treated as hidden. One strict setting can cut your visible list down to a handful of models.

1. Open The LoRA Tab — Click the LoRA tab above the prompt area, then find the search bar and filter controls near the top.
2. Clear Search Text — Delete any typed search text so the list is not limited by a partial name filter.
3. Reset Version Filters — In Settings > Extra Networks, turn on options such as “Always show all networks on the LoRA page” so SDXL LoRAs still appear while you run SD 1.5 checkpoints.
4. Change Hidden Directory Rules — If “Show cards for models in hidden directories” is set to “Never,” change it to a less strict option, apply, and restart.
5. Use The Refresh Icon — In the LoRA tab header, click the small refresh icon to rescan the directory without a full restart.

With filters relaxed, a refresh usually restores the full set of cards. If the tab still shows nothing, return to the folder checks and confirm that the models sit in a non-hidden directory the WebUI can reach.

Match LoRA Types To The Correct Checkpoint Model

Even when the LoRA tab looks healthy, you might see a different kind of problem: the name appears, you apply it to the prompt, yet the output image looks unchanged. That can be a sign of a broken file, but with Automatic1111 it more often points to a mismatch between the LoRA’s base model and the active checkpoint.

LoRAs carry metadata that states which base model they expect. SD 1.5 anime LoRAs work best with SD 1.5 anime checkpoints, SDXL LoRAs with SDXL base models, and so on. Some WebUI builds filter LoRAs by version in Extra Networks; others still show them but throw warnings or silently skip them during generation. Either way, picking a checkpoint that matches the LoRA’s training base removes a whole category of “this LoRA does nothing” complaints.

LoRA Type	Works Best With	Typical Problem When Mismatched
SD 1.5 character LoRA	SD 1.5-based checkpoints	Style barely changes or faces look generic
SDXL LoRA	SDXL base and SDXL finetunes	LoRA card may hide under strict filters or fail silently
Special fork LoRA	Matching fork (anime, pony, etc.)	Garbled shapes, heavy artifacts, or no visible effect

1. Read The LoRA Page — On CivitAI or the model’s download page, check the “trained on” or “base model” section.
2. Select A Matching Checkpoint — In Automatic1111, choose a checkpoint that lines up with that base model before you apply the LoRA.
3. Test With A Simple Prompt — Use a short prompt that calls the LoRA’s trigger word and a high weight, such as <lora:loraname:1.0>, plus a generic subject.
4. Check The Console Log — Watch the terminal window while you generate; if the LoRA fails to load, the log may mention missing networks or skipped weights.

If the WebUI console mentions “failed to find networks” or similar messages, return to the folder and Extra Networks checks. That line usually means Automatic1111 could not map the LoRA file it found on disk to the network type the current build expects.

Reset Settings And Extensions When LoRA Still Not Showing

When paths and filters look correct, yet LoRA cards still refuse to appear, corrupted settings or an extension conflict become prime suspects. Large updates, partial Git pulls, and aggressive theme extensions can all leave Extra Networks in a strange state.

Test With Extensions Disabled

1. Open The Extensions Tab — In Automatic1111, click Extensions at the top of the interface.
2. Switch To Installed — Go to the installed extensions list to see every add-on currently loaded.
3. Disable Non-Core Extensions — Temporarily disable anything that is not part of the base project, especially model browsers, theming add-ons, and LoRA managers.
4. Apply And Restart — Hit Apply, then restart the WebUI and check the LoRA tab again with only core features active.

If the LoRA tab comes back with extensions disabled, turn them on one by one until the problem returns. That narrows down the offender, and you can then update, replace, or remove that add-on instead of wiping the whole install.

Clean Up Config Files After Large Updates

Old configuration files sometimes carry references to settings that no longer exist in newer builds. Automatic1111 usually handles this gracefully, yet Extra Networks can behave oddly when option names change across versions. A quick reset of UI configuration often restores missing tabs and default filters.

1. Shut Down The WebUI — Close Automatic1111 and make sure the terminal window is no longer running any server process.
2. Backup Config Files — In the WebUI root directory, copy config.json and ui-config.json to a safe backup folder so you can restore them if needed.
3. Delete The Originals — Remove the original config files from the WebUI directory. Do not touch your models folder.
4. Restart Automatic1111 — Launch the WebUI again. It will rebuild fresh config files with default Extra Networks and LoRA settings.
5. Re-Apply Only Needed Tweaks — Set your theme, paths, and performance options again, leaving LoRA-related settings at defaults until you confirm that cards appear.

This reset step feels heavy, yet it saves time when a silent config error keeps the LoRA tab empty across multiple restarts and updates.

Quick Health Checks To Keep LoRA Visible In Automatic1111

Once everything works again, a few small habits will keep LoRA cards from vanishing in the middle of a project. These checks fit nicely into your normal model-management routine and reduce surprises after updates.

1. Keep A Single LoRA Library — Store all LoRA files under one models/Lora directory instead of spreading them across multiple folders.
2. Label LoRAs By Base Model — Add short tags such as “sd15,” “sdxl,” or “anime” to file names so you can pair them with matching checkpoints at a glance.
3. Avoid Overly Aggressive Filters — Leave Extra Networks options on defaults unless you have a specific reason to hide cards or directories.
4. Update Gradually — When pulling WebUI updates and new extensions, change one thing at a time so you can spot which change breaks LoRA visibility if it happens again.
5. Check The Console When Something Feels Off — Keep the terminal window visible while you work; many LoRA errors print there long before the interface shows symptoms.

With folder paths cleaned up, Extra Networks set to show all relevant cards, and LoRAs paired to matching checkpoints, Automatic1111 handles even large LoRA libraries without trouble. If you ever hit automatic1111 lora not showing again, walk back through these checks from top to bottom, and you should reach the fix in a few minutes instead of burning hours on a full reinstall.