How to Launch a Figma Plugin for Free: Two Review Clocks and a Calendar
Launch a Figma plugin by planning around two reviews: Figma reviews a plugin before listing it in the Community, and reviews the data security disclosure you fill in at publishing, which its help page says may take up to two weeks. Turn on two-factor authentication, publish from the desktop app, test privately with designers first, and decide early whether the plugin is free, because a paid plugin cannot be converted back.
What does Figma review, and who is excused?
Figma’s help page on publishing plugins says a plugin has to go through its review process before it is listed in the Community. When you first submit, the plugin sits in your Published section with an “In review” badge, you hear by email, and an approved plugin gets a “Published” badge. A rejection is not final: you address the feedback and submit again. The page does not give a review time, only that approval times vary with current volume.
The page also says Figma does not review plugins you share privately inside an organization. That is a real route if your first users are a design team you already know. It is not a launch, since nobody outside the organization can find it, but it is the fastest honest way to find out whether the plugin works on other people’s files.
Why plan two weeks for the data security form?
Publishing includes a data security page: a set of questions about how your plugin handles data, which Figma reviews. The help page notes that review and approval may take up to two weeks, and that once approved your answers are shown to logged-in users who view the listing. Treat it as a clock that runs beside the plugin review, not before it.
The form is easy to answer honestly if you decided what your plugin does with files before writing code. If the plugin sends layer names to your server so a model can rename them, say that plainly. The network access label on the listing is read from your manifest: unknown, unrestricted, restricted to listed domains, or none. “Unknown” looks worse than the truth, so list the domains in the manifest and the label becomes specific.
Which images does the listing need?
| Asset | What the page says | What to put in it |
|---|---|---|
| Icon | Recommended 128 by 128 pixels | A mark that survives at small size beside other plugins |
| Thumbnail | Image or video, recommended 1920 by 1080 | The result of running the plugin, not its panel |
| Carousel | Optional, up to nine images and videos | Before and after, then one frame per major feature |
| Playground file | Optional file where people can try it | A messy file that shows the problem the plugin solves |
| Support contact | Required at the last step | An address you read |
The playground file is the cheapest conversion tool on the list. Designers decide quickly, and “open a file and press run” beats a paragraph. The full set of requirements is gathered in the Figma Community listing requirements reference, and the demo video script helps if your thumbnail is a clip.
What can you not undo if you charge?
Figma’s page is specific about paid plugins, and most of it is irreversible. You must be an approved creator to publish one, and after approval you activate a Stripe account. The creator who first publishes becomes the designated payee and that cannot change. You pick one-time payments or a subscription, and that cannot change either. A plugin published as paid cannot be converted to free later, and paid plugins can be delisted but not unpublished.
That is a reason to launch free first if you are unsure. A free plugin gives you installs and feedback while you work out what people would pay for; a paid one locks the structure in before you know. You can still run a paid tier through your own site and keep the Community plugin free.
What does a calendar look like with two clocks?
- Week 1: build the core job. Decide the network access story and write it in the manifest as you go.
- Week 2: share the plugin privately with an organization or a few trusted designers, and watch them use it without helping.
- End of week 2: open the publish dialog, upload the assets, and submit the plugin and the data security form together. Updates can still be pushed while review runs.
- Weeks 3 and 4: while Figma reviews, write the announcement, record the clip, and recruit three designers who will try the public version on day one.
- Launch day: when the badge changes to “Published”, post. Reply to every question within the day.
If review is faster than expected, nothing is lost. If it is slower, you spent the extra time on the announcement instead of waiting on an email.
Where do designers hear about a plugin?
The Community is the shop window, but a listing is a quiet place to arrive. Most first installs come from a link someone sent or a clip someone saw. Post the thumbnail clip in design communities where you already take part, and show the plugin on a real file instead of describing it. A short write-up of the problem and how you solved it is received better than a feature list.
For a page that sits outside Figma, launch your plugin free here: one verified email, no account, live when you press publish, with your own site’s link attached. Browse the design tool ideas first to see what builders are asking for, and read where to launch Figma plugins for other venues. A UI kit takes a different path, as the UI kit playbook explains, because a file is not reviewed like code.
What should you count?
Count runs, not just installs. A plugin installed once and never run is a bookmark. If your plugin has an interface with a result screen, add a link to a short feedback form there, and read the first fifteen answers before you decide what to build next. Compare each announcement with the day’s installs, as in the launch metrics checklist.
Frequently asked questions
Does Figma review every plugin?
Figma’s help page says a plugin goes through its review process before it is listed in the Community. It also says Figma does not review plugins you share privately within an organization. The page gives no fixed review time, only that approval times vary with volume.
How long does the data security review take?
The help page says review and approval of the security disclosure may take up to two weeks. Submit it together with the plugin, since both must clear before the listing is fully ready, and write your answers from what the plugin really does with user data.
What do I need before I can publish a Figma plugin?
According to the help page, you need the Figma desktop app, a plugin created for development, and two-factor authentication enabled, and you can only submit from the desktop app. Check which plans support publishing, since the page lists them, and prepare an icon and a thumbnail.
Can I make a paid Figma plugin free later?
No. Figma’s page says a plugin published as paid cannot be converted to free later, and paid plugins can be delisted but not unpublished. The payment type and the designated payee are also fixed after publishing. If you are unsure, launch free and sell through your own site.
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.