What Is Figma Make, and How Do I Get a Figma Make Project Live?
Figma Make is Figma's AI-driven, prompt-to-app tool: you describe what you want, and it builds a working prototype or web app you can keep refining, publish to a URL, and pull the code out of. It ships inside Figma itself, not as a separate product. This post covers what plans and seats include it, how its credit system works, the exact steps to publish and connect a domain, and how to get the code out through a download or a GitHub push — sourced from Figma's own help center.
What is Figma Make?
Figma's help center defines it directly: "Figma Make is an AI-driven, prompt-to-app tool that lets you bring ideas and existing Figma designs to life as functional prototypes, web apps, and interactive UI" (Figma Help, "Figma Make FAQs", checked September 2026). You write a prompt, optionally attach an existing Figma design so Make works from your actual layout and styles, and the tool generates a functional build you keep editing through more prompts or by opening the code editor directly. Figma also documents Make kits, which bring your design system package and written guidelines into Make so the output follows your design system (Figma Help, "Get started with Make kits").
This is a different job from publishing a Figma design as-is. If your Figma file already is the finished design and you just want it live as a website, Make isn't the tool for that — see how it compares to Figma's separate website-publishing product in Figma Sites vs Figment, which covers that distinction in detail.
Which plans and seats include Figma Make, and what do credits limit?
Figma Make runs on the same AI-credit system as Figma's other AI features, and access depends on your seat type, not just your plan:
| Seat / plan | What it can do in Make |
|---|---|
| Full seat, paid plan (Professional, Organization, Enterprise) | Full access: create files in team folders, share, publish, use the code editor |
| Dev, Collab, or View seat | Can try Make in drafts only: no sharing, no publishing, no team folders. A Dev seat can also export code |
| Starter (free) | Trial access, but can't use paid team libraries for style context, and "can only publish to the public web if they also publish to the Figma Community" |
| K-12 education | Not currently available (higher-education and bootcamp accounts are covered separately) |
(Figma Help, "Figma Make FAQs," checked September 2026)
Credits are the actual usage limit. Figma's credits article gives exact monthly allotments per Full seat: 500 credits/month on Starter, 3,000 on Professional, 3,500 on Organization, and 4,250 on Enterprise; Dev, Collab, and View seats get 500 credits/month regardless of plan, and Starter or View users also have "a daily limit of 150 credits" (Figma Help, "How AI credits work", checked September 2026). Figma's own approximations for what a Make action costs: a font change is "approximately 30+ credits," adding interactivity is "approximately 75+ credits," and generating an app from scratch is "approximately 100+ credits" — the same page notes these estimates "may evolve over time" as the underlying model changes. When you run out, "you'll see an in-product message letting you know," and you can't complete further AI actions until credits refresh or an admin adds more.
Check Figma's pricing page for current per-plan numbers before you commit a workflow to a specific credit budget — these figures move with plan changes.
How do I publish a Figma Make project?
Figma's own publishing guide gives the exact steps:
- Open the Figma Make file you want to publish.
- In the upper-right corner, click Publish.
- In the Publish modal, set a title.
- Adjust any settings you need in Make settings.
- Click Publish.
(Figma Help, "Publish, update, or unpublish a Figma Make file", checked September 2026)
Figma generates a URL in the pattern three-random-words.figma.site. To push a later change live, repeat the same steps and click Update in the Publish modal instead. To take it down, open Make settings in the upper-right corner and click Unpublish.
One detail worth knowing before you build a workflow around a paid seat: if you downgrade from a paid plan to free, Figma states that "any Figma Make files previously published to the web... will remain published." Publishing itself can also be turned off by an organization admin, so a blocked publish button may be a workspace setting rather than a bug.
By default, Figma says a published Make project "won't be indexed by search engines," though you can change its discoverability in the project's settings. Figma also states plainly that hosting runs on its own infrastructure — "Published functional prototypes or web apps are hosted by Amazon Web Services, while the domain and routing is served by Cloudflare" — and that "you are responsible for content that is published with Figma Make."
Can I use a custom domain with a published Make project?
Yes, on a paid plan, and the domain limit is shared with Figma's separate Sites product. Figma states: "Each plan has a custom domain limit, which is shared between Figma Make and Figma Sites. Organization and Enterprise plans can connect as many custom domains needed, and Professional plans can connect 10 custom domains" (Figma Help, "Figma Make FAQs," checked September 2026). Figma's publishing guide says the custom-domain steps for Make are the same as for a Figma Sites site. Check Figma's current pricing and help pages directly before you plan around a specific domain allowance, since shared limits like this one are exactly the kind of number that changes across plan updates.
Can I export the code, or push it to GitHub?
Both, and they're two different mechanisms with different rules.
Download a zip. Open the code editor inside your Make file and click Download code in the upper-right corner to get "a .zip file that contains all of the files in your Figma Make file" (Figma Help, "Edit the code of a functional prototype or web app", checked September 2026). Figma's seat table lists code export for Full and Dev seats, and in drafts only for Collab and View seats.
Push to a GitHub repository. In the upper-right corner of Figma Make, click Make settings, then GitHub. The first time, select Create Repository, name it, and click Create; every time after that, use Make settings > GitHub > Push to..., which pushes to the same repository Figma Make created (Figma Help, "Push from Figma Make to GitHub", checked September 2026). Figma states this is available on all plans, but it comes with real constraints worth knowing before you rely on it:
- One-way sync only. "It's a one-way push from Figma Make → GitHub. If you edit your code in GitHub, those changes won't appear in Figma Make and will be overwritten next time you push from Figma Make to GitHub."
- Figma-created repos only. "You can't push to GitHub repos you've created yourself. Figma Make only pushes to repositories it creates."
- Default branch only. Every push lands on the repository's default branch — there's no branch selection.
- No GitHub Enterprise Server, and the connection doesn't support GitHub IP allowlists.
If you plan to hand a Make project to a developer for ongoing work outside Figma, push it to GitHub once, then treat that repository as the new source of truth — the one-way sync means the two copies will drift, and Make will overwrite GitHub-side edits on the next push. For the broader checklist of what to verify (secrets, database ownership, auth callbacks) once an AI-generated project moves into your own codebase, see Moving an AI builder's project to your own codebase — it covers Bolt and v0, but the same handoff checklist applies here.
What are Figma Make's real limits?
- No two-way GitHub sync. GitHub is a snapshot, not a live mirror — keep iterating in Make and pushing again, or move to the GitHub copy for good, not both.
- Local development is announced, not shipped. Figma's own Make product page lists "Use Make locally to build in any codebase, then ship right to production" as "Coming soon" as of this writing.
- Seat and plan gates are real. A Dev, Collab, or View seat can draft but not publish or share; a Starter account can publish only by also publishing to the Figma Community.
- Credits are a hard stop. You can't complete an AI action with zero credits left — you wait for the refresh or ask an admin for more.
Is Figma Make the right tool, or should I use Figment?
If the job is "build an interactive app or prototype from a prompt or an existing design, and I want the resulting code," Figma Make is a genuinely strong fit — it's built for exactly that, with a real GitHub export path most AI app builders don't document as clearly. If the job is instead "I already designed this site in Figma and I just want it live as a website," Make is the wrong tool for that specific job: it's building a new functional app from your design, not shipping the design itself.
That second job is what Figment does — we publish Figma design files as websites through a Figma plugin, keeping the Figma file itself as the source of truth rather than generating a separate codebase. We don't have a prompt-to-app builder, an AI editor available for public use today, or anything like Make's code export; if you need those, Make (or Figma's own Sites product, covered in the comparison linked above) is the honest answer, not us.
