What are plugins?
Plugins are third-party scripts or applications that extend the functionality of Figma's products. You can use plugins to customize your experience and create more efficient workflows.
Types of plugins
In Figma, there are two types of plugins that are categorized by the method in which they’re built:
- Classic plugins, where your development environment is hosted locally on your computer
- Generative plugins, where you build via prompting the Figma agent in design files
Classic plugins interact with Figma using the Plugin API. The Plugin API is built around a set of fixed controlled endpoints. This ensures your plugins won't break when Figma releases new features and updates.
- The Figma Plugins API gives both you read and write access to Files.
- Plugins can also use external Web APIs such as the Google Maps API. This allows you to create plugins that can view, modify and create objects or layers.
- Plugins are usually short-lived and are always manually invoked by the user. They can run immediately, or may require input from the user before applying any changes.
If you are interested in building a plugin, there are some key distinctions between classic and generative plugins that may influence which method you wish to take. These differences are laid out in the comparison table below:
| Classic plugins | Generative plugins | |
|---|---|---|
| Backed by | Figma Plugin API | Figma Plugin API |
| Environment | Local; Built in your own development environment and hosted in your local database. | Figma Design; Built via prompting Figma’s agent in Figma Design, and hosted on Figma’s database. |
| Third-party API Calls | Supported | Not supported |
| UI customization | Full customization of look and feel | Uses assets from Figma’s PropsKit components and therefore looks native to Figma files |
| Cost | Free to build and publish | Costs AI credits to build; Free to run the tool |
| Monetization | Supported, optional | Not supported |
| Shareability | Private plugins for Org; Publishable to Community | Private plugins for Org; Publishable to Community |
Overall, classic plugins are suitable for developers who are familiar with how to code and the development lifecycle, or who need full control over the style and feel of a plugin.
On the other hand, generative plugins are best for those are not familiar with code, or want their plugins to look native to Figma.
Resources
Classic plugins
To get started on building a classic plugin, check out Figma's article series on making classic plugins for the Figma Community and the Build Your First Plugin course.
If you’re ready to share your classic plugin, learn how to share publish the classic plugin to the Figma Community and optionally monetize your classic plugin. Organization admins can also publish the classic plugin privately to their organization.
Generative plugins
To get started with generating plugins, check out the guide on how to generate plugins with the Figma agent.
If you're ready to share your generative plugin, you can publish the generative plugin to the Figma Community. Organization admins can also publish the generative plugin privately to their organization.