Can a client comment on a Figma Make app without a Figma account?

Not directly. Figma Make's published links let anyone view and interact with the app, but there's no built-in guest commenting. To collect pinned feedback without requiring an account, export the screens and share them through a review tool that supports guest comments.

How do I share a Figma Make app without showing my prompt history?

Use the Publish option inside Figma Make — it generates a clean figma.site URL that shows only the app, not the AI chat or prompt log. Avoid sharing the Make editor URL directly; that exposes everything.

What is the difference between sharing a Figma Make app and a regular Figma prototype?

A Figma prototype shares a static frame flow from a design file. A Figma Make app is a functional web app built with AI — it has live logic, real inputs, and connects to data sources like Supabase. Sharing works differently: Make apps publish to figma.site, not through Figma's prototype viewer, and they don't inherit Figma's comment system.

How do I collect structured feedback on specific UI elements in a Figma Make app?

Export screenshots of each screen, then share them through a review tool that supports element-anchored comments. This lets your client click the exact button, field, or section they mean and pin a note to it — instead of describing location in prose ('the thing near the top on the left').

Does Figma Make support comments from clients or stakeholders?

As of 2026, Figma Make has no built-in stakeholder commenting. There's an open feature request for 'comments in Figma Make' on the Figma forum. The current workaround is to export and share screens through an external review tool.

What do I do if my client won't make a Figma account to leave feedback?

Most won't — and it's reasonable to not ask them. The standard freelancer workaround is to export your Make screens and share a review link through a tool that accepts comments as a guest. They open a URL, click the spot they mean, and type. No account creation, no platform onboarding.

drafty

How to get feedback on a Figma Make app

Quick answer

To get feedback on a Figma Make app, export or screenshot the current state and share it through a tool that accepts comments without a Figma account. Figma Make's built-in share options either expose your full prompt history or drop the client into the raw Make interface — neither is clean for client review. The practical path: export, share a link, and collect pinned notes on the exact spot.

Step 1

Share a published link (and know what the client will see)

Figma Make lets you publish to a public URL under figma.site. That link shows the working app — no prompt history, no Make interface. The limitation: the client can interact with the app but has no way to leave a comment on a specific element. You'll get feedback via Slack or email ('the button near the top felt off'), and spend time working out which button they meant. It works for quick demos but falls apart for sign-off on a specific build.

Step 2

Take a screenshot and share it for annotated feedback

Screenshot each key screen of the Make app, then drop them somewhere the client can mark up specific spots. Google Slides lets them draw on top with a stylus or text box. Google Docs accepts image comments. Neither pins feedback precisely to an element — a note on an image ends up as a comment floating near the top of the page, not anchored to the actual button or field. Still, for a small number of screens this is the fastest zero-tool option if your client is already in Google Workspace.

Step 3

Share a review link with element-anchored comments

Export the screens from Figma Make (screenshot or frame export), then drop them into a review tool that lets your client click the exact element and pin a note to it. They open a URL in any browser, click the component they mean, and type — no Figma account, no Make interface, no prompt history visible. You see every note in one thread, reply, and mark it resolved. This is the pattern most freelance designers use when the client has never touched Figma — it keeps feedback off email and tied to the actual UI.

Step 4

Avoid sharing the raw Make interface with clients

It's tempting to copy the Make editor URL and send it directly. Don't. The client sees your full prompt history, the AI chat panel, and the code/preview toggle — none of which is relevant to them, and all of which can expose your working process. Figma's forum has a standing request for a 'prototype-only share without AI chat' option (filed 2025, open as of 2026). Until that ships, the export path keeps what your client sees clean and focused on the actual output.

The faster way

If you're iterating fast in Figma Make and need clean client sign-off between builds, export the key screens and drop them into Drafty. Share the link — your client clicks the exact button or field they mean and pins a note to it, no account. You see every note in one thread, reply in context, push a revised export to the same URL, and resolve. Feedback that used to scatter across iMessage and a 'the thing near the top' Loom stays pinned to the actual element.

Open a live demo

Questions

Can a client comment on a Figma Make app without a Figma account?: Not directly. Figma Make's published links let anyone view and interact with the app, but there's no built-in guest commenting. To collect pinned feedback without requiring an account, export the screens and share them through a review tool that supports guest comments.
How do I share a Figma Make app without showing my prompt history?: Use the Publish option inside Figma Make — it generates a clean figma.site URL that shows only the app, not the AI chat or prompt log. Avoid sharing the Make editor URL directly; that exposes everything.
What is the difference between sharing a Figma Make app and a regular Figma prototype?: A Figma prototype shares a static frame flow from a design file. A Figma Make app is a functional web app built with AI — it has live logic, real inputs, and connects to data sources like Supabase. Sharing works differently: Make apps publish to figma.site, not through Figma's prototype viewer, and they don't inherit Figma's comment system.
How do I collect structured feedback on specific UI elements in a Figma Make app?: Export screenshots of each screen, then share them through a review tool that supports element-anchored comments. This lets your client click the exact button, field, or section they mean and pin a note to it — instead of describing location in prose ('the thing near the top on the left').
Does Figma Make support comments from clients or stakeholders?: As of 2026, Figma Make has no built-in stakeholder commenting. There's an open feature request for 'comments in Figma Make' on the Figma forum. The current workaround is to export and share screens through an external review tool.
What do I do if my client won't make a Figma account to leave feedback?: Most won't — and it's reasonable to not ask them. The standard freelancer workaround is to export your Make screens and share a review link through a tool that accepts comments as a guest. They open a URL, click the spot they mean, and type. No account creation, no platform onboarding.

Keep exploring

How to annotate a Figma file Review a website BugHerd alternative Website feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo