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. 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.
Make plugins for Figma products
This article outlines the plugin development process in Figma. We designed this as a supplementary resource to our developer documentation.
- Create a plugin for development
- Build and test your Plugin
- Publish a plugin to the Figma Community
- Manage plugins as a developer
Check out our Plugin API documentation for a complete guide on making plugins for the Community.
You must have the Figma Desktop app installed to make plugins.
Figma Plugin Examples
Here's some examples of existing Figma plugins:
- Content Buddy: Find text within your designs and replace it with the actual copy.
- Themer: Swap between published styles from your libraries, in bulk.
- Content Reel: Bring data into your designs. Including text strings, avatars and icons.
- Map Maker: Insert customized maps into any shape layer.
- Figmotion: Animate objects within a Frame, without having to leave Figma.
- Stark: Checks the contrast of a selected layer against WCAG 2.1 guidelines.
Sell plugin source code
Note: Ownership of paid plugins cannot be transferred.
If you’re interested in selling the source code and ownership of plugins you’ve built, do the following:
- The buyer and seller must reach out to the Support team at firstname.lastname@example.org to facilitate the sale. For example, the seller emails Support with the buyer cc'd or vice versa.
- The seller must confirm that they are authorizing the sale.
- The buyer confirms they will abide by our Terms of Service after the sale.
Once this process is complete, the Support team transfers ownership of the plugin between parties.
Keep in mind that once a plugin has been published, the publisher cannot materially change the purpose or nature of the plugin. In order to do so, a new plugin must be published and reviewed again.