How to add a plugin in Figma on Mac: step by step for Figma desktop

Figma runs community plugins from the Tools tab inside a design file. That is the route in Figma's own help article, and this guide follows it. You will also find older guides that describe an Actions button and a Save step. Both routes are covered below, so you can match what your screen shows.

What you need before you start

You need edit access to the file. Figma's help article says you must have edit access to run plugins. A view-only link opens the file, but it does not let you run a plugin. Ask the file owner for edit rights if you cannot run anything in the file.

• The Figma desktop app for Mac, installed in /Applications or ~/Applications
• Edit access to the Figma Design file you are working in
• A Starter or Full seat, since Figma lists Figma Design plugins for those seats
• No admin rule that blocks the plugin you want

The desktop app is the route this guide uses. Figma's deploy help says the Mac app installs to /Applications for all users or to ~/Applications for a single user. The Universal installer supports both Intel and Apple silicon Macs. If you have not installed the app yet, follow the install guide first.

Which plans and seats can run plugins

Plugin access depends on your seat. Figma's help article lists Figma Design plugins for Starter and Full seats. Dev, Collab and View seats are not on that list for Figma Design. The table shows the split for the three product areas that Figma lists.

The table is a snapshot from Figma's help article as of November 7, 2026. Seats change, so check the article or ask your admin before you assume a Run button will appear. Figma's pricing page does not list a plugin row for each plan, so the help article is the better source for this question.

Add a community plugin from the Tools tab

The steps on this page follow Figma's current help article. Each one matches a label you should see on screen. Read them once before you start, then keep the list open while you work.

Here is a worked example. Say you want a contrast checker for a landing page file. You open the file in the Mac app, click Tools, filter to Plugin, find the contrast checker by name, open its details modal, and click Run. Run it on a copy of the file first, so a bad change does not reach the original.

Why older guides show a Save step

You will find two versions of the install steps online. The first is Figma's help article, which describes the Tools tab, the Plugin filter, and Run. The second is a Hypermatic tutorial dated August 3, 2024, which describes an Actions button in the bottom toolbar, a Plugins and widgets tab, and a Save button.

The Hypermatic tutorial says Save adds the plugin to your saved list. It also says the bookmark icon on a plugin's community page does the same, and that a second click shows Remove from saves. Figma's current help article does not confirm that step, so treat Save as a fallback, not a rule.

Labels also change between versions. The older guide's Actions label may not match what your build shows. If your menu says Tools, follow the Tools route first. If you see Save, use it, then look for the saved plugin under the right-click Plugins menu.

Run a plugin again with a keyboard shortcut

Command Option P is the fastest way to repeat a plugin. Figma's help article lists it as Run last plugin on Mac, and it also appears as a quick action. On Windows the same action uses Alt Control P, which helps if your team works on mixed machines.

The shortcut runs the last plugin you ran. It does not open a picker. If you want a different plugin, go back to Tools, filter to Plugin, and click Run again. Mixing up the two can make a plugin look like it disappeared.

Fix a plugin that will not run on Mac

Work through the causes in a set order. Start with the cheap checks: seat, edit access, and admin approval. Then check the network. Reset the app last, because a reset touches more than a single plugin.

The Reset Figma and Restart item comes from a third-party guide, so treat it as a suggestion. One guide also suggests quitting Figma and removing ~/Library/Application Support/Figma in Terminal. That deletes local app data. Back up anything you need first, or skip that step and ask your admin for help.

Admin approval on team and government accounts

Organization admins can limit plugins. Figma's help article says they can restrict use to approved classic plugins. The Figma for Government edition only offers plugins approved by the organization's admins. If you cannot run a plugin on a team account, the block is probably an admin setting, not a fault in the plugin.

Send your admin the plugin name and the exact message on your screen. They can tell you whether to request approval or pick an approved alternative. That is faster than retrying the same click.

Build your own plugin with Plugins > Development

Adding a community plugin and building your own are different jobs. Building needs the desktop app, because Figma's developer quickstart says plugin development and testing requires it. Figma also reads the plugin code from a local file. Skip this section if you only want to use a plugin.

1. Open Plugins > Development in the menu bar and select New plugin.
2. In the Create a plugin modal, choose Figma design and enter a name.
3. Select Custom UI, then click Save as.
4. To run it, open the design file, go to Plugins > Development, select the plugin name, and click Create.

The quickstart gives one shortcut, ⌘⇧B, which starts the TypeScript watch build. It does not install or run a plugin. Use it while you edit your code, and keep the desktop app open while you test.

Desktop app or browser for running plugins

Figma's plugin help article does not describe any difference between the desktop app and the browser when you run a plugin. The desktop-only item in the sources is plugin development. That is the main reason this guide assumes the Mac app.

On May 1, 2026, Figma's release notes said links open directly in the macOS desktop app, skipping the browser step. You can also search open and recently closed tabs from the tab overflow menu. If a Figma link opens straight in the app, that change is working as described.

Keep the Mac app current

An old app can cause plugin problems. The current Mac desktop build in Figma's version file is 126.11.8, checked on November 7, 2026. If your app is far behind that number, update it before you chase other causes.

Figma's deploy help says desktop app versions are supported for only up to two months. That matters most on a managed Mac where updates are blocked. Ask IT to deploy new builds on time, or the app falls outside its support window.

Mistakes people make with Figma plugins

• Looking for community plugins under the menu bar Plugins item. They live in the Tools tab of the file.
• Using a view link and expecting Run to work. Plugins need edit access.
• Pressing ⌘⌥P and expecting a picker. The shortcut runs the last plugin only.
• Following a Save step from a 2024 tutorial without checking your build first.
• Deleting the Figma application support folder before trying the simpler fixes.

What to do next

Once a plugin runs, test it on a copy of your file before you use it on client work. Note the plugin name and the seat you used, so a teammate can repeat the steps. If you want more keys at hand, read how to show keyboard shortcuts in Figma on Mac.

If your next task is building components, how to create a component in Figma on Mac covers the steps. For exporting a finished frame, see how to export a frame as PNG in Figma on Mac.