Nexus
Requirements and support
An add-on includes an embedded framework and local pages, and needs matching runtime components. Blender 5.0.0 and later, Apple silicon Mac · Windows x64.
Check your computer and Blender
Supports Apple silicon Mac · Windows x64. Runtime components are not currently available for Intel Macs or Linux.
| Item | Current requirement | Meaning |
|---|---|---|
| Blender | 5.0.0 and later | The declared minimum does not mean every later version has been individually tested. |
| Mac | Apple silicon, arm64 | Use matching Blender/runtime architecture. Intel Mac runtime components are unavailable. |
| Windows | x64 | Use Windows components; Mac packages cannot substitute. |
| Other platforms | No current runtime components | Copying Python/pages alone cannot add Linux or Intel Mac support. |
Check the Blender version actually running, not merely installed. Real windows also depend on local graphics. Meeting declarations is a starting point; opening and performing an operation establishes results on this computer.
Add-on and runtime installation
Add-on package Contains your Python logic, local pages, and embedded framework. Runtime components Installed separately in a shared current-user location, not inside every add-on.
Separate framework copies are intentional. Do not delete other add-ons' copies to deduplicate. Match runtimes by real compatibility, not similar directory names or version numbers.
For missing, damaged, or incompatible components, follow Install and check runtime components. Users need not compile Chromium/CEF or install repository maintenance tools.
Building and using require different tools
| What to do | Required |
|---|---|
| Use a finished add-on | A supported Blender version, the add-on package, and matching runtime components. Local pages ship with the add-on, so users do not need to start a frontend development server. |
| Build with the starter tutorial | Also needs matching source, template, editor, and runnable Python 3.11+ for the copy tool. |
| Use frontend build tools | Prepare the chosen toolchain and ship built static output. The plain-web starter template does not require Node.js. |
| Migrate an existing web interface | Prepare the page source or static build output and its assets. Keep using your editor and build tools, and connect operations that need Blender to the add-on's Python actions and state. |
| Maintain the framework or run source checks | First follow First-time development setup to install check dependencies, then add current-platform compile tools as determined by the gate. Full checks also require these tools when a source archive has no known change scope. This is separate from an add-on author's page development environment. |
Blender's bundled Python does not guarantee a runnable terminal
python3
command. If the copy tool cannot start, check the interpreter rather than assuming missing runtime components.
Where networking is needed
- Local interface: Files ship with the add-on and need no persistent server. Online application features have their own network requirements.
- First online installation: Showing a missing-runtime notice does not connect. Download begins only after Download & Install.
- Offline installation: Obtain a matching ZIP beforehand and use Local Package…. Installation itself needs no network.
- Compatible updates: When Blender permits online access, usable runtimes can check updates regardless of installation source. Identical packages are not repeatedly offered. Historical packages without versions show Not recorded and offer a compatible installation. Checking does not install automatically.
Offline-capable local pages do not mean every installation source or feature never connects. Prepare add-on, matching runtime, and local assets for offline delivery.
What browser visibility does not prove
Browser previews check color, layout, and page interactions, not Blender communication, host dragging, transparent hit testing, writeback, or local runtime health.
Development-server and remote pages have no Blender bridge. Ship loadable local pages and follow First-build tutorial to verify real results.
For system blocks or organizational device policy, inspect exact messages and contact administrators. Disabling protection is not a routine installation step.