Two different searches end up on the same query. One is a designer who finds Figma Make slow or credit-hungry and wants another AI design tool. The other has a working prototype and needs it to become a page somebody can find.
The first person should read the table at the bottom. The second one has a shorter route, and it is worth trying before comparing anything: ask the agent you already pay for to build the page as plain static files, and give the result a real address.
One prompt: try the page without a builder
Plenty of Figma Make projects are a landing page that happens to be built as an app. If yours is, the swap is direct: paste this into Claude or ChatGPT.
Build this as a single static bundle: index.html plus one style.css, no build
step, no framework, no client-side router, no client-side routing at all.
Multi-page is fine as separate .html files that link to each other.
What it is: [one sentence]. Who it is for: [one sentence]. The one action:
[what you want them to do].
Style: [two words], and specifically oversized headline, high contrast, one
accent colour, generous whitespace, system fonts. Real copy, no placeholder
text.The "no client-side routing at all" line is doing the work. Left to its own defaults, an agent will happily hand you the same single-page app you are trying to get away from. Then time it against the same brief in Figma Make, and compare your own two numbers rather than ours. The rest of the prompts, including publishing and collecting remarks, are in AI website prompts.
What Figma Make actually gives you when you publish
From Figma's own help centre, and the details matter here:
- The URL is generated for you. "Figma Make provides a randomly-generated public URL... The generated URL will look like this:
three-random-words.figma.site." - There is a switch for keeping it out of search. An "Exclude all pages from search engine results" setting tells robots not to index the published prototype.
- It needs a paid seat. Figma Make is available for "Full seats on paid plans", and the Education plan includes one published file, subject to bandwidth limits.
Read together, that is a description of a very good prototype-sharing surface. Three random words is a fine address for something you are sending to five people this week. It is not an address you print, and a prototype is not what you want ranking for your product's name.
Figma Sites, which is the neighbouring product, is more site-shaped: publishing is available on all paid plans, a Starter plan has to upgrade, and after publishing "you can customize the subdomain of your site, or add your own custom domain."
The other thing to know before you plan a move
Figma Make produces a real single-page app. That is a feature while you are prototyping, and it is the one technical fact that decides where the result can go afterwards.
A single-page app expects the server to hand its entry file back for any path the browser asks about. Static hosts do not do that: they serve the file at the path or return 404. So a Make-style app on a static host works on the first screen and breaks on the second.
This is a boundary rather than a bug, and it is ours as much as anyone's. Birta serves static files, so an app that needs path rewriting is not a thing to move here.
If what you have really is an app, this is not us
- It is a single-page app with client-side routing. On a static host unknown paths return 404, and Figma Make's output is exactly this shape.
- It needs a server, a database or user accounts. Birta serves static browser files and nothing else.
- It needs to take payments on your own site. Not something Birta does yet.
- You need form submissions in Slack, Telegram or a webhook. Ours land in the project panel and an email digest only.
What you get instead of a generated URL
- Your own address, or a Birta subdomain you choose rather than three random words. A custom domain needs Solo or Pro.
- Indexable by default. Nothing to switch on; the page is a page.
- Versions and rollback, so every publish is recoverable.
- A review link that needs no account, with remarks pinned to elements on a frozen version. Your agent reads those numbered threads with the connector and fixes them in the same draft. It cannot reply in the thread or resolve one, so closing them stays with you.
- A declared lead form, submissions in the panel plus an email digest roughly fifteen minutes after the first one.
All of that is on the free tier, where the "made in Birta" badge stays on.
The honest alternatives
If you want another AI design or build tool, these are the real options. Note that the search results for this query are half about Figma the design tool rather than Figma Make, so be specific about which job you are replacing.
| Instead of Figma Make | What it is for | Worth knowing |
|---|---|---|
| Figma Sites | The site-shaped sibling in the same account | Publishing on all paid plans; you can set a subdomain or a custom domain |
| v0 | Prompt to UI, front-end first | Documented code export; output is a Next.js project |
| Lovable | Prompt to app with an optional backend | Clear docs on what is static and what is not |
| Bolt.new | Prompt to full-stack app in the browser | Its docs note a project published to Bolt hosting cannot switch to Netlify without a new copy |
| Uizard, Visily, Banani | Fast mockups for non-designers | Prototype tools; the output is not a website |
| Webflow | Designer-grade sites with a CMS | Its reviewer can reply and resolve, which our agent cannot |
| Your agent plus a host | A real page at a real address, today | No canvas and no design system. That is the trade |
Turn the prototype into a page at your address
Static publishing with versions, rollback and account-free review, all on the free tier.