Using plugins
Plugins extend the editor with new tools and panels — gradient generators, content importers, icon packs, AI helpers, whatever the community builds. They run sandboxed, isolated from the rest of the editor.
Find a plugin
Open the command palette with ⌘K and go to the Plugins / Marketplace section. Search by name, and you'll see each plugin with its author and description.
Install
Each marketplace plugin offers up to two install options:
- Add to project (Cloud) — installs the plugin as a cloud plugin. Your project keeps a pointer to it; it loads from the marketplace and updates automatically when the author ships a new version (you'll see an "update available" notice).
- Import locally — copies the plugin's source into your project as an editable file. It stops following the author's updates (it's now your fork), and you can open and change it. This is only offered for plugins whose authors published their source as open.
You can also paste a plugin's share URL into the command palette to install it directly — handy when someone sends you a link to their plugin.
Run a plugin
Installed plugins appear in the Library → Plugins section and in the command palette. Launch one and it opens as a floating panel beside your design. Resize or drag it; close it when you're done.
Manage your plugins
From the Library → Plugins section you can:
- Launch, or remove, any installed plugin.
- Organize project plugins into folders.
- See cloud plugins grouped by their author.
Is it safe?
Yes — by design. Every plugin runs in a sandboxed iframe and can only reach the editor through a permission-checked SDK. A plugin can do exactly what its manifest declares (edit the canvas, read the CMS, upload images, …) and nothing more, and it can't read the editor's internals or other plugins' data. Marketplace plugins are reviewed against their published source before they go live.
Build your own
Anyone can write a plugin — in the editor or as a local project — and publish it. See Building a plugin and Submitting plugins.