Figma Community Listing Requirements for Plugins, Files and Apps
Publishing to the Figma Community means filling a name, tagline, description and category, then adding images. Figma recommends a 128 x 128 pixel icon and a 1920 x 1080 pixel thumbnail for plugins, and 1920 x 1080 images for files, with up to nine more images in a carousel. Plugins and apps are reviewed before they are listed. This was read from Figma’s help pages on 13 November 2026; confirm in the publish dialog.
Does Figma treat plugins, files and apps the same way?
No, and the first decision is which kind of listing you are making. Figma’s Help Center has a separate article for each: Publish classic plugins, Publish files and Publish apps. The same pages say that widgets and slide deck templates have their own publishing steps. We read the first three on 13 November 2026 and did not read the widget or slide-deck articles, so this page says nothing about them.
| Item | Classic plugin | File | OAuth app |
|---|---|---|---|
| Text fields | Name, short tagline, description, category | Name, description, category, up to 5 tags (custom tags up to 25 characters) | Logo, tagline of 100 characters or fewer, description, landing page URL, support contact, plus testing instructions for the reviewer |
| Main image | Icon, recommended 128 x 128 px; thumbnail image or video, recommended 1920 x 1080 px | Thumbnail, recommended 1920 x 1080 px | Cover image, recommended 1920 x 1080 px |
| Extra images | Up to 9 images and videos in a carousel; optional playground file | Up to 9 more images | Up to 9 images in a carousel |
| Review | Reviewed before listing; shows an In review badge, then Published | Paid files are reviewed by Figma’s content team | Figma reviews the listing and tests the app, using your testing instructions |
| Where to publish from | Figma desktop app for macOS or Windows | The editor, not the file browser | figma.com/developers/apps |
What is the plugin publishing flow?
Before you can publish or update a plugin, the plugin article lists three prerequisites: the Figma desktop app, a plugin created for development, and two-factor authentication on your account. You then go to Plugins, Manage plugins, choose Publish, and work through a modal with pages for describing the resource, choosing images, an optional data security disclosure and final details.
- Describe your resource: name, tagline, description and a category such as Design tools or Software development.
- Choose some images: the icon, the thumbnail, an optional playground file where people can try the plugin, and up to nine carousel items.
- Data security (optional): a questionnaire about how the plugin handles data. Figma reviews the answers, says the review can take up to two weeks, and then shows them to signed-in users on the listing.
- Final details: who publishes it (yourself, a team or an organization on eligible plans) and a read-out of the plugin’s network access, which is shown to users as a label.
Figma says it does not review plugins you share privately inside an organization, and that approval times vary with volume. While a plugin is in review you can still push updates. If it is rejected, you can fix the feedback and submit again.
What changes if you plan to charge?
Paid plugins require you to be an approved Community creator and to activate a Stripe account before publishing. The article lists decisions you cannot undo: the creator who first publishes becomes the designated payee for good; the choice between one-time payments and a monthly subscription is fixed after publishing; and a plugin published as paid cannot later be converted to free. Paid plugins cannot be unpublished, though they can be delisted. Subscriptions come with a seven-day free trial by default, and you may set a yearly discount between 1 and 95 percent.
For a first release, those rules point one way: publish a free version first if there is any doubt about pricing, and treat the paid decision as permanent. The Figma plugin launch playbook works through a free launch in order, and the Figma plugin places guide lists where else designers look.
How should you make the 1920 x 1080 images?
Figma’s file article says its Community file cover frame preset creates a frame of the right size, so start from that instead of typing dimensions. The article also notes a trade-off: if the thumbnail includes a prototype preview, you cannot upload additional carousel images. That makes the thumbnail decision a real choice. A prototype preview lets people click through; a still thumbnail leaves room for nine more images explaining use cases.
The figures are labelled “recommended”, not mandatory, so do not read them as a rejection rule. They are what Figma’s own interface suggests. Design the thumbnail so that the name of the resource and one visible result are readable when the image is small. A plugin thumbnail that is a blank panel tells a designer nothing; one that shows a before-and-after on a real frame does.
What do you do once the listing is live?
Every listing gets a unique Community URL, found in the Share section, and that is the link to use everywhere else. Put it on your own page first, then launch your product free here with the Figma URL as the main link so that visitors who like it can install it in one click. Tag each outbound link so you can see which place sent installs; the UTM tagging guide for launches has a naming scheme. Design-tool authors may also want the design tool ideas on the board for inspiration, and the Product Hunt alternatives for design tools page lists boards that fit.
Keep the exported images with the project. If you later add a file listing for a UI kit, the same 1920 x 1080 frame can be reused, and the logo and icon specs page shows what other platforms want for the icon.
Frequently asked questions
What size should a Figma plugin icon be?
Figma’s plugin publishing article recommends an icon of 128 x 128 pixels and a thumbnail image or video of 1920 x 1080 pixels. Both are described as recommended sizes in the publish dialog, so check the dialog when you upload.
How many images can a Figma Community file have?
A file listing takes one thumbnail plus up to nine other images, which form a carousel on the Community page. Figma recommends 1920 x 1080 pixels for them. If the thumbnail includes a prototype preview, you cannot add any carousel images.
Does Figma review plugins before they are listed?
Yes. A plugin submitted to the Community goes through Figma’s review process before it is listed, and shows an In review badge until a decision arrives by email. Plugins shared privately inside an organization are not reviewed. Approval times vary with the team’s workload.
Can I turn a paid Figma plugin into a free one later?
No. Figma’s article says a plugin published as paid cannot be converted to free later, and the one-time versus monthly payment choice cannot be changed after publishing either. If you are unsure about pricing, publish a free version first and decide on pricing separately.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.