Add-Ons Not Showing Up In Blender | Fix Install Paths

If you just installed an add-on and it’s missing from the list, you’re not alone. Most “ghost installs” come from a small set of causes: a zip with an extra folder layer, a script placed in the wrong version folder, a filter hiding it, or an error that stops it from registering.

This guide walks through the checks that solve the issue in minutes, then the deeper fixes that catch the stubborn cases like multiple Blender installs, custom script paths, and broken preferences files. You’ll end with a repeatable way to install, enable, and verify add-ons without guesswork.

Add-Ons Not Showing Up In Blender

When add-ons don’t appear, it helps to separate two moments: install time and enable time. Install time is when Blender copies the add-on into an add-ons folder. Enable time is when Blender loads it, checks metadata, and adds it to the interface.

If install time fails, Blender often gives little feedback, especially when the zip structure is wrong. If enable time fails, you may see an error banner, or the checkbox flips off again after you click it. Both paths have clean fixes once you know where to look.

In Blender 4.x, you may also see “Extensions” features next to older add-on tools. Legacy add-ons still exist, and Blender’s manual still documents installing them from disk by selecting a single .py file or a folder that contains the add-on code.

Start With These Fast Checks First

Run these in order. Each one can hide an add-on that is installed and fine.

Symptom	Likely Cause	Fix To Try
Add-on list looks empty	Category or filter is active	Clear filters and search by name
Add-on installs but never appears	Zip has extra folder layer	Extract and install the inner folder
Checkbox won’t stay enabled	Python error on load	Open the console and read the error
Add-on worked yesterday	Version folder changed after update	Copy add-on into the new scripts/addons path

• Clear Filters — In Edit > Preferences > Add-ons, disable category toggles and remove any typed filter text, then search again.
• Search By A Unique Word — Use a short token from the add-on name, not “tools” or “utility.” Many add-ons share common words.
• Enable It On Purpose — Find the add-on entry and tick the checkbox. If it turns off right away, jump to the error section below.
• Confirm You’re In The Right Blender — If you have more than one Blender build, open Help > About Blender and check the version number you are running.

If you’re stuck at the first step because the Add-ons tab itself looks different, check whether you’re in Preferences at all. Blender’s manual shows the Add-ons panel and the install flow, including the “Install from Disk” option for legacy add-ons.

Fix The Install File And Folder Structure

Blender expects a specific layout when you install from disk. If the zip contains one .py file at the top level, selecting that file often works. If it’s a folder-based add-on, Blender needs the folder that contains the __init__.py file and the rest of the package.

A common failure is a “double folder” zip: you install the zip, Blender stores it, yet the real add-on code sits one folder deeper, so Blender never sees it. Community answers point out that you should extract the archive and then pick the deepest folder that still contains the add-on package, not the outer wrapper folder.

1. Inspect The Zip — Open the archive and look for __init__.py. If you see it inside AddonName/AddonName/, you have a wrapper folder problem.
2. Extract To A Clean Folder — Unzip into a short path like Desktop/AddonsTemp so you can see the nesting at a glance.
3. Install The Correct Target — In Preferences > Add-ons, use Install from Disk and select the inner folder (or the single .py file) that contains the code.
4. Restart Blender Once — Some add-ons register menus on startup. A restart also confirms the install survived a reload.

Also check file types. Blender’s manual notes that legacy add-ons are installed by choosing a .py file or a folder, not a random text file or a compiled installer. If the download is an .exe or a .msi, it may be a separate app, not a Blender add-on.

Check Version Compatibility And Python Errors

When an add-on is present in the list but won’t enable, treat it like a startup error. The fastest path is to read the actual error message Blender logs, then act on it.

• Open The System Console — On Windows, use Window > Toggle System Console, then enable the add-on and watch the traceback output.
• Read The First Real Error Line — Ignore long stacks at first. Look for missing modules, syntax errors, or version checks.
• Check The Blender Version Range — Many add-ons declare a minimum Blender version. If the add-on was built for 2.9x and you are on 4.x, it may fail on API changes.
• Update The Add-On Build — Download the release that matches your Blender branch. Some vendors ship separate builds for LTS releases.

One more gotcha: Blender may show an add-on only after it reads the metadata inside the package. If a zip is missing __init__.py, or the file header is broken, Blender can’t register it in the list.

Common Error Patterns And What They Mean

