Can Figma plugins still make money now?

Why is making money from Figma plugins harder to judge now?

Figma plugins can still make money today, but the easy plugin opportunity has clearly become harder.

Two things are happening at the same time. Figma is much larger than it was during the early plugin years, with more paying customers, more large companies using the platform and more types of employees working inside it. Yet plugin creation has become dramatically easier too. Figma had already passed 10,000 plugins and widgets in its Community before its latest push into agent-generated plugins.

That second change is particularly important now. Figma's agent can build a custom plugin from a plain-English prompt, without requiring the user to understand the Plugin API. More recently, Figma also opened Community publishing for these generated plugins. Someone can now describe a tool, iterate on it with the agent and put it in front of other Figma users without going through the traditional development process.

Classic plugins still have two major advantages. They can be monetized, while generative plugins currently cannot, and they can call third-party APIs, which generative plugins currently cannot do. Those advantages leave plenty of room for commercial products.

Still, the bar has moved. A plugin that saves a designer a few clicks now competes with thousands of existing tools, Figma's own expanding feature set and, increasingly, a plugin the designer can ask Figma to create for them.

That is the real question now: which plugins merely work, and which ones solve a problem people will keep paying to solve?

Is Figma still growing enough for new plugins to make money?

Yes. Figma is currently growing more than fast enough to support new plugin businesses.

Figma's latest quarterly results showed $370.1 million of revenue, up 48% from the same quarter a year earlier. It was the company's third consecutive quarter of accelerating year-over-year growth.

The customer numbers are just as useful for plugin developers. Figma had 15,964 customers spending more than $10,000 a year by the end of that quarter, up 34% year over year. The number spending more than $100,000 reached 1,635, up 46%.

Earlier in the year, Figma also disclosed roughly 690,000 paying customers, up 54% in twelve months. That includes a huge long tail of individuals and small teams rather than only enterprise accounts.

And the audience is wider than the words "design tool" suggest. In its annual report, Figma said non-designers such as developers, product managers, researchers, marketers and writers represented roughly two-thirds of monthly active users during the final quarter of 2025.

So a plugin developer today can target far more than interface designers. Design systems, marketing production, developer workflows, accessibility, content operations, localization and product management all sit close enough to Figma to create potential businesses.

Lack of users is not what should stop someone from building a Figma plugin now. Finding a painful enough problem inside that audience is much harder.

Is the Figma plugin market already too crowded?

Yes, generic Figma plugins are crowded now, and the difference from the early market is enormous.

When Figma officially launched plugins in 2019, it said there were just over 40 public plugins after six weeks of beta. A developer could still find major holes in the product and be one of the first people to fill them.

By the time of Figma's IPO filing, builders had created more than 250,000 Community resources, including over 10,000 plugins and widgets.

That number understates the competitive change happening today because creating plugins has become easier again. Figma's latest generative-plugin system lets users create tools through prompting and publish them to Community. The supply of small utilities can now grow without every creator first learning JavaScript, setting up a development environment and studying the Plugin API.

The competition is especially heavy around obvious jobs. Icons, placeholder content, image manipulation, layer cleanup, renaming, spacing, exporting and simple automation have already attracted plenty of alternatives.

But saturation changes dramatically when the problem becomes specific. There may be thousands of Figma plugins, yet far fewer products that can manage a large company's design tokens across design and code, run a serious accessibility process, connect proprietary company data to Figma or automate a specialized production workflow.

So "the Figma plugin market" is too broad a category to be useful. Generic utilities are packed. Expensive professional problems remain much less crowded.

Can you actually charge people for a Figma plugin today?

Yes. Figma currently gives classic plugin creators a real native payment system, although it works much better for individual buyers than for larger teams.

A classic plugin can be sold as a one-time purchase or a subscription, with a minimum price of $2. Subscription plugins get a seven-day free trial by default, and developers can customize the trial through Figma's Payments API.

Figma handles payment processing, sales-tax collection, refunds, fraud monitoring and delivery. It takes a flat 15% of each Community sale. A $10 monthly subscription therefore leaves the developer with $8.50 before their own taxes, hosting, AI costs and other expenses.

That setup is perfectly usable for a designer buying a $5, $10 or $20 tool for themselves.

Team purchasing is still clumsy, though. According to Figma's current Community rules, an admin cannot buy a paid resource on behalf of team or organization members. Access belongs to the account that made the purchase.

That becomes a serious limitation once a plugin is meant for 20, 100 or 1,000 employees. Larger companies may also require administrators to approve third-party plugins before anyone can run them.

Figma does allow plugins to use external payment systems, which is why a developer can start with native checkout and later build a more traditional SaaS sales operation around the plugin.

For a small paid utility, Figma's 15% fee can be a reasonable price for getting checkout, tax handling and delivery out of the way. A serious team product will usually outgrow that purchasing model.

How many paying users does a Figma plugin need to make decent money?

A Figma plugin can reach meaningful side income with surprisingly few customers if people are willing to pay $10 to $20 a month.

With Figma's 15% fee, a $10 subscription leaves $8.50 per customer. About 118 subscribers would produce roughly $1,000 a month after Figma's cut. Around 589 would produce $5,000.

At $20 a month, those thresholds roughly halve. A developer would need around 59 customers for $1,000 a month and 295 for $5,000.

Those numbers exclude hosting, model inference, external APIs, support, tax and other expenses. An AI-heavy plugin can have much worse economics than a plugin that performs everything locally.

Still, the exercise shows why chasing enormous install counts can be a distraction. A narrow product used by a few hundred professionals can become a useful business. A free plugin with 100,000 users can make almost nothing.

Monthly price	Revenue per user after Figma's 15% fee	Users for ~$1k/month	Users for ~$5k/month	Users for ~$10k/month
$5	$4.25	236	1,177	2,353
$10	$8.50	118	589	1,177
$20	$17.00	59	295	589
$50	$42.50	24	118	236

Are there real businesses built around Figma plugins?

Yes. Some Figma plugins have clearly grown into real software businesses, but their evolution tells us more than their install counts do.

Tokens Studio is probably the cleanest example. The product started by solving design-token problems inside Figma and has since expanded into a much broader design-system platform.

Its pricing today runs from €17 a month, billed annually, for its Variables plan to €169 a month for Essential and €499 a month for its Organization plan. The higher plans include things such as versioned releases, branching, direct-to-code workflows, asset management, documentation and security support.

The Figma plugin is still important, but the company now sells infrastructure around the work happening inside Figma.

Stark shows the same progression in accessibility. Its current team pricing starts at $198 per user per year for premium tooling. Larger packages start at $2,500, $8,000 and $21,000 per year as Stark adds website monitoring, repositories, CI/CD, mobile apps, governance, SSO and compliance features.

Mokko is a newer and smaller example at the AI end of the market. Its Figma product currently charges $19.99 a month for up to 120 generated screens and $49.99 for up to 250. It uses existing product screens, design systems and other context to generate more interface work directly inside Figma.

These products sit at very different scales, but the pattern is pretty consistent. Revenue gets more interesting when the plugin controls an ongoing workflow rather than selling access to one clever action.

What kind of Figma plugins will people still pay for now?

Figma users still pay for plugins that repeatedly save serious work, connect Figma to something outside Figma or handle a problem with real professional consequences.

The pricing we found makes the difference visible.

Create Specs charges $8 a month for unlimited design-system documentation. It can generate component anatomy, spacing, colors, typography, variants and nested-component information from Figma components. A design-system team has to keep that documentation current as the system changes, which gives the product repeated value.

Mokko charges $19.99 to $49.99 a month because screen generation also repeats. Product teams constantly explore new flows, edge cases and revisions, and AI generation has an ongoing compute cost.

