How to Install Blender Add-ons (2026)

If you have installed a Blender add-on before and came back to a newer version confused, you are not imagining things. Blender 4.2 LTS replaced the old Install… button with an Extensions system, and the two now live side by side. There are four working ways to get an add-on into Blender, and which one you want depends entirely on where the add-on came from.

This guide covers all four, with the exact menu paths as they exist in Blender 4.2 LTS through 5.2 LTS. Getting an add-on in is one problem; keeping it updated is a separate one with its own rules.

Quick answer

Where the add-on came from	Use this method
extensions.blender.org	Edit ▸ Preferences ▸ Get Extensions, search, click Install
A website with an "Install in Blender" drag link	Drag the link straight onto the Blender window
A `.zip` you bought or downloaded (Superhive, Gumroad, GitHub)	Preferences ▸ Add-ons ▸ ▾ ▸ Install from Disk
A single loose `.py` file (older add-ons)	The same Install from Disk, pick the `.py`
A folder of loose `.py` files	Add a Script Directory in File Paths

Extensions vs. add-ons: what actually changed

An add-on is the old concept — a Python script that extends Blender. An extension is the packaging and distribution format introduced in 4.2: the same Python, plus a blender_manifest.toml that declares an ID, a version, a Blender version range, a license, and any Python wheels it needs.

The practical differences that affect you as a user:

Extensions installed from a remote repository can be updated from inside Blender. Blender knows where they came from.
Extensions installed from disk land in a local repository. Blender has no idea where they came from, so it will never offer you an update for them.
Legacy add-ons (a bare .py, or a .zip with an old bl_info block and no manifest) still install and still work. They also never auto-update.

That last point is the one that bites people. If you paid for an add-on and installed the .zip by hand, Blender is not going to tell you when 2.4 ships. Nothing is broken — Blender simply has no update channel for a file you handed it. Most commercial add-ons solve this with their own in-add-on update check; that is the problem Project LEUC exists to make trivial for developers to add.

Method 1: Install from the Extensions platform (recommended)

This is the path with real update support, so use it whenever the add-on is listed there.

Edit ▸ Preferences ▸ Get Extensions.
The first time, Blender asks you to Allow Online Access. Approve it — without it Blender cannot reach the remote repository at all, and the list will sit there empty.
Type the add-on name into the search field.
Click Install on the result.

The extension is installed and enabled in one step. It then appears under Add-ons with a checkbox, and Blender will offer updates for it.

Empty list, endless spinner, or a connection error? It is nearly always Allow Online Access being off, a corporate proxy, or a firewall. Try Refresh Remote in the Extension Settings dropdown (the ▾ at the top right) before assuming the add-on is missing.

Method 2: Drag the install link onto Blender

Many extension pages offer a drag-and-drop install link. Drag that link from your browser onto an open Blender window and Blender resolves it, downloads it, and installs it.

This is the fastest route when you are already browsing the web, and unlike a manual .zip, Blender records the source repository — so updates still work afterwards.

Method 3: Install a .zip from disk

This is what you use for anything bought on Superhive (formerly Blender Market), Gumroad, or downloaded as a release asset from GitHub.

Edit ▸ Preferences ▸ Add-ons (or Get Extensions — either works).
Click the ▾ dropdown at the top right of the panel.
Choose Install from Disk…
Select the .zip file. Do not unzip it first.
If the add-on does not switch itself on, tick the checkbox next to its name.

You can also just drag the .zip from your file manager onto the Blender window — same result, fewer clicks.

The single most common mistake

People unzip the archive, then try to install the inner folder or one of the .py files inside it. That fails, or half-installs.

Install the .zip exactly as you downloaded it. The one exception: some vendors ship a wrapper archive containing documentation plus the real add-on .zip. If you unzip and find another .zip sitting next to a PDF, that inner .zip is the one to install.

Method 4: Legacy .py add-ons

Older add-ons distributed as a single .py file still work.

Use the same Install from Disk… item and select the .py. Blender copies it into your add-on directory. It will not be enabled automatically — tick the checkbox yourself.

A folder of loose .py files

If the add-on is a folder full of .py files with no packaging, Install from Disk cannot take it. Register the folder as a script directory instead:

Create an empty folder somewhere permanent, e.g. D:\blender_scripts.
Inside it create a subfolder named exactly addons. The name matters — Blender looks for that literal directory.
Put the add-on folder inside addons.
Preferences ▸ File Paths ▸ Script Directories ▸ +, and point it at D:\blender_scripts.
Save preferences and restart Blender.

Everything under that folder shows up in the add-on list, ready to enable.

Enabling, and what to do when nothing happens

Installing and enabling are separate steps. An installed add-on with an unticked checkbox does nothing at all.

After enabling, expand the arrow to the left of the add-on's name. You get its description, its Location (which menu or panel it lives in — invaluable when you cannot find the thing you just installed), a documentation link, and its Preferences section.

Check those preferences. A surprising number of add-ons ship with their most interesting features defaulted to off.

If enabling throws an error or silently does nothing: open the console. On Windows that is Window ▸ Toggle System Console; on macOS and Linux, launch Blender from a terminal and read the output there. The traceback almost always names the real problem — usually a Blender version mismatch or a missing Python dependency.

Where installed add-ons actually live

Worth knowing for backups, for syncing a setup between machines, and for cleaning up after a bad install. On Blender 5.2 — substitute your own version number:

Windows — %USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\5.2\
macOS — ~/Library/Application Support/Blender/5.2/
Linux — ~/.config/blender/5.2/

Inside that folder, extensions/ holds the 4.2+ extensions and scripts/addons/ holds legacy add-ons.

Two useful consequences. Copying that folder to a new machine carries your entire add-on setup with it. And if an add-on is so broken that it prevents Blender from starting, you can delete its folder from disk without opening Blender at all.

Upgrading an add-on you already have

For extensions from a remote repository: Get Extensions ▸ ▾ ▸ Refresh Remote, then Update All, or update them one at a time. Blender does not check on its own unless you turn on Check for Updates on Startup in the repository's settings — worth turning on.

For anything installed from disk, you are on your own. The safe sequence is: remove the old version, restart Blender, install the new .zip. Installing over the top usually works and occasionally leaves orphaned files from renamed modules, which produces the class of bug that survives a restart and makes no sense.

If you develop add-ons and would rather your users stopped doing this dance manually, that gap is exactly what Project LEUC fills — one endpoint your add-on calls to learn whether a newer version exists, so the update prompt appears inside Blender instead of in an email nobody reads.

Troubleshooting checklist

"Add-on is not compatible with this version of Blender" — the manifest declares a Blender version range and yours falls outside it. Check the add-on's page for a build matching your Blender.

Installed and enabled, but I cannot find it — expand the add-on entry and read its Location field. Many add-ons live in the N-panel (press N in the 3D viewport) rather than adding a top-level menu.

Blender is slow to start after installing several add-ons — every enabled add-on runs its registration code at launch. Disable what you are not using this week, or use a loader that defers them — fixing Blender's startup time covers how to measure the real cost and what to cut.

Everything broke after installing something — start Blender with --factory-startup to load with no add-ons at all, then re-enable them one at a time to find the culprit.