Plugin Review Guidelines

This is an evolving document, so its contents may change over time. If you have any questions or concerns around our review guidelines, please reach out to

Figma is incredibly excited to be introducing plugins to our community!

Developers, like you, help our community to discover new ways to design and explore Figma. We can't wait to see what you've created.

Before a plugin can be listed in the Figma plugin directory, it needs to go through our review process.

To make the submission process as smooth and seamless as possible, we have created a set of guidelines. These outline what is required to make it through the approval process.

Before You Submit

When you are ready to submit, please make sure you have done the following:

  • Tested your app extensively for crashes and bugs.
  • Ensured your plugin description and image(s) are complete and accurate. Profanity in the name or description of your plugin is not accepted.
  • Established a way for users to contact you for support. It's your responsibility to provide support for your plugin's users. You can provide them with an email address, or a link to a website or help center.

What to Expect

Our goal is to reach a decision ASAP, ideally within 3-7 business days. We will contact you via your Figma account email to notify you of our decision.

If your plugin has been rejected, we'll send you an email to clarify and provide a brief explanation. You may submit your plugin again for review, after addressing any feedback.

Any attempts to exploit the Plugins API (provide false information, plagiarism, deceitful manipulation of user files, or theft of data) will result in immediate removal. You will also be banned from publishing future plugins to the community.

Review Guidelines

  1. Safety
  2. Business
  3. Usability
  4. Legal

1. Safety

We want our users to feel confident that installing Figma plugins is safe and non-offensive.

We will not allow any plugins that are aimed to be malicious or damaging to our users or their work.

  1. Objectionable Content
    1. Content that is offensive, insensitive, upsetting, or intended to disgust is not permitted.
  2. Official API Usage
    1. Plugins can only leverage official plugin APIs and cannot require users to install separate packages that manipulate Figma on the Web or the Desktop App.
  3. Developer Contact Information
    1. Authors must be individuals on a Figma plan (Starter, Pro, Organization) or companies on the Figma Organization plan. Attempts to artificially represent a plugin author as a company may result in your plugin being rejected
    2. Please ensure that your contact information is reliable for users in the event they have any questions, support issues, or feedback.

2. Business

Our hope is that Figma plugins are made available and accessible to the entire Figma community, regardless of their ability to pay for services.

While we do not offer functionality that supports payments through Figma, we do allow for developers to use a third party to facilitate monetizing your plugin.

  1. Monetization Policy
    1. We allow plugins to direct users to a third party to allow for monetization. We reserve the right to reject plugins that attempt to monetize in poor taste.
  2. Advertising Policy
    1. Plugins may not display ads to Figma users. Please do not insert advertisements into design files or present ads in the plugin UI.

3. Usability

We want all of the plugins available to our community to be useful and valuable. If your plugin is trivial or intended to be creepy or uncomfortable, we may not approve it.

  1. Plugin Completeness
    1. Please make sure your plugin is completed, functions as intended, and does not include temporary content. We will reject plugins that crash or have obvious bugs.
    2. Please do not use developer error messages to communicate with end users.
  2. Complete and Accurate Metadata
    1. It should be clear to users that the plugin they are installing does what they expected it to do. Please include an accurate description, screenshot, or previews so that the users will not be surprised by any hidden functionality.
  3. Design
    1. We highly recommend matching your plugin to Figma's UI so we can create a seamless experience for our users.
    2. If there are any concerns with usability, or any other negative externalities, we may reject the plugin.
  4. Performance
    1. If your plugin negatively impacts the overall performance or experience within Figma, we may reject it. An example of this would be a long-running background process.
    2. Your plugin should deliver the appropriate notifications if the user is offline and your plugin cannot perform offline.
    3. Plugins that stop working or offer a low quality experience may be removed at any time.

Plugins are expected to comply with the law. It is ultimately your responsibility to make sure that your plugin is not doing anything illegal. You should consult with a lawyer if you are unsure about something.

Please do not rely on these guidelines to make sure you are in compliance with the law.

  1. Intellectual Property
    1. Ensure that your plugins only use content that you created or have a license to use. Your plugin may be removed if you use content without permission.
  2. Gaming, Gambling, Lotteries
    1. No gambling or sweepstake-related usage is permitted.

If you have any questions or concerns around our review guidelines, please reach out to

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.