How Figma Grew: The Product-Led Growth Strategy Behind $1B+ Revenue

Figma grew by turning collaboration into distribution.

Before Figma, designers often worked in desktop apps, exported their work, uploaded files, and sent them to teammates.

Figma made the design file a URL.

A designer could send that URL to an engineer, product manager, executive, or client. The recipient could open the latest version in a browser, inspect it, comment on it, and eventually work alongside the designer.

Every time someone shared their work, they also introduced another person to Figma.

That created Figma's core growth loop:

designer creates a file → shares the link → teammates open Figma → more people start using it → teams adopt Figma → companies upgrade

Figma then added free viewers, developer handoff, multiplayer editing, plugins, Community, education, and enterprise features around that loop.

It worked.

Figma reported more than 13 million monthly active users in its busiest month of Q1 2025. Two-thirds were non-designers.

About 70% of new Organization and Enterprise customers in 2024 and Q1 2025 had at least one person who had previously used Figma's Professional plan.

By 2025, Figma had reached $1.056 billion in annual revenue, up 41% from 2024.

The interesting part of the story is not the final number.

It is how Figma designed a product that distributed itself.

Figma's growth strategy in one table

Growth lever	What Figma did	Why it worked
Browser-first product	Made professional design software work in a browser	Anyone could open a file without installing software
Shareable URLs	Every design could be shared as a link	Sharing work also introduced people to Figma
Multiplayer	Multiple people could edit the same file in real time	Made collaboration much better than sending files back and forth
Free viewers	Engineers, PMs, and executives could participate without paid editor seats	Removed friction from inviting more people
Developer handoff	Developers could inspect designs and copy implementation details	Expanded usage beyond designers
Free plan	Small teams could start before talking to sales	Made bottom-up adoption possible
Community	Users published templates, plugins, UI kits, and other resources	Users created content that attracted and helped other users
Education	Students and teachers could use Figma for free	Created users before they entered the workforce
Enterprise plan	Added security, administration, shared libraries, and billing	Converted organic company adoption into large contracts
Product expansion	Added FigJam, Dev Mode, Slides, Sites, Make, and other products	Increased how many people and teams could use Figma

1. Figma spent years making design work in the browser

Figma was founded by Dylan Field and Evan Wallace in 2012.

Their early bet was simple but risky:

professional design software would eventually move to the browser.

At the time, serious design tools were desktop applications.

Browsers were good for reading websites. They were not considered good enough for manipulating large design files at professional speed.

Wallace had been experimenting with WebGL, a browser technology that gave web applications access to a computer's graphics processor.

That made a different kind of design tool possible.

Figma spent years building the technology needed to make it work.

The team built its own renderer, document model, text system, vector tools, and file format.

Field announced Figma's Preview Release in December 2015 after what he described as "three years of silence and hard work".

Figma had already been using the product internally for 18 months and working with alpha customers.

The public launch came in September 2016.

This long build mattered because Figma's later growth loops depended on one thing:

the browser experience had to be good enough for professional designers to actually switch.

2. Figma won its first users one team at a time

Figma did not begin by selling to huge companies.

Its earliest customers were smaller technology startups willing to try a new browser-based design tool.

Early adopters included companies such as Notion and Coda, which was then called Krypton.

Field and Wallace worked closely with those teams.

Field later told the story of onboarding Coda and driving away, only to receive an email saying that broken fonts would stop the company from evaluating Figma.

They turned the car around and fixed it.

This was Figma's early go-to-market strategy:

find teams open to a new way of working
watch them use the product
find what stopped adoption
fix it
repeat

The product still had a long way to go.

When Figma launched its closed beta in 2015, it did not even have multiplayer editing.

The first job was proving that a professional design tool could work in the browser.

3. Multiplayer gave Figma its breakthrough feature

Figma's public launch on September 28, 2016 introduced one of its most important features: real-time multiplayer editing.

Multiple people could now work inside the same design file at the same time.

This sounds normal today because tools such as Google Docs, Notion, and Figma made multiplayer software familiar.

For professional design software in 2016, it was unusual.

Traditional design workflows involved sending files between people.

One person might edit a file, upload it, send it to someone else, collect feedback, make another version, and send it again.

That created a common problem:

Which version is the latest one?

