How to record a product demo
The difference between a demo that gets watched and one that gets scrubbed past is decided before you press record. Almost all of it is preparation, and the preparation takes about five minutes.
Decide the one thing first
A demo that shows everything shows nothing. Before recording, write down in one sentence what the viewer should be able to do after watching — not what your product *has*, but what the viewer *gets*. "Turn a CSV into printable labels" is a demo. "Overview of features" is not. Everything you record then either serves that sentence or gets cut. This is also what makes the recording short, and short is the single most reliable quality in a demo: nobody has ever complained that a product video ended too soon.
Set the stage before you record
Clean up what the camera will see. Close the tabs that are not part of the story, sign out of anything personal, clear notifications — a Slack toast sliding in during the one good take is the most common reason people record a fourth time. Use a dedicated browser profile or a guest window if you have one. Prepare the data you will use so you are not typing "asdasd" into a field on camera; realistic sample data is what makes a demo feel like a product rather than a prototype. Then set your window to a sensible size, because a maximised 4K window makes every UI element tiny in the final video.
Record in one take, and record it badly the first time
Do a full run-through you intend to throw away. It costs a minute and it finds everything: the step you forgot, the loading state you did not account for, the modal that takes four clicks to dismiss. Then record for real, moving deliberately and pausing for about a second at each place the viewer needs to read something. Do not narrate with your mouse — wiggling the cursor to point at things reads as nervousness on playback. If you make a mistake, pause, and carry on rather than starting over; a pause is easy to trim, a restart costs the whole take.
Polish afterwards, not during
Recording and editing are separate jobs and doing them at once makes both worse. Record the clean run, then load it in and let the analysis propose zoom moves — it looks for where the picture changed sharply in a small area, which is usually exactly where you did something. Keep the two or three moves that land on real moments, drag the rest away, then choose a background and a frame. The whole polish pass is a few minutes and it is where a screen recording stops looking like a screen recording. And nothing you load leaves the tab: there is no endpoint on our side that accepts video.
Frequently asked
How long should a product demo be?
Shorter than you think. Thirty to sixty seconds covers one clear task, which is what most people are deciding on when they press play.
Do I need to narrate?
No. Silent demos with clear on-screen actions work well and travel further — they play with sound off in feeds and need no re-recording when you change languages.
What do I do about mistakes mid-recording?
Pause, take a breath, and carry on. A pause trims out cleanly; restarting costs you the whole take.
Does my recording get uploaded anywhere?
No. There is no endpoint on our side that accepts video — recording, editing and encoding all happen in the browser tab. Page analytics are separate and do not touch your video.
Which browser do I need?
Chrome or Edge on a desktop. Recording and editing work more widely, but exporting needs WebCodecs, which those browsers have.
Can I use a video I recorded elsewhere?
Yes — drop in an MP4 or WebM you already have. Anything the browser can play works; the only requirement is that the clip is at least a second long.
Turn a screen recording into a demo people watch. Record a tab, get automatic zoom moves where things actually happened, put it on a clean background in a window frame, and export MP4. Everything happens in the tab — no endpoint on our side accepts video.
Open Demo Studio