Record a walkthrough, get a finished film
Record yourself using your own product for a few minutes and Frame24 turns it into a finished demo film — either a close edit of what you recorded or a fully composed film that uses it as source material.
The honest version of most product demos is a screen recording somebody made in ten minutes, narrating as they clicked through the thing they had just shipped. A walkthrough makeover starts from exactly that recording rather than asking you to write a script first, and turns it into a film without a manual edit in between.
What actually happens to the recording
The recording is read three ways: its timeline is scanned for the moments the screen meaningfully changes, its audio is transcribed for narration, and frames are selected by looking at what is actually on screen at each point rather than by timestamp alone. That reading is what the rest of the process is built from — a written interpretation of what you did and said, not the raw file.
Choosing a treatment
One decision sits above everything else, made on the upload card before the recording is even sent: how closely should the film follow what you actually recorded?
| Polish (default) | Full | |
|---|---|---|
| Structure | One scene per step you performed, in the order you performed it | A normally composed film, using the recording as source material |
| Narration | Your own words, kept verbatim | Written narration informed by what the recording showed |
| Screens | Your recorded screens, cut down | Screens are rebuilt as reusable product-UI components, available in later films too |
| Extra shots | None — nothing is invented that you did not do | Additional generated scenes are allowed if the brief calls for them |
| Best for | A faithful record of a real workflow, fast | A polished marketing film that happens to be grounded in something real |
Neither treatment is allowed to add a claim the recording never supported — that rule holds for both. What changes is structure: whether the film is your recording, cut close, or a composed film that treats your recording as evidence rather than as the shot list.
Recording one well
Recording a walkthrough worth making a film from
- Pick one real workflowNot a tour of the product — one job, start to finish, the way an actual user would do it. "Import a CSV and get a cleaned report" makes a better film than "here's the dashboard, and here's settings, and here's...".
- Talk as you go, plainlySay what you are doing and why, in your own words. You do not need a script, and you do not need to sound polished — the narration is transcribed and, for a Polish film, kept as you said it.
- Let mistakes happen and keep goingA stumble mid-sentence or a misclick does not need a re-take. The read looks for the moments the screen changed with intent; a recovered mistake reads as a real product being used, which a rehearsed take does not.
- Finish on the outcomeEnd on the result — the finished export, the number that changed, the thing that is now true. That is the shot most walkthroughs cut away from a beat too early.
What happens while you wait
Nothing about this mode makes you wait for the read before doing anything else. The rest of the create wizard — length, brand, voice, language — runs in parallel with the recording being processed; the film is ready once both are done. There is no separate review of the interpretation before it builds: for this specific mode, a long form standing between recording something and having a film is the thing being removed, not relocated.
Where a Polish makeover is the wrong choice
If the recording is genuinely rough — wrong workflow chosen, a long dead patch in the middle, screens with real customer data you have not thought about sanitising — a Full treatment or a fresh recording is usually faster than trying to rescue a Polish cut of a bad take. And if there is no recording at all yet, screenshots through product UI capture cover the case where a live walkthrough is not practical to record.
Questions people ask
Do I need to be good on camera to record a walkthrough?
No — nothing of the recording itself is published unless you choose to keep your narration verbatim in a Polish film. What matters is that you do one real workflow in the product and talk through it naturally; the useful frames and lines are selected from that afterwards.
How long should the recording be?
Two to five minutes covering one workflow. Longer recordings are fine but rarely add anything: the film is built from the moments the screen meaningfully changes, not from the total runtime.
What is the difference between Polish and Full?
Polish is a close edit of your own recording — one scene per step you performed, your own words kept verbatim, no invented shots. Full is a normally composed Frame24 film that treats your recording as material rather than a script, with the usual scene design and generated media available.
Can I review the film before it renders?
A makeover skips the brief-review step every other creation mode has, because reading the recording already takes a few minutes and a form to approve on top of that undoes the point. The ordinary create-wizard questions — length, brand, voice — still apply; you just do not see a written brief first.
Does the recording get published?
The original recording is kept privately after the film is made, so a later AI edit can refer back to it, but it is source material, not the deliverable — only the finished film is meant to be shared.
Keep reading
How to edit a screen recording with AI
AI can accelerate the mechanical edit, but it still needs a clear job and a review pass. This workflow keeps the result accurate and human.
Get your real product UI into the film
A public URL cannot see past your login. Here is how to give Frame24 the three or four screens that actually carry the argument.
How to make a product demo video
The best demo is not a tour. It is proof that one important job becomes easier. Here is how to script and show that proof.