Figma removed much of that.

The file lived online.

Everyone could see the current version.

Multiple people could edit it.

Comments lived beside the work.

Figma spent roughly a year building the multiplayer system rather than using simpler ideas such as letting only one person edit at a time.

Evan Wallace explained the decision in Figma's 2016 multiplayer launch post.

That investment became one of Figma's biggest advantages.

4. The URL became Figma's best distribution channel

Multiplayer was powerful, but the browser created an even more important growth advantage.

Every Figma file was a URL.

Imagine a designer working with an engineer.

Before Figma, the designer might have needed to:

export the design
upload it somewhere
send it to the engineer
explain which version was current
send another file when the design changed

With Figma, the designer could send one link.

The engineer opened it in a browser.

That small change created a powerful product-led growth loop.

Every project naturally involved other people:

designers
engineers
product managers
researchers
marketers
executives
clients

When a designer shared a Figma file with one of them, that person encountered Figma because they needed to do their job.

Figma did not need a separate referral pop-up telling users to "invite three friends."

The work itself required sharing.

Sharing the product was part of using the product.

That is the core reason Figma's architecture became its distribution strategy.

5. Free viewers made the growth loop much stronger

Figma could have weakened this loop by charging every person who opened a file.

It did the opposite.

In 2017, Figma added developer handoff and let developers access files with free view-only seats.

Developers could inspect spacing, export assets, and access CSS, iOS, and Android information without buying an editor seat.

Figma explained the idea when it launched Figma 2.0.

This mattered because most people who needed to see a design were not designers.

An engineer did not need a full design tool.

A product manager did not need to edit vectors.

An executive might only need to review and comment.

Making those interactions free meant designers did not have to think about cost before inviting someone.

That expanded the growth loop:

designer → engineer → PM → marketer → executive → more teams

By Q1 2025, the result was visible in Figma's user base.

Figma reported more than 13 million monthly active users, and roughly two-thirds were non-designers.

Developers alone accounted for about 30%.

Figma had started as a design tool.

Its distribution model turned it into software used by entire product teams.

6. Figma used free plans to let teams adopt it before talking to sales

Figma started charging in 2017, but it kept a way for people to begin using the product for free.

That was important.

A designer at a company could try Figma without:

getting a large software budget
talking to procurement
booking a sales demo
convincing the entire company to switch

They could just start.

Then they could bring in teammates.

Figma did not get every part of its free plan right immediately.

Its original Starter plan limited shared files to two editors.

That created a problem.

Multiplayer was one of Figma's biggest advantages, but the free plan stopped many teams from fully experiencing it.

Figma tested removing the two-editor limit and instead limiting how much team content free users could create.

Teams in the experiment collaborated 29% more.

Figma changed the plan.

The lesson was simple:

do not put the paywall directly in front of the behavior that makes your product spread.

7. Figma expanded from designers to developers and product teams

Figma initially competed as a design tool.

But the browser gave it a larger opportunity.

Instead of asking only:

How do we make designers more productive?

Figma could ask:

How do we help everyone involved in building a product work together?

Developer handoff was an early step.

Prototyping removed another tool from the workflow.

Comments brought reviewers into files.

Shared design systems connected entire organizations.

Later products such as FigJam and Dev Mode expanded Figma further.

This increased the number of people who could become users without Figma needing to enter an entirely unrelated market.

The same design file could now connect the people who designed the product with the people who planned, reviewed, and built it.

8. Community turned users into a distribution channel

Figma's next major growth loop came from its community.

The company launched plugins publicly in August 2019.

After only six weeks of beta testing, Figma already had more than 40 public plugins.

Instead of Figma needing to build every feature itself, developers could build tools that extended the product.

That created another loop:

more users → more incentive to build plugins → better product → more users

Then came Figma Community.

Community let people publish editable resources that other users could inspect, duplicate, and adapt.

These included:

templates
UI kits
design systems
icons
plugins
widgets
wireframes
illustrations

This helped Figma in several ways.

Community helped acquisition

Useful Figma resources could bring new people into the ecosystem.

Community helped activation

A new user did not always need to begin with a blank canvas.

They could duplicate something useful and start editing.

Community helped education

People could inspect how experienced designers structured real files.

