Figma Plugin Launch Checklist

Updated 26 September 2026 · Checked against Figma’s own docs the same day · For plugin makers

Tick the boxes as you go. Figma’s rules change, so we link to its own pages, and every item here was checked against them on 26 September 2026. We run The Design Tools and Launch Week, which appear in the launch section.

1. The plugin itself

• Your manifest includes "documentAccess": "dynamic-page". Figma requires this field, with this value, for all new plugins.
• editorType lists only the editors you really support: figma (Figma Design), figjam, dev (Dev Mode), slides or buzz. The combination of figjam and dev isn’t supported.
• networkAccess.allowedDomains lists every domain the plugin calls, or ["none"] if it calls nothing. If you allow "*" or a local server, add the reasoning field Figma asks for.
• It’s finished and works as described, with no placeholder content, crashes or obvious bugs.
• It stays responsive on a large file, and slow operations show progress. Figma rejects plugins that hurt its performance.
• An empty selection or an error gets a plain-language message, not a silent failure.
• It only reads or changes a file when the user asks it to.
• It uses only Figma’s official APIs.
• If it needs the internet, it tells people when it can’t work offline.
• Its interface follows Figma’s own look where it can.

2. The rules that get plugins rejected

• No ads in the plugin’s interface or in files it creates.
• No general-purpose AI chat inside Figma, and no MCP server exposed through the plugin.
• It doesn’t recreate core Figma features or work around Figma’s paid features.
• It isn’t a copy of another plugin you’ve already published.
• Every third-party service it uses is named in the description.
• If it processes user data, it has a privacy policy.
• Its name and branding follow Figma’s trademark guidelines, so nobody could think Figma made it.

Figma’s full list is in its plugin and widget review guidelines.

3. The Community listing

• You’re publishing from the Figma desktop app on macOS or Windows.
• Two-factor authentication is switched on for your Figma account.
• Icon: 128 × 128 px.
• Thumbnail: 1920 × 1080 px.
• Up to nine more images or videos for the carousel, showing the plugin in real use.
• A name, a short tagline, a description and a category.
• The description’s first line says what the plugin does. Setup and usage steps come after it, because Figma expects documentation.
• A support contact that someone actually reads.
• The network access label matches your manifest: unknown, unrestricted, restricted or no network access.
• Optional: a playground file so people can try the plugin on a sample before using it on their own work.
• The security disclosure form, which Figma’s guidelines encourage. Its review can take up to two weeks, and approved answers are shown to logged-in Community users.

Figma’s step-by-step guide: publish plugins to the Figma Community.

4. Review

• After you submit, the plugin appears under Published with an “In review” badge.
• You’ve planned for an open-ended wait. Figma gives no fixed timeline: approval times depend on volume and the team’s availability, and the decision arrives by email to your Figma account.
• If you fix something during review, you can publish the update without resubmitting.
• You know that material updates later on are reviewed again.
• Your public launch date is set only after approval.

5. If you plan to charge

• You have an activated Stripe account connected to your Community profile, and you meet Figma’s current seller requirements. Figma has changed these before, so check its help pages.
• Your price is at least $2, in whole dollars.
• You’re ready for a 7-day free trial, which is the default.
• For a monthly subscription, you know the price can rise by at most 50% every 30 days.
• If you offer a yearly discount, it’s between 1% and 95%.
• You’ve decided for good: a plugin published as paid can’t be made free later.

6. Launch it outside Figma

• The plugin is submitted to The Design Tools. It’s free, a person reviews it within 7 days, and you get a permanent review page you can claim and reply to.
• A Launch Week is booked for the week after approval, so the plugin spends Monday to Sunday on a board designers vote on.
• The story of why you built it is sent to Sidebar, which shares five design links every weekday.
• It’s suggested to Toools.design (free) and, if you have a small budget, listed on usetools.design (from €9.99).
• It’s shared in design communities that allow people to post their own work, after reading each one’s rules.
• It’s on Product Hunt if you have an audience to bring on one day. Ask people to visit and comment, not to upvote.
• Each link carries its own ?ref= tag, so you can see which places send installs.

Where each of these fits, and what it costs, is in Product Hunt alternatives for design tools and how to launch a design tool.

7. After launch

• You reply to comments on your Community page within a day.
• You check your plugin’s numbers in the Metrics tab of your Community profile.
• You ship a visible update in the first few weeks and say what changed.
• If the plugin has a website, it shows your “Reviewed on” badge.
• You bring the next big update back to Launch Week. Each tool can launch there once every 90 days.

Frequently asked questions

How long does Figma plugin review take?

Figma doesn’t publish a fixed time. Approval depends on how many plugins are waiting and on the review team’s availability, and makers on Figma’s forum have reported waits of a week or more. Submit well before the date you want to launch.

Is documentAccess dynamic-page required?

Yes. Figma requires the documentAccess field for every new plugin, and its value must be dynamic-page.

What size should a Figma plugin icon and thumbnail be?

Figma recommends a 128 × 128 px icon and a 1920 × 1080 px thumbnail. You can add up to nine more images or videos to the carousel.

Do I need two-factor authentication to publish a Figma plugin?

Yes. Figma asks you to turn on two-factor authentication before you publish, and publishing is done from the desktop app.

Can I sell a Figma plugin?

Yes, if you meet Figma’s seller requirements and connect an activated Stripe account. The minimum price is 2 dollars in whole dollars, there’s a 7-day free trial by default, and a plugin published as paid can’t be made free later.

Can a Figma plugin show ads?

No. Figma’s review guidelines don’t allow advertisements in a plugin’s interface or in the files it creates.

Where should I promote a Figma plugin after publishing?

Outside Figma: a design-only directory such as The Design Tools with its weekly Launch Week, design link sites like Sidebar, design directories such as Toools.design, communities that allow sharing your own work, and Product Hunt if you have an audience to bring on one day.