Tokens Studio can charge far more because the product sits inside the infrastructure connecting design decisions to code and other tools.

Stark moves higher again when accessibility becomes an organizational process rather than a quick contrast check. At that point, companies are paying for monitoring, governance, reporting and compliance across multiple stages of product development.

The common thread is frequency plus consequence. People can justify recurring payments when a problem returns every week or when getting it wrong costs the company time, money or risk.

A plugin somebody runs twice a year needs a very different business model.

Are simple Figma utility plugins becoming obsolete because of AI?

Many simple Figma utility plugins are becoming much harder to monetize now because users can increasingly generate the tool themselves.

Figma's own examples make the threat unusually concrete. Its generative-plugin documentation suggests asking the agent to build tools for sorting layers, creating different spacing densities, applying consistent padding, or finding and replacing text and colors.

Several years ago, any one of those ideas could have become a standalone Community utility.

Today, a Figma user can describe that workflow to the agent. No Plugin API knowledge is required. And after Figma's latest update, users can publish generated plugins to Community or distribute them privately within an organization.

Generative plugins currently have limits that protect classic plugin businesses. They cannot yet be monetized, they cannot call third-party APIs, and their interface is more constrained. Classic plugins still make far more sense for sophisticated commercial products.

But those restrictions do not rescue a basic utility whose customer mainly wants the task completed. A company may simply generate an internal version instead of buying one.

AI also helps plugin developers, of course. A solo creator can build and iterate much faster than before. Mokko shows that AI itself can support a paid plugin when it is wrapped around useful product context.

The important change is that writing the plugin code is becoming less valuable. The harder parts to copy are the workflow, data, integrations, history, specialized evaluation and company-specific context around it.

Could Figma just add your plugin's feature to Figma itself?

Yes. Figma absorbing a successful plugin category is one of the biggest risks for anyone whose whole product is a missing Figma feature.

Design tokens give us a good example. Tokens Studio became important partly because Figma lacked strong native token tooling. Figma later launched Variables and continued expanding its native design-system capabilities.

Tokens Studio survived because it kept moving beyond the original gap. Today it sells versioning, releases, code synchronization, cross-project workflows and broader design-system management.

AI gives us another example. Diagram built Magician, a popular collection of AI tools for designers, before Figma acquired Diagram. Figma has since built AI much deeper into the product, covering writing, image generation, repetitive automation, its agent and other creative workflows.

The risk is even higher now because Figma is moving quickly. Its latest quarterly update highlighted Code Layers, the Figma agent, generative plugins, Motion, Shaders and Weave Tools. More tasks that previously sat around the edge of the design editor are moving onto Figma's own canvas.

We would be especially cautious about businesses whose pitch is basically "Figma doesn't have this button yet."

The safer territory starts when the useful part continues to exist even if Figma adds the underlying feature. External data, cross-platform workflows, compliance, proprietary logic, collaboration history and deep integrations are much harder for one native feature to erase.

Is building a business on Figma's API too risky now?

Figma's API is still usable enough to build a business on, but developers should now plan for the possibility that platform access becomes more expensive or more controlled.

Figma continues to support classic plugins and explicitly says they are not going away. The company is investing in new plugin APIs and plugin interfaces that can benefit both classic and generated plugins.

So there is currently no evidence of Figma trying to shut its developer ecosystem down.

There is, however, a new financial risk worth taking seriously. In its latest quarterly filing, Figma said it is evaluating consumption-based pricing and metering for parts of its developer platform. It specifically mentioned rate limits and usage-based charges for certain APIs, MCP access and other programmatic access.

Figma has not announced that ordinary plugin API usage will suddenly become paid. The filing describes something the company is evaluating.

Still, it is a useful warning for anyone building a business on the assumption that large amounts of automated Figma access will remain free forever.

The best protection is fairly straightforward: keep as much of the valuable customer relationship, data and processing as possible under your control.