Community made Figma more useful

Creators kept producing resources Figma itself did not have to build.

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

Community became part of the product, not just a marketing channel around it.

9. Figma invested early in students

Figma also made the product easy for students and teachers to adopt.

In April 2020, Figma said more than 100,000 people already used Figma in classrooms.

It expanded its education program to online courses, bootcamps, hackathons, and more.

Verified students and educators could access paid features for free.

This created a long-term distribution channel.

A student could:

learn Figma → graduate → join a company → already know Figma → introduce Figma at work

The strategy worked especially well for a tool where users develop habits and workflows over time.

Figma could acquire someone years before that person had authority to buy software for a company.

10. Bottom-up adoption made enterprise sales easier

This may be the most important part of Figma's business model.

Figma did not begin by selling a giant enterprise contract and then asking employees to use the software.

Employees often started using Figma first.

The company contract came later.

Designers adopted Figma.

They invited coworkers.

More teams started using it.

Different groups inside the same company eventually had their own Figma accounts and projects.

Then larger companies needed things such as:

central billing
shared libraries
security controls
single sign-on
administration
organization-wide design systems

Figma launched its Organization plan in January 2019.

Uber was one of its beta partners and had moved about 90% of its product design work into Figma by the launch.

Square had moved more than 100 designers across over 25 products into Figma.

Enterprise sales could now enter a company where people already knew and liked the product.

Figma's IPO filing later showed how strong that bottom-up motion had become.

During 2024 and the first quarter of 2025, about 70% of new Organization and Enterprise customers included at least one user who had previously been part of a Professional plan.

Around 70% of Figma's revenue during those periods also came from Organization and Enterprise customers.

The growth path looked like this:

individual → small team → multiple teams → company → enterprise contract

That is product-led growth combined with enterprise sales.

11. COVID accelerated Figma, but did not create the growth engine

The shift to remote work in 2020 was perfect for Figma.

Teams suddenly needed software that worked:

remotely
across operating systems
in real time
without sending files around

Figma had already spent years building exactly that.

Its multiplayer system had launched in 2016.

Free viewers existed.

Developer handoff existed.

The Organization plan existed.

Plugins and Community existed.

COVID made all of those features more valuable.

Figma's own analysis later found that file sharing between designers and people in other roles increased 140%.

Cross-time-zone collaborative files grew even faster.

Remote work accelerated Figma.

But it is important not to confuse the accelerator with the engine.

Figma's growth system was already working before the pandemic.

12. Figma expanded the market with FigJam

Remote work also showed Figma that people were using its canvas for more than interface design.

Teams were using Figma for:

brainstorming
diagrams
games
workshops
planning
virtual social spaces

That helped inspire FigJam, Figma's online whiteboard product, which launched in April 2021.

FigJam gave Figma another way to spread inside companies.

Someone who never designed a user interface could still use Figma's ecosystem for a brainstorming session.

This was the beginning of a broader strategy:

expand from a design tool into a platform where teams turn ideas into products.

13. Adobe offered $20 billion for Figma

By 2022, Figma's growth had become impossible to ignore.

Adobe announced in September 2022 that it planned to buy Figma for approximately $20 billion in cash and stock.

Adobe said Figma was expected to add about $200 million in annual recurring revenue during 2022 and exit the year with more than $400 million in ARR.

The acquisition never happened.

Regulators in Europe and the UK raised competition concerns.

Adobe and Figma terminated the deal in December 2023.

Adobe paid Figma a $1 billion termination fee.

Figma remained independent.

14. Figma crossed $1 billion in annual revenue

Figma went public in July 2025.

Its financial results show how large the business had become:

Year	Revenue
2023	$504.9M
2024	$749.0M
2025	$1.056B

Revenue grew 41% in 2025.

Figma's growth also continued deep inside large companies.

By June 30, 2026, Figma reported:

15,964 customers with more than $10,000 in ARR
1,635 customers with more than $100,000 in ARR
136% net dollar retention among customers above $10,000 ARR

Those numbers show that Figma was not only acquiring customers.

Existing large customers were spending more over time.

The 5 growth loops behind Figma

Figma's story becomes easier to understand when you reduce it to five loops.

1. The collaboration loop

create file → share URL → teammate joins → teammate collaborates → more files get shared

