Related Videos

• Community publishing permissions

  Community profiles showcase files and plugins creators have shared with to the Figma Community.

  Figma supports Community profiles for creators, teams and organizations. Whether you can publish to a personal, team, or organization profile depends on your role or permissions.

  Publish files

  Publish any file you have can edit access to, including files in your drafts, teams, and any shared projects.

  Anyone with edit access can also publish updates to the file. This includes updating the tags or description, and adding or removing creators.

  Only team admins can publish to a team's profile, and only organization admins can publish to an organization's profile.

  If you are a team or organization admin, you may be able to publish to more than one profile. You can select which profiles when you publish the file. Figma determines what profiles you can publish to based on the file's location and your role or permissions. Show me the permissions table ↓

  Publish a Community file →

  Personal profile

  Who can publish to a personal profile?

  Anyone with a Figma account can create a personal profile. You can create one profile per Figma account (email address).

  Anyone with can edit access to the file can publish that file to the Community.

  If you have both personal and work Figma accounts, you can add connected profiles and publish to one profile across accounts.

  Organization members

  Organization admins are the only ones who can publish files and plugins from the organization space. You can only publish files in the organization workspace to an organization profile.

  If you are part of an organization, any files or plugins you create in the organization workspace belong to the organization. You can only publish files from the external teams workspace.

  You can connect your Community profile to your organization account to publish files and plugins from the external teams space to your profile.

  Organization admins can choose to recognize an individual contributions by adding members to the file as a creator.

  Should you leave, or be removed from the organization, you can disconnect your work account from your profile.

  The organization can choose to add you as an editor to any specific Community files you contributed to. This allows you to be listed as a creator of that resource under your personal Community profile.

  Team profiles

  Who can publish to a team profile?

  Only team owners and admins can publish files and plugins to a team profile.

  Files have to be in that team's workspace to publish to the team's profile. If it is in your drafts or another team, you will need to move it to the correct team to publish it.

  As part of the publishing process, team admins can add other contributors as creators. Creators need to be directly invited to the file with can view or can edit access. Learn more about being listed as a creator ↓

  Note: Once the file is published to the Community, you won't be able to move it to another team. You can still move it between projects on the same team.

  Organization profiles

  Who can publish to an Organization profile?

  Only organization admins can publish files or plugins to an organization profile. 

  If you're an organization admin, you can publish files and plugins to the organization's Community profile. To publish a file to the organization's profile, the file must:

  • Be in the organization space (not a member's drafts or external teams workspace)
  • Not be in a secret team
  • Not be moved between teams once published

  Organization admins can add other contributors as creators when publishing. Creators need to be directly invited to the file with can view or can edit access. Learn more about being listed as a creator ↓

  Note:There isn't currently a way to move files between the organization workspace and the external workspace.

  If you want to publish a file to the organization's profile, you will need to export the file from the external team workspace. You can then import this as a new file in the organization workspace. This won't include any comments or version history from the original file. Learn how to export .fig files →

  Publish files or plugins

  Publish any Figma plugins you've developed or files you want to share. Figma uses your role or permissions to determine which profiles you can publish files to. Use the tables below to see which profiles you can publish to based on the file's location.

  Note: You only only publish a file if you have can edit access to the file. You can still be listed as a creator if you have been invited to the original file with either can view or can edit access.

  Drafts

  File permission	Personal profile
  Can edit	✓
  Can view	✕

  Professional, Education, or Starter teams

  Team permission	Team profile	Personal profile
  Admin	✓	✓
  Can edit	✕	✓
  Can view	✕	✕

  Organization

  Note: It's not possible to publish to a personal profile within the organization space. We recommend you switch to your personal space or publish from a personal Figma account.

  Organization workspace

  Account	Role	Team permission	Organization profile	Team profile	Personal profile
  Admin	Editor	Admin	✓	✓	✕
  Admin	Editor	Can edit	✓	✕	✕
  Admin	Viewer	Can view	✕	✕	✕
  Admin	Viewer-restricted	Can view	✕	✕	✕
  Member	Editor	Admin	✕	✓	✕
  Member	Editor	Can edit	✕	✕	✕
  Member	Viewer	Can view	✕	✕	✕
  Member	Viewer-restricted	Can view	✕	✕	✕

  External teams workspace

  Team permission	Organization profile	Team profile	Personal profile
  Team Admin	✕	✓	✓
  Editor	✕	✕	✓

  Creator contributions

  If you've contributed to other files in the Community, and have a role on that file, you can also be added to the file as a creator.

  Publishers can add any others contributors to the file as creators as part of the publishing process. Creators need to have explicit can view or can edit permissions on the file itself.

  Every who is added as a creator will have the option to accept or decline the request. Figma will send you a notification in your account.

  Figma will display accepted creators on the file's Community page, as well as include the file on each individual creator's profile.

  If you have published to a team or organization profile, Figma will show the team or organization first, then any individual creators.

  Note: If you only have access to the file based on your team permissions, you won't be included in the list of potential creators. If someone is missing from the list of creators, you will need to invite them to the file itself.

  Organization role	Team permissions	File permission	Creator supported
  Editor	Can edit	-	✕
  Editor	Can edit	Can edit	✓
  Editor	Can view	-	✕
  Editor	Can view	Can view	✓
  Viewer	Can view	-	✕
  Viewer	Can view	Can view	✓
  Viewer restricted	Can view	-	✕
  Viewer restricted	Can view	Can view	✕

• Publish Community files

  Who can use this feature?

  Supported on any team or plan.

  Applies to both Figma design and FigJam files.

  You must have can edit access to the file to publish the file to the Community.

  Which profile(s) you can publish to depends on your permissions within a team or organization. Learn who can publish files and plugins →

  Community files are design files creators have shared with the Community. Create templates for wireframe, UI kits, asset libraries, and designs systems. Or share educational resources, interactive tutorials, and tools to use across the design process.

  Anyone with can edit access to the file can publish it. This includes when the file is originally published, as well as any subsequent publishes.

  When you publish a file, Figma will add a snapshot of that file to the Community. Anyone who duplicates the file gets a new copy, without any updates, version history or comments from the original file.

  You can continue to make changes to the file once it's published, then publish any updates to your Community file. Designers and other creators can duplicate the updated version to get access to those changes,

  Copyright, licensing, and attribution

  Any files you share in the Community will have an attribution 4.0 International (CC BY 4.0) license. This means other members are free to share and adapt these files, but they must give credit to the original creator. Learn more about copyright and licensing →

  Remixes

  Remixes are files in the Community that originated from another Community file. Other Community members can duplicate your files, make them their own, and share them again.

  Figma tracks remixes to provide easier attribution and a joyful experience. If people remix your file, Figma will add an attribution to the remix's file page that links to the original Community file.

  Figma will also add a Remixes section to your file's page. If there are more than three remixes for a file, Figma will add a dedicated remix tab to your file page. Click See All to view all remixes.

  Publish files

  Caution: If you're in an organization, you won't be able to publish files from the organization workspace to an individual profile. If the file is in the organization workspace, we recommend you export it, re-import it to your external workspace, then publish it from there.

  You can publish both FigJam files and Figma design files. You can only publish files when you have them open in the Editor, not from the file browser.

  Anyone with can edit access to the file can publish the file and any updates. This includes collaborators with edit access to the team or project.

  1. Click the Share button in the toolbar.
  2. Select the Publish to Community tab at the top of the modal.
  3. Click Publish to open the publishing modal.

  Every file will have its own page in the Figma Community. This allows other members of the Community to browse, search, and find your file.

  You'll need to provide some information about your file, which Figma will display on the file page:

  File information

  • Choose a name for your file. Users can search for your file using this name, or via relevant keywords (tags). You can give the file a different name than the original file.

  • Write a description for your file. Use this space to give directions for how to use the file, or credit other contributors. You can format your description using some basic text formatting:

    • Bold
    • Italic
    • Strikethrough
    • Header 1
    • Header 2
    • Bulleted list
    • Numbered list
    • Add hyperlink
    • Inline code
    • Code block
  • Add up to 12 keywords or tags to classify your file. Figma supports alphanumeric characters (a-z and 1-9), but no special characters or punctuation. Tags can be up to 25 characters.

  

  Preview

  Choose to preview your file as a file or a prototype. Members can still access the entire file, including any prototypes, when they duplicate it.

  1. Choose to Preview as:
     • File: Members can view, pan, and zoom around your file. Members can preview other pages in your file using the page selector.
     • Prototype: Members can click on hotspots to interact with the prototype, use the arrows to navigate between screens, or restart the prototype.
  2. Set the scale of the preview, choose from Fit, Fill, or 100%. Learn more about scale →

  If you select file, Figma will use the file thumbnail as the preview for your file. The recommended dimensions are 1920 x 960, with a safe area of 1600 x 960. Community frame presets →

  Creators

  Figma allows you to choose who is listed as a file's creator(s). This is a great way to recognize other contributions to the file. To qualify as a creator they will need to meet both the following criteria:

  • An explicit can view or can edit role on the original file
  • An existing Community profile

  When you add someone to a Community file as a creator, Figma will send them a notification which they can accept or decline.

  Every contributor that accepts the request is listed as a creator on the file. Figma will also display that file on the Community profile of any creators. Use the Creator field to add any contributors.

  If you're an admin of a team or organization, you will have two fields available for Creators. The first field allows you to select the team or organization profile you want to publish to.

  The second field allows you to find and select individual contributors. Type a person's name or profile handle to search for their profile, and click to select.

  

  To add an individual as a creator, they will need to have an explicit can view or can edit role on the file, as well as a Figma Community profile. Who can publish files and plugins →

  Publish settings

  Choose whether fellow Figma Community members can comment on your files and plugins. Comments in the Community are turned on by default, but you can turn off community comments at any time.

  1. Check or uncheck Allow comments from Community members.
  2. If commenting is on, you can click More options and check or uncheck Let people pin comments to specific spots in my design to allow pinned comments.
  3. Check the box to agree to the licensing terms and click Publish to confirm.

  Figma will send everyone you listed as a creator a notification. This gives them the option to accept or decline the request. Every creator that accepts the request will be listed on the resource page. 

  Publish file updates

  Anyone with edit access to the file can continue to make changes to the original file. They will need to publish those changes to the Community to see them reflected in the Community file.

  Figma will treat this as a new version of the file and won't update any existing duplicates of the file. Community members will need to duplicate the updated version to access those changes.

  Figma will maintain your file statistics likes and duplicates, across file versions.

  Publish an update

  Publish updates the same way you originally published the file. This includes changes to the file's details, like description, tags, and any creators.

  1. Open the file in the editor.
  2. Click the Share button in the toolbar.
  3. Select the Publish to Community tab at the top of the modal.
  4. Click Publish update to open the publishing modal.
  5. Add or update the title, description, tags, and publish as settings (optional).
  6. To remove a creator, click the next to their name. To add a creator, type a person's name or profile handle to search for their profile, and click to select.
  7. Check the box to agree to the licensing terms and click Publish to confirm.

  Remove or unpublish Community files →
• Make plugins for the Figma Community

  Before you start

  Who can use this feature

  Users on any plan can develop plugins for the Figma Community.

  You can only register and publish plugins from the Figma Desktop App to develop plugins. The Desktop App is only available for macOS and Windows.

  Plugins are third-party scripts or applications that extend the functionality of another app.

  You can use plugins in the Editor to customize your experience, or create more efficient workflows.

  Plugins interact with Figma via a dedicated Plugin API.

  We built the Plugin API 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 can perform one or more "User Actions". User Actions 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.
  • Only one plugin can be active at a time. Plugins that run in the background - or respond to changes in a File - aren't currently supported.

  Make plugins for Figma

  This article outlines the plugin development process in Figma. We designed this as a supplementary resource to our developer documentation.

  1. Register a Plugin with Figma
  2. Build and test your Plugin (Visit the Figma Plugin Developer site)
  3. Publish a Plugin to the Figma Community
  4. Manage plugins as a developer

  Check out our Figma Plugin Developer site for a complete guide on making plugins for Figma

  You must have the Figma Desktop app installed to make plugins. We recommend building plugins using TypeScript in Visual Studio Code. If you're not familiar with TypeScript, you can still build a plugin with Javascript.

  Figma Plugin Examples

  Here's some examples of existing Figma plugins:

  • Content Buddy: allows you to find text within your designs and replace it with the actual copy.
  • Themer: allows you to swap between published styles from your libraries, in bulk.
  • Content Reel: helps you to bring data into your designs. Including text strings, avatars and icons.
  • Map Maker: allows you to insert customized maps into any shape layer.
  • Figmotion: allows you to animate objects within a Frame, without having to leave Figma.
  • Stark: checks the contrast of a selected layer against WCAG 2.1 guidelines.

  

  Buy and sell plugins

  While we don't provide the ability to directly buy and sell plugins through Community, you can sell licenses to plugins you've built by following these steps:

  1. The buyer and seller should reach out to the Support team at support@figma.com to facilitate the sale. For example, the seller emails Support with the buyer cc'd or vice versa. 
  2. The original owner must confirm that they are authorizing the sale. 
  3. The buyer of the plugin confirms they will abide by our Terms of Service after the sale.

  Once this process is complete, the Support team will transfer the plugin between the appropriate 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 →

• Register a plugin for development

  Before you start

  Who can use this feature

  Supported on any team or plan

  You must use the Figma desktop app to register and publish plugins. The Figma desktop app is only available for Mac and Windows. Download the Figma desktop app →

  This article covers one step in the plugin development process. Learn how to make plugins for Figma →

  Find all the information you need to get started writing plugins on the Figma plugin developers page.

  You will need to register a plugin before you can start developing it. You must use the Figma desktop app to develop a plugin.

  Plugin templates

  When you register a plugin, Figma will create a new plugin manifest on your computer. This includes the folders, templates, and information you'll need to build your plugin.

  You can choose a plugin template when you register your plugin for development.

  • Empty: A blank slate where you can build your plugin from the ground up.
  • Run once: This is a template for a plugin that runs on the canvas, without any further interaction from the user. Use this template if you don't need to build any UI.
  • With UI's and Browser API's: Use this template if you want to create a plugin with an interactive UI. Or, if you want to use browser APIs as part of your plugin.

  

  Register a plugin

  1. Open the Figma desktop app
  2. Open the account menu in the top-right corner.
  3. Select Plugins to open your plugin page.
  4. Under In Development, click <span id="plus-icon" class="ui-icon" aria-label="Plus addition symbol icon."></span> Create your own plugin.
  5. Enter a name for your plugin, you can always change your plugin name when you go to publish it.

     Want to upload an existing Figma plugin? Select the Link existing plugin option to link your manifest to the new plugin.

  6. Click Continue to go to the next step.
  7. Choose a plugin template: Empty, Run once, with Ui and browser APIs.
  8. Click Save as to create a new manifest.
  9. Figma will prompt you to choose a name and a location on your computer to save the manifest to. Enter a name and location, then click Save to confirm the download.
  10. Figma will also provide download links for any related tools.
      • Download Node.js to use Javascript
      • Copy the install code to run in the terminal for TypeScript
  11. Click Okay to close the modal and return to the plugin page. You'll see your new plugin listed in the Development column.

  

  Want to open your manifest from Figma? Click on the plugin and select Reveal in Finder.

• Publish plugins to the Figma Community

  Before you start

  Who can use this feature

  Supported on any team or plan.

  You must use the Figma desktop app on macOS or Windows to develop plugins. Download the Figma Desktop app →

  This article covers just one step in the plugin development process. Find everything you'll need to make plugins for Figma on the Figma Developers site →

  When you're ready to share your plugin you can submit your plugin to the Figma Community. This allows other Figma users to install and run your plugin(s).

  You'll need to do the following before you can publish a plugin:

  • Download the Figma Desktop app →
  • Register a plugin for development →
  • Enable two-factor authentication →

  Note: You need to have two-factor authentication enabled to publish plugins, including publishing updates to existing plugins. You won't need to use two-factor authentication if you sign in to Figma via SAML SSO or Google SSO.

  Before you publish

  Creators and contributors

  For security reasons, it's only possible for one developer to be involved in publishing a plugin to Figma. This includes any subsequent updates to the plugin.

  The publisher can choose to list any other creators as part of the publishing process. This is a great way to recognize any contributions to the plugin's development. To qualify as a creator, the contributor will need to have a Figma Community profile.

  Figma will send a notification to anyone added as a creator, which the creator must accept or decline the request. Accepted contributors will appear on the plugin's page and the plugin will appear on each creator's Community profile.

  Prepare plugin information

  Every plugin will have its own page in the Figma Community. This allows other members of the to find and install your plugin.

  You'll need to provide some information for your plugin page. We recommend getting this set up before you start the publishing process.

  • Choose a name for your plugin. This can be something descriptive or a little creative. Users can search for your plugin using this name, but you also have tags to add relevant keywords.
  • Create an icon to represent your plugin in the Community. Figma will use this icon to identify your plugin in the Community and in the Editor. The recommended dimensions are 128 x 128.
  • Create some cover art for the top of your plugin page. The recommended dimensions are 1920 x 960 (safe area: 1600 x 960).
  • Write a description of your plugin. Use this field to explain what the plugin does, how to use it, and a sales pitch. If your plugin requires a subscription, we recommended mentioning this first. You can format your description using some basic text formatting.
  • Add up to 12 keywords or tags to classify your File. We support alphanumeric characters (a-z and 1-9), but no special characters or punctuation. Max 25 characters per tag.
  • As a plugin creator, it's your responsibility to provide support for your plugins. You'll need to provide an email address, website, or help center for your support contact.

  Monetization: You cannot display advertisements to users within design files, or as part of a plugin's UI. However, there are no restrictions around creating websites or profiles for your plugin.

  There isn't currently a way to monetize plugins in Figma Community itself. If you require a paid subscription, you can direct users to a third party site from your plugin description. Read the Figma Community Guidelines →

  

  Submit your plugin

  When you're ready to share your plugin with the Figma Community, you can submit it for review. You can only submit plugins from the Figma desktop app.

  Warning! Any attempts to exploit the Figma Plugins API will result in immediate removal. This will also ban you from publishing plugins in the future.

  This includes but is not limited to: Providing false information, plagiarism, deceitful manipulation of user files, and theft of data.

  1. Open the file browser in the Figma desktop app.
  2. Click on your name in the top-left to open your account and select the Plugins tab to view the plugins you have In development.
  3. Click on the plugin you'd like to publish and select Publish from the options.
  4. Upload an Icon and Cover art.
  5. Update the plugin's Name if needed.
  6. Add a Description of the plugin to set your plugin apart. Figma supports the following formatting:
     • Bold
     • Italic
     • Strikethrough
     • Header 1
     • Header 2
     • Bulleted list
     • Numbered list
     • Add hyperlink
     • Inline code
     • Code block
  7. Add any tags and a support contact.
  8. Use the Creators field to add any other contributors to the plugin. They will need to have an existing Figma Community profile. Type a person's name or handle in the field to search for their profile, and click to select.
     
     

     Note: If you're an admin of a team or organization, you will have two fields available for Creators. The first field allows you to select the team or organization profile you want to publish to, the second to search for existing creators. Learn who can publish files and plugins →

  9. Choose where to publish the plugin using the Publish to setting [Figma Organizations only]
     • Select Organization to share the plugin privately within your organization.
     • Select Community to publish the plugin and share it with to the Figma Community.
  10. Choose whether fellow Figma Community members can comment on your files and plugins. Comments in the Community are turned on by default, but you can turn off community comments at any time.
  11. Click Review to submit your plugin for review.

  Plugin review process

  Before Figma lists a plugin in the Figma Community, it needs to go through our review process. Figma doesn't review any plugins you choose to share privately within an organization. Learn more about Figma's Plugin Review Guidelines →

  When you first submit a plugin for review, Figma will move the plugin to the Published section with an In review badge.

  Figma will contact you via your Figma account email to notify you of our decision, our goal is to reach a decision within 5-10 business days.

  Once approved, Figma will add a Published badge next to your plugin. If Figma rejects your plugin, you can address any feedback and submit again.

  Noticed a mistake? You can still push updates to your plugin during the review process. Learn how to manage plugins as a developer →

  Share your plugin

  Figma gives your published plugin its own listing in the Figma Community, this allows other Figma users to find and install your plugins.

  Every plugin has a unique URL which you can copy and share with others. Find the plugin URL in the Share section of your plugin listing. It should look something like this: https://www.figma.com/community/plugin/uniqueidentifier/name

  If you have more than one plugin, you may want to share your creator profile instead. Learn more about Community profiles →

• Remove or unpublish Community files

  Who can use this feature?

  Supported on any team or plan.

  Applies to both Figma design and FigJam files.

  You must have can edit access to the file to publish or unpublish files.

  Which profile(s) you can publish to depends on your permissions within a team or organization. Learn who can publish files and plugins →

  Remove or unpublish files to remove them from the Community.

  Unpublish a file

  Unpublish the file to remove the file listing from the Community. This will remove the file from your Community profile and the profiles of any other creators.

  Removing or unpublishing a file doesn't affect duplicates of the file. Anyone who duplicated the file before it was removed can continue to access and edit their copy of the file.

  You can remove a published file from the original file, or from the file page in the Community.

  Note: Only an organization admin can unpublish a file or plugin on an organization's profile. If you're not an organization admin, you can still choose to remove the file from your profile.

  • A

    Original file

    1. Open the file in the editor.
    2. Click the Share button in the toolbar.
    3. Select the Publish to Community tab at the top of the modal.
    4. Click the Unpublish button to remove the file from the Community, and any creator's profile(s).
  • B

    File listing

    1. Open the file page in the Figma Community.
    2. Click the Unpublish button at the bottom of the page.
    3. Click Unpublish in the dialog to confirm.

  Remove yourself as a creator

  If you're listed as a creator of a resource, but don't want to have it on your Community profile, you can remove yourself as a creator.

  This will remove you as a creator on the file listing and from your own profile, but won't remove the file from the Community.

  Anyone who has edit access to the file can add and remove creators.

  1. Open the file page in the Figma Community.
  2. Click the Remove yourself from creators button at the bottom of the page.
  3. Click Remove in the dialog to confirm.
• Plugin Review Guidelines

  Caution: 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 reviews@figma.com.

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

  Developers like you help our community 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 5-10 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.

  Warning: 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.

  Authors may not share their Figma account or password information with other users or otherwise license, sell, transfer, or assign plugins.

  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.

  4. Legal

  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.

  Note: If you have any questions or concerns around our review guidelines, please reach out to reviews@figma.com.