Tokens Studio's design-system platform lives beyond one Figma API. Stark reaches into browsers, code repositories, CI/CD and mobile products. If Figma changes something, those companies still have customers using a broader system.

A plugin that exists entirely inside one API call has much less room to adapt.

Can Figma plugins really be sold to enterprise customers?

Yes, but selling a Figma plugin to a large company quickly starts looking like regular B2B software sales.

Enterprise customers can require approval before employees use third-party plugins. Figma admins can control which plugins are available and, on larger plans, inspect how approved plugins are being used.

That adds friction for a new developer. A designer liking the plugin may no longer be enough. Security, IT or procurement can become part of the sale.

The upside is much higher pricing when the plugin handles an important company-wide problem.

Stark's pricing shows the jump. Its Scale plan currently starts at $21,000 per year and includes SSO, JIT provisioning, security reviews, a dedicated account manager, governance features and support for thousands of monitored pages.

At that point, the customer is paying to manage accessibility across an organization. The Figma integration simply puts part of that workflow where designers already work.

This is an attractive path for products in design systems, accessibility, governance, brand management, localization or other areas where companies need consistency across many people.

The challenge is that the product has to deserve an enterprise sales process. A nice layer-cleanup tool probably does not.

Do big Figma plugin install numbers actually mean much?

Big Figma plugin usage numbers can look impressive while telling us surprisingly little about revenue.

Figma itself warns us to be careful here. The usage number shown for Community resources does not simply mean "paying customers." Depending on the resource, it can represent people who used the plugin, duplicated something, authenticated an app or even previewed a paid resource.

So we cannot look at a plugin with 50,000 or 500,000 users and derive its revenue.

The economics can also work in the opposite direction. A plugin with only 500 paying customers at $20 a month produces $10,000 of gross monthly subscription revenue before marketplace fees and expenses.

That is why the most interesting metric for a plugin business is repeated usage among people with a reason to pay.

A huge top-of-funnel audience is useful if the developer can convert part of it. Without that conversion, the number mostly proves that people clicked Install.

Can Figma Community still bring a new plugin users today?

Yes, Figma Community can still be a powerful distribution channel, but relying on Community alone is much less comfortable today.

The basic advantage remains excellent. A plugin can appear inside the ecosystem where designers are already working, and users can search for tools without first visiting an external software marketplace.

Very few SaaS founders get distribution that close to the moment when the customer feels the problem.

The difficult part is standing out. The ecosystem grew from roughly 40 public plugins during the original beta to more than 10,000 plugins and widgets before the latest wave of generated tools.

And Community supply can now increase much faster. Users with access to Figma's agent can create a generative plugin through prompting and submit it to Community. Figma has effectively lowered the cost of creating another competing utility.

That makes external distribution more valuable. Search traffic, tutorials, social content, communities, integrations, word of mouth and a separate website can bring users into the plugin rather than leaving discovery entirely to a crowded marketplace.

The strongest businesses we looked at already work this way. Their Figma listing is one acquisition channel inside a broader product rather than the whole marketing strategy.

Is it smarter now to sell a Figma plugin or build SaaS around it?

For a serious business, the stronger model today is usually a SaaS product that uses Figma as one of its main interfaces.

Tokens Studio makes the logic easy to see. Its €17 Variables plan includes a companion plugin and its Studio platform. The €169 Essential plan adds versioning, releases, branching and direct-to-code workflows. The €499 Organization plan adds more projects, editors, asset management, documentation and security support.

The customer has moved from paying for a plugin action to paying for a system.

Stark follows the same path from another direction. Designers may encounter Stark through Figma, while larger customers use it across websites, repositories, CI/CD, mobile apps, reports and compliance workflows.

Mokko is earlier in that evolution but already keeps important value outside the canvas through model usage, product context and its credit system.

This structure raises the ceiling and gives the developer more protection from changes inside Figma. If Figma adds one feature, it has only reproduced one part of the product.