The product naturally exposed itself to new users.

2. The team adoption loop

designer starts free → invites team → team depends on Figma → more teams adopt → company upgrades

This turned individual usage into enterprise revenue.

3. The community loop

more users → more templates and plugins → Figma becomes more useful → more users join

Users helped improve the value of the ecosystem.

4. The education loop

student learns Figma → enters workforce → already knows the product → brings it into a company

Figma acquired future professional users early.

5. The product expansion loop

more roles use Figma → Figma learns more workflows → launches products for those workflows → more roles join

This helped Figma expand from designers to entire product teams.

Why Figma grew so fast

Figma's biggest advantage was not simply that it had better design features.

Its product architecture made distribution easier.

The browser meant anyone could open a file.

The URL made sharing easy.

Multiplayer made collaboration useful.

Free viewers removed friction.

Developer handoff brought engineers in.

Community brought creators in.

Education brought students in.

Enterprise features turned bottom-up adoption into large contracts.

Each layer strengthened the one before it.

The result was a product where normal usage created new users.

What startups can learn from Figma

The biggest lesson from Figma is not "use product-led growth."

It is more specific.

Build distribution into the main action of the product

Figma users had to share their work.

Every share exposed another person to Figma.

The best viral loops are useful even if they never create a new customer.

Let collaborators experience the product cheaply

Figma could have charged engineers, PMs, and executives every time they opened a design.

That would have slowed distribution.

Instead, it made many of those interactions free.

Don't paywall the feature that makes people understand the product

Figma discovered this with multiplayer.

If collaboration is your biggest advantage, users need to experience collaboration.

Let small teams adopt before enterprise sales arrive

Figma's sales team could approach companies where employees were already using the product.

That is a much easier conversation than selling software nobody inside the company has tried.

Expand around the workflow, not randomly

Figma moved from design into prototyping, developer handoff, whiteboarding, presentations, websites, and other related workflows.

Each product served people already connected to the same work.

Frequently asked questions

How did Figma grow?

Figma grew through product-led, bottom-up adoption. Designers could create files in a browser and share them with a URL. Free viewers, multiplayer editing, comments, and developer handoff brought engineers, PMs, executives, and other teammates into the product. Teams then expanded organically until companies upgraded to Organization or Enterprise plans.

What was Figma's main growth strategy?

Figma's main growth strategy was making collaboration part of the product. Sharing a design also distributed Figma because recipients opened the file inside Figma itself. Free plans and free viewers reduced the friction of bringing new people into that workflow.

How did Figma get its first users?

Figma worked closely with small, innovative technology companies willing to try browser-based design software. Early users included Notion and Coda. Figma's founders personally onboarded teams, watched how they used the product, and quickly fixed problems that stopped adoption.

Why did Figma beat desktop design tools?

Figma's browser-based architecture made collaboration much easier. Files were URLs, stayed up to date, worked across operating systems, and supported real-time multiplayer editing. This reduced the need to export, upload, sync, and send different versions of design files.

How did Figma use product-led growth?

Individuals and small teams could start using Figma before buying an enterprise contract. They invited coworkers into files, adoption spread across teams, and Figma's sales team later helped companies consolidate that usage into larger Organization and Enterprise plans.

What role did Figma Community play in its growth?

Figma Community let users publish templates, design systems, plugins, widgets, and other resources. Those resources helped new users discover Figma, learn the product faster, and start projects without beginning from scratch. They also made Figma more useful without requiring Figma itself to build everything.

Did COVID cause Figma's growth?

No. COVID accelerated Figma's growth, but its main growth engine already existed. Figma had launched browser-based sharing, multiplayer, free viewers, developer handoff, enterprise plans, plugins, and Community before remote work surged in 2020.

How much revenue does Figma make?

Figma reported $1.0558 billion in revenue for 2025, up 41% from $749 million in 2024. Revenue is different from ARR, valuation, market capitalization, or the $20 billion price Adobe proposed to pay for Figma.

Did Adobe buy Figma for $20 billion?

No. Adobe agreed to acquire Figma for approximately $20 billion in September 2022, but the transaction never closed. The companies terminated the agreement in December 2023 after regulatory resistance. Adobe paid Figma a $1 billion termination fee.