Guide6 min read

Figma Make Demo Video

Show a Figma Make flow the way it actually behaves, not the way a prototype implies.

Turn a Figma Make app into a reviewed demo video, accounting for what its generated flows do and do not persist between visits.

See how it worksYour first 60 seconds of video are free, with a watermark.
Verify your email to download it.

gogoscreen.com

Confirm what the flow actually persists

Confirm whether the action you plan to show actually persists after it happens, before writing the hint around it.

Open the route by hand

Open the exact route in a browser first and check what a fresh visit actually shows before recording.

Write the hint and review

Write a one line hint naming the start, the action, and the result, then review the finished candidate against what you confirmed by hand.

A Figma Make build often starts life as a design brought to life rather than a fully engineered application. That distinction matters for a demo video more than it does for most other builder platforms, because the thing that looks like a working feature on screen does not always behave like one behind the scenes. Before recording anything, it is worth confirming what the flow you plan to show actually does, not just what it appears to do when clicked through once.

GogoScreen takes a web app URL and a one line hint about what to show, then returns a narrated MP4 with automatic editing: zooms on clicks, cursor smoothing, dead air cuts, and burned in captions. It can use a demo account when a route sits behind a login, though many Figma Make builds are published without one, since they are frequently generated for a design or prototype purpose rather than as a full account backed application. None of this is a promise that a particular Figma Make build or a first render will come out usable. Review time belongs in the schedule regardless.

What does the flow actually do once the action is taken?

Click through the intended flow yourself before deciding it belongs in the video. Add the item, submit the form, or trigger whatever action the demo is meant to show, then refresh the page or revisit the route. If the result disappears or resets, that tells you the interaction may be visual rather than backed by persistent storage, and the video should be framed accordingly rather than implying the change was saved somewhere.

What to check	Why it matters for a Figma Make build	What to do if it fails
Does the action's result survive a refresh	Distinguishes a real state change from a visual only interaction	Choose a different action, or frame the video around the interaction itself
Does the route require a login	Not every Figma Make build includes account handling	Confirm before writing a hint that assumes one exists
Does the flow work the same on a second visit	Some prototypes are tuned for a single pass through	Test twice before trusting the flow for recording

A demo video from a website URL guide covers the broader question of preparing any URL based flow for capture, which applies here alongside the persistence check specific to this platform.

Which flow is worth showing?

Pick the interaction that best demonstrates the interface behaving the way it was designed to, whether or not it persists data afterward. A Figma Make build is often judged on how the interaction feels rather than on backend completeness, so an action with clear visual feedback, such as an animated transition or a state change that is obviously visible, tends to demonstrate the product well even when nothing is saved behind it. Just be accurate in the narration about what is happening rather than letting the phrasing imply persistence that was not confirmed.

This is also where the reviewer's eventual reaction matters. Someone who has used a fully backed application before may reflexively assume any convincing interface is doing more underneath than it actually is. Choosing an honestly framed interaction and describing it accurately protects the video from that assumption backfiring later, when the viewer tries the same action themselves and gets a different result than the one implied on screen.

If the build does include an account system, decide whether that screen adds anything for the intended viewer. If it does not, and many Figma Make builds skip account handling by default, then the video can open directly on the interface itself without a sign in step to account for. Either way, avoid guessing. Confirm what the actual build requires before writing the hint, since assuming a login exists when it does not will produce a hint the route cannot follow.

Test the intended action twice, checking whether the result survives a page refresh.
Confirm whether the build requires a login at all before assuming a demo account is needed.
Prepare any needed data by hand rather than expecting it to already exist.
Write the hint around what you actually confirmed, not around what the interface implies.

How should the hint be written for this kind of build?

Keep the hint specific to the one interaction confirmed by hand: the starting screen, the single action, and the visible result, worded the way the interface itself labels things. A hint that assumes backend behavior the build does not have, such as "show the saved order in the account history," will produce a confusing or failed render if no such history exists. Write the hint to match what was actually tested, not what a similar app on a different platform might do.

What is the short version of this process?

Confirm whether the action you plan to show actually persists after it happens, before writing the hint around it.
Open the exact route in a browser first and check what a fresh visit actually shows before recording.
Write a one line hint naming the start, the action, and the result, then review the finished candidate against what you confirmed by hand.

What should you check before this goes public?

Watch the candidate against what you confirmed by hand earlier. Check that the narration does not claim more than the interface actually does, particularly around whether anything was saved. If the candidate does not match the intended job, adjust the hint and try again rather than publishing it as is. Roughly one render in five needs exactly this kind of retry, so build that expectation into the schedule from the start.

Every new account gets 60 seconds of video once, watermarked, with email verification required before download. After that, you pay for video time: Starter is $29 for 15 minutes a month, Pro $79 for 45 minutes, and Business $199 for 120 minutes, and top ups start at $10, about $2.07 a minute, and never expire. Time is used only when a render succeeds, held at submission and returned automatically if the render fails.

Where does this video go next?

Once a candidate has passed review, match it to the surface that needs it. The build's own landing page video usually wants a shorter, above the fold cut of the same flow. A Product Hunt launch video has its own length and aspect constraints for the gallery. Sharing the build with a non technical reviewer is covered in the guide on how to share a Figma Make project with a client, a portfolio entry usually wants the interface shown running rather than described, and a formal review walkthrough frames the flow around what was asked for.

Related guides worth reading include the landing page demo video guide, the investor demo video guide, the beta launch demo video guide, and the AI agent launch demo video guide. Compare direct URL options at GogoScreen versus ngram, review pricing before committing to a plan, or browse the rest of the guides and comparisons from the homepage.

Clarifications

Before you start

What should a Figma Make demo video show?

One user job from a recognizable starting screen to a visible result, the same as any web app demo. Confirm first whether that result actually persists after the interaction, since a Figma Make build does not always keep state the way a fully backed app would.

Does a Figma Make app need a login for the demo?

Not always. Many Figma Make builds are published without an account system, since they are often generated for a design or prototype purpose rather than as a full application with user accounts.

Will the first render always show the app correctly?

No. Roughly one render in five fails or needs a retry, the same as for any other web app. Review the candidate before it goes anywhere public.

Paste a URL, describe one flow, and get a demo video of your web app.

Your first 60 seconds of video are free, with a watermark. Verify your email to download the video.

View pricing Read the guides