Business model	Realistic revenue ceiling	Exposure to Figma copying the feature	Best use today
Small paid utility	Low to moderate	High	One sharp individual pain
Premium standalone plugin	Moderate	Medium-high	Repeated professional workflow
Plugin + SaaS	High	Medium	AI, data, synchronization, integrations
Plugin + enterprise platform	Very high if the problem supports it	Lower	Compliance, governance, design systems

Which Figma plugin ideas still look strongest today?

The strongest Figma plugin ideas today sit around workflows that keep accumulating context, connect Figma to other systems or solve problems companies really care about.

Design systems still fit that description. Native Figma Variables have made basic token management less differentiated, yet companies still need to synchronize design decisions, code, releases, documentation and multiple projects. Tokens Studio's current pricing shows how much larger that problem can become than the original plugin feature.

Accessibility works for similar reasons. A basic contrast checker is easy to copy. Managing accessibility across design, code, websites, mobile products and compliance reporting is much harder.

AI generation can work too, but a generic "type a prompt and get a design" plugin now sits dangerously close to what Figma itself is building. Mokko's more interesting angle is using the customer's existing screens, product context and design system to generate related screens that fit the product.

Localization, production automation, proprietary-data workflows, design-to-code infrastructure, brand governance and specialized handoff can all have similar characteristics.

The simple test we would use now is whether the valuable part of the business survives after basic manipulation of a Figma file becomes almost free.

If the answer is yes, there may still be something worth building.

Is it easier or harder for a solo developer to make money from Figma plugins now?

It is easier than ever for a solo developer to build a good Figma plugin and harder than before to make an ordinary one worth paying for.

On the building side, the improvement is huge. Figma's agent can now create working plugins from prompts. AI coding tools can help with classic plugins too. Native monetization handles subscriptions, trials, payments and taxes. A developer can get much further with less engineering work.

Figma's audience is also far larger. Earlier this year, the company reported roughly 690,000 paying customers, 54% more than a year earlier.

But easier creation means easier competition. A developer no longer deserves much of an advantage simply because they can manipulate Figma through code.

A solo founder who understands one frustrating professional workflow extremely well may actually be in a better position these days. They can build cheaply, test quickly and reach the exact users who feel the problem.

A solo founder whose main advantage is "I know how to build Figma plugins" has a much weaker position.

Knowing what to build has become more valuable than knowing how to build the plugin.

Can Figma plugins still make money now?

Yes. Figma plugins can absolutely still make money today, but small generic utilities are becoming a much worse business while deeper workflow products still have plenty of room.

The demand side looks healthy. Figma's latest quarter grew 48% year over year to $370.1 million. The company has thousands of customers spending more than $10,000 a year, its biggest accounts are still growing quickly, and roughly two-thirds of its monthly active users are now people outside traditional design roles.

Creators also have better monetization tools than they did during the early plugin era. Classic plugins can sell subscriptions or one-time purchases directly through Community, and Figma handles much of the payment infrastructure for a 15% fee.

The pressure is coming from supply.

Figma had already accumulated more than 10,000 plugins and widgets. Now its agent can build simple plugins from prompts, and generated plugins can be published to Community. Figma itself is also moving aggressively into automation, AI generation, design systems and other areas once filled by third-party tools.

That makes the old strategy of finding a missing button and charging for it increasingly fragile.

There are still several ways to build a good business. A focused plugin can produce worthwhile side income with a few hundred paying customers. A deeper product can use Figma as its distribution and workflow layer while charging for AI, data, integrations, collaboration or infrastructure outside the plugin. At the high end, products such as Tokens Studio and Stark show that a Figma integration can lead into software sold for hundreds of euros per month or thousands of dollars per year.

So our answer is clearly yes, but with a much narrower definition of what looks attractive now.

Figma plugins still make money. The best businesses increasingly make money from the workflow around the plugin.