How to Record a Software Demo (Setup, Settings and Common Mistakes)
August 9, 2026
Most bad software demos are not badly recorded. They are badly prepared. The recording exposes an untidy account, a notification at the worst moment, or a flow the presenter had not actually rehearsed.
Ten minutes of setup saves an hour of re-recording, so most of this guide is about what happens before you press record.
Prepare the account first
- Populate real-looking data. Plausible names, sensible numbers, enough records that the screen looks used.
- Remove anything private. Real customer names, internal notes, billing details, anything under NDA.
- Get to the starting screen in advance. Never record yourself logging in and navigating to the interesting part.
- Check for empty states. A section with no data reads as a broken product, not an unused feature.
Prepare the screen
- Silence notifications. Do Not Disturb at the OS level, not just in the app you are recording.
- Close unrelated tabs. Tab titles are readable and often revealing.
- Raise the browser zoom to around 110-125%. Demos are watched in a small embed, and default zoom is usually unreadable there.
- Hide bookmark bars and extension icons that clutter the frame or identify tools you would rather not advertise.
Rehearse the exact path once
Click through the flow once without recording. You will find a dead end, a slow load, or a step that needs data you have not created. Finding those during a take is how a fifteen-minute job becomes an afternoon.
Write the path down as a list of clicks. Not a script of what you will say -- a list of where you will click, in order.
Capture at the right size
Record at the size the demo will be watched at, or larger. Scaling down stays sharp; scaling up does not.
For a demo embedded on a marketing page, a 1280-1440px wide browser window is a good target. Ultra-wide monitors are the most common cause of demos where nobody can read the text.
Mistakes that force a re-record
- Starting at a login screen instead of the moment value appears.
- Moving the mouse while talking -- constant motion is exhausting to watch. Move, stop, then speak.
- Recording the whole product rather than one flow. Long demos are abandoned, not watched at higher speed.
- Forgetting the ending. Decide what the last frame is before you start, so the demo concludes instead of trailing off.
Frequently asked questions
- What resolution should I record a software demo at?
- Record at or above the size it will be viewed at, since downscaling stays sharp while upscaling does not. A 1280 to 1440 pixel wide browser window suits most embedded demos. Recording on an ultra-wide monitor is the most common reason demo text ends up unreadable.
- How long should a software demo be?
- For marketing use, under a minute and focused on one flow. For a sales follow-up, match whatever you actually covered on the call. Long demos are abandoned rather than watched faster, so covering less well beats covering everything briefly.
- What should I do before recording a product demo?
- Populate the account with realistic data, remove anything private, silence OS-level notifications, close unrelated tabs, raise browser zoom to around 110 to 125 percent, and rehearse the exact click path once so you discover dead ends before recording rather than during.
Keep reading
This is what Demorta does
Click through it — the same kind of demo you can record of your own product.
Try it on your own product
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →