Nexus
What is Nexus UI Web?
Bring existing Web UIs and frontend components into Blender. Reuse your Python logic and extend scene, state, and file interactions as needed.
Bring familiar web interfaces into Blender
Nexus UI Web turns existing HTML, CSS, and JavaScript interfaces into tool windows inside Blender editors. Keep the layouts, components, and interactions from plain web pages, React, Vue, or other frontend projects. Deliver static pages that can load locally, then connect Blender features with Python.
For a material tool, the web page handles thumbnails, filtering, and parameter layouts; Python reads or changes Blender data; and the framework hosts the page, forwards input, and connects both sides. Reuse your existing interface and add features through the public APIs as you need them.
Illustrative workflow. The website does not connect to local Blender.
When it fits
- Flexible layouts. Build cards, tool panels, canvases, or complex editors beyond a single fixed control arrangement.
- Reuse existing web pages. Keep your design, components, and frontend toolchain. Put the built static files in your add-on and connect the Blender operations you need.
- Extend your tool with new features. Combine tables, charts, node editors, or canvases in one tool. Connect Python through actions, update the interface through state, and add file and resource interactions as needed.
- Work inside the editor. Declare size, placement, and transparency, then separate drag and control regions in the page.
For a few standard buttons, native panels may be simpler. Web UI adds pages, logic, integration, and matching runtime maintenance. Read Window guide and Connecting the interface to Blender before deciding whether the flexibility is worthwhile.
Distinguish the parts
| Part | What it provides | How to use it |
|---|---|---|
| Framework | Windows, input, communication, and resources. | Embed manifest-listed files and call public APIs. |
| Runtime components | Programs for local web execution and rendering. | Installed in a shared user-level location, matched to the embedded framework. |
| Your add-on | Specific operations, pages, and application data. | Start from a template or integrate into an existing project. |
| Official examples | Complete use cases and reference usage. | Read and try them; do not depend on internal example helpers. |
| Third-party frontend libraries | Specific controls, canvases, node editors, and other UI features. | Follow their documentation/licenses and ship required output with the page. |
An example canvas or node effect does not mean the framework includes that application feature. It hosts the interface; corresponding code implements the behavior.
Know the boundaries
The Python bridge is for trusted local pages. Browser previews check appearance; development-server and remote pages lack this bridge. Verify windows, input, and application results in Blender.
Local pages need no persistent server or frontend development tools for users. Online page services still require networking; runtime installation and update checks have their own network conditions. Environment and network boundaries →
Ordinary buttons do not automatically become Blender features. Connect operations, handle failures, and invalidate state after changes. Undo, progress, and long-task handling are not automatically provided by integration.
Relationship to NexusUI
Nexus UI Web originated from NexusUI's Web component and now works independently without installing NexusUI. Use current templates, documentation, and public APIs rather than the old implementation.
An add-on may use both frameworks in separate windows, not mix their controls, layouts, or dialogs in one window.
Start here
Confirm your computer, Blender, and runtime meet requirements.
Materials readyBuild your first add-on →Open a window and complete a read-only scene call.
If you already have a web page or frontend project, start with Migrating web pages and extending components or Integrate into an existing add-on to choose your route.