• ModuleNotFoundError — The add-on expects a Python package that isn’t present. Some add-ons bundle it, some require a separate install path.
• SyntaxError — The add-on code was written for a different Python version. Blender updates Python over time, so older scripts can break.
• PermissionError — Blender can’t read or write the add-on folder. This shows up with locked directories or restrictive installs.

Confirm Script Paths And Where Blender Stores Add-Ons

If your add-on seems to “install” but disappears after a restart, Blender might be writing to one scripts location while you are checking another. Blender uses user and system directories, and the exact path changes by OS and Blender version.

In Preferences > File Paths, Blender lets you add a user scripts path. Blender’s manual notes that adding a user script path makes Blender use an extra directory for scripts and add-ons, which is handy when you want a separate folder that survives upgrades.

1. Check Preferences Paths — Go to Edit > Preferences > File Paths and review any custom script entries you set earlier.
2. Locate The User Addons Folder — On Windows it sits under your AppData roaming folder, on macOS under Library/Application Support, and on Linux under .config, all inside a versioned Blender folder.
3. Compare Version Numbers — Blender stores add-ons under a folder that matches the major.minor version. After an upgrade, 3.6 and 4.2 are different folders.
4. Test With A Portable Install — A portable zip build can store scripts next to the executable, while an installed build uses the user directory. Blender’s directory layout docs outline these locations.

If you’re on Windows Store builds, directory paths can be different from the classic installer. Blender’s directory layout section for Windows Store installs calls out that user and system directories sit inside a special package folder.

Reset Preferences Safely When Nothing Else Works

Sometimes the install is fine and the add-on is fine, yet your config is the part that’s broken. A corrupted preferences file, a bad startup script, or an old path setting can block add-ons from loading.

Do this in a way that keeps your work safe. You can reset Blender’s config without deleting your projects, and you can back up the scripts/addons folder before you touch anything.

1. Back Up Your Config Folder — Copy the whole Blender version folder from your user directory to a backup location.
2. Move Add-Ons Out Temporarily — Create an “addons_hold” folder and move third-party add-ons there, then launch Blender to confirm it starts clean.
3. Reset Blender To Factory Settings — Use Blender’s built-in reset option or start with a fresh config folder name, then re-enable add-ons one by one.
4. Add Back Only What Works — Return add-ons in small batches, restarting between batches to pinpoint the one that triggers errors.

After the reset, install one known-good add-on and confirm it appears. Then install the one you really want. If add-ons not showing up in blender was caused by a bad path or a broken config file, this step clears it fast.

Keep Add-Ons Stable Across Updates

Once everything is visible again, set yourself up so the problem doesn’t return at the next Blender update. Most people get burned by versioned folders and scattered installs.

• Use One Add-Ons Folder — Pick a single user scripts directory and point Blender to it in Preferences so upgrades don’t strand your add-ons in older version folders.
• Name Your Downloads Clearly — Store zips in a folder that includes the Blender version, like “Addons_4_2,” so you can match builds later.
• Keep A Simple Install Checklist — Verify zip structure, install, enable, restart, then test the menu entry in the UI.
• Log Errors Right Away — When an enable attempt fails, copy the console error into a note. That one message often points straight to the fix.

Quick Fixes For Blender 4.x Extensions Screens

If you installed something through the Extensions area and it still doesn’t appear in the interface, check two things: whether the item is enabled, and whether Blender can reach the repository you selected. A local repository can work, but the folder must match the structure Blender expects for extensions.

If you meant to install a classic add-on, skip Extensions and use Install from Disk in the Add-ons panel. Blender’s manual still documents this workflow for legacy add-ons, and it avoids confusion when an item is packaged as a normal add-on zip.

• Switch To The Add-Ons Tab — Use Edit > Preferences > Add-ons, then run a search again after install.
• Disable “Only Enabled” — If the list is set to show enabled items only, a new add-on can hide until you tick it on.
• Refresh After Changes — Close Preferences, reopen it, then search once more to confirm the list is updated.

Also watch for mixing extensions and legacy add-ons in new Blender releases. The manual’s Add-ons and File Paths pages are a steady reference for what Blender expects, even as the interface shifts between versions.

If you still see add-ons not showing up in blender after all steps, the last suspect is a mismatch between the add-on’s intended install method and the file you received. At that point, open the add-on’s readme and match its folder layout to Blender’s add-ons install rules.

Save a startup file only after you confirm your add-ons load on restart.