How do I share a Figma Make prototype without the chat?

How to show a client a Figma Make prototype without the prompts and code beside it, and how to see who opened it and what they did.

On this page

By Kaz Kato · Published 20 October 2026 · Updated 20 October 2026

Send the app, not the Make file. Publishing puts the working app, without the chat, at its own address on the web, and a password can go on it. To see who opened it, download the code and put the build in a room. Only the built app goes in, and each client gets their own link.

This guide covers the two ways to send a Figma Make prototype without the file you built it in: Figma’s own publishing, and a room. It says what each gives the client, what each tells you afterwards, and how to move the code across. If you are still building, using mock data in an AI-built demo is worth reading first.

Ways to send a Figma Make prototype

Way What the client opens Keeping it to one client What you learn afterwards
Share the Make file The file you built it in, its chat included Figma’s file sharing Who you shared it with
Publish to figma.site The app, at a random public address One password for everyone Google Analytics totals, if you connect it
Download the code and deploy it to a room (ours) The app, on a link in their name A link each, which you can revoke Who opened it, when, and their time on each app and page

Anyone a Figma Make file is shared with can see its conversation with the AI, as well as its content. People who open a published Figma Make app cannot see the conversation, or the Make file it was published from. So for a client, send the app, not the file.

How do I publish a Figma Make prototype?

Publishing puts the app on the web at a randomly generated address ending in figma.site. Anyone with that address can open it. Only Figma’s two largest plans can keep it inside your organisation, which does not help with a client outside it.

Publishing a Figma Make file puts it on the public web at a randomly generated figma.site address. Only Figma’s two plans above Professional can keep it to people in your organisation. Only Full seats on Figma’s paid plans, and Starter plans, can share or publish a Figma Make file. On Starter, publishing to the public web also puts it on the Figma Community.

So a published prototype is public by default. Anyone your client forwards it to can open it too, and you will not know they did. Check what is in it before you publish: invented names and figures only, never a real client’s data. Is it safe to send a client an AI-built app? has the full checklist.

Can I password-protect it?

Yes. Figma Make can put one password on the published app, and every visitor types it before they see anything. It keeps strangers out. It does not tell you which client opened it, and you cannot shut out one person without changing the password for everyone else.

Figma Make can put one password on a published app, which every visitor enters before they see it.

Figma’s help page on password protection says nothing about a record of who opened a protected file or prototype. That page is about design files and prototypes in Figma Design, but it is the closest Figma’s help comes to the question.

Can I see who opened it?

Not by name. Figma Make has no analytics dashboard; a published app can carry Google Analytics or another snippet, which count visits and pages. They cannot tell you that your prospect opened it on Tuesday, came back on Thursday and forwarded it to a colleague. A room records that, link by link.

Figma Make has no analytics dashboard of its own. A published app can carry a Google Analytics ID, or another analytics snippet, added in the file’s settings.

In a Roomi room on Pro, each client opens a link made in their name. You see when they opened it, the time they spent on each app and page, how far they got through the tour and any comment they pinned to a screen. If they pass it on, whoever opens it next is asked who they are, and appears under the original link. Analytics and the pipeline shows what you see.

Download the app’s code from Figma Make, build it on your own computer and deploy it to a room. The build is only the app a browser runs, so there are no prompts beside it. Then make a link for each client. They open it with no account, and you see each one’s visits.

  1. Download the code. A Figma Make file’s code can be downloaded as a zip by someone with a Full or Dev seat. Make can also push the code to GitHub, if you would rather keep it there. Figma Make can push a file’s code to GitHub on every plan, to a repository it creates for that file; it cannot push to one you made yourself.
  2. Unzip it into a folder of its own on your computer.
  3. Deploy it. Open the folder in Claude Code and say “deploy it to roomi”. The Roomi plugin drives the command line, and Claude offers to install it if you need it. It builds the app, checks it for secrets and rehearses. Nothing goes live until you say yes.
  4. Or run the commands yourself. Install the app’s packages as you normally would, then run roomi init and roomi deploy in the folder. Add --commit once the rehearsal looks right.
  5. Make a link for each client. On Pro, give the link the client’s name, and an expiry if you want one. Sharing a private link covers every option.
  6. Send it, with one line on what to try first. Send it yourself, or tick Send this for me in the app and Roomi emails them the link for you. Either way, tell them the room records what they do there and shows it to you, as the terms ask.

An app that runs in the browser alone deploys as a static demo, on every plan, Free included. On Free it is a draft only your workspace opens, or a public listing on the community. A link for each client starts on Pro, at £4 a month. If the app talks to a server of its own, it runs as a container demo, on the paid plans, and any data it reaches should be invented.

When you change the prototype in Figma Make, download the code again and deploy it again. Everyone’s link stays the same and opens the new version.

What about Figma Sites?

Figma Sites publishes in much the same way as Figma Make: a random figma.site address, on Figma’s paid plans. So it has the same limit for a client as a published Make app: one public address, the same for everyone who opens it.

Figma Sites is on Figma’s paid plans. A published site is open to anyone on the web at a random figma.site address, which cannot be changed. Its two largest plans can keep a site to an internal audience.

For a site you want a client to try and comment on, a room with a link for each of them tells you more. Pricing shows what each Roomi plan includes, and sharing a Figma Make app has the steps on one page.

Questions people ask

Can I see who opened my published Figma Make app?

Figma Make has no analytics dashboard of its own. A published app can carry a Google Analytics ID, or another analytics snippet, added in the file’s settings. Those count traffic, not people. In a Roomi room, each client has a link in their name, and you see their visits and their time on each app and page.

Can I keep a published Figma Make app to one client?

Figma Make can put one password on a published app, which every visitor enters before they see it. Everyone shares that one password, so you cannot tell one client from another or close the door on just one.

Do I need to know how to code to put it in a room?

No. Download the code, open the folder in Claude Code and say “deploy it to roomi”. With the Roomi plugin, Claude builds it, checks it and rehearses the deploy. Nothing goes live until you say yes.

Sources

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit. More at katosan.co.uk.

Send the prototype, not the prompts.

Deploy it free, and give each client their own link on Pro.

Get started freeSee pricing