Plugins
Plugins extend Studio itself. A plugin is a folder of files that runs inside the editor without anything being rebuilt — it can add a panel, generate scenes, process resources, or add a new kind of component to objects.
Want to build one? → Writing a plugin.
The plugins panel
Two tabs.
My uploads — your local development folders, your published plugins and the ones you installed, in one list. From here you can create a plugin, open an existing folder, reload it from disk, publish or unpublish, and delete.
Library — the shared registry: search, tags, screenshots, author, rating, install count and favourites. Your own and installed plugins rank higher in results.
Search spans both: type a query and the tabs collapse into a single list, yours first.
Installing
Installing adds a plugin to your editor. Its icon appears in your toolbar.
Adding it to a project is different: the plugin then appears for everyone who opens that project, not just you. That is the right choice for a plugin your whole team needs — a house style checker, a scene generator you all use.
Removing a plugin from the registry removes it from every project that used it.
Trust
Opening someone else's plugin asks for confirmation once, because it can read and change your scene and resources. "Do not ask again" remembers your answer for that plugin.
Treat the library the way you would treat any third-party extension: install what you have reason to trust.
What verification means
A verified plugin is not "a good plugin". It means someone read this exact code.
Verification is tied to a fingerprint of the plugin's contents. Publishing new code changes the fingerprint, so a verified plugin drops back to pending until it is looked at again. Editing the description, tags or screenshots does not — those do not run.
A verification can waive up to three separate things:
| Waives | Means |
|---|---|
open | no confirmation dialog when you open its panel |
autorun | its self-starting parts may run without asking — see below |
warnings | the "we do not review plugin code" notices are hidden |
An empty set is possible: the badge alone, with every prompt still in place. "We read the code" and "we will stop asking you" are deliberately different promises.
A panel runs when you open it. A component extension or a viewport overlay runs every
time anyone opens the project. That is why autorun is waived separately, and why an untrusted
plugin's self-starting parts do not mount at all.
Statuses are none, pending, verified, rejected and revoked. A revoked verification
also clears your local "do not ask again" — that consent was about different code.
Ratings and premium
One rating per person, one to five stars. Some plugins are marked as requiring a subscription; your own are never gated.
What you need
The development side needs a Chromium-based browser, because reading a local folder uses the File System Access API. The library works everywhere — only building plugins from a local folder needs Chromium.
Next: Writing a plugin