How to record a product demo video

Most product demos fail for the same two reasons: they show the tour instead of the point, and they look like a raw desktop capture. Both are fixable before you press record. This is the whole run, from deciding what the demo has to prove to exporting a file you can attach to an email, and none of it involves uploading your screen to anyone.

Try it in the editor, freeNo upload · No sign-up to start · 100% private

Decide what the demo has to prove

A demo is an argument, not a feature tour. Pick the one job your viewer is trying to get done and show that job completed, start to finish. Everything that does not serve it, the settings page, the integrations list, the thing you are personally proud of, comes out. Write the beats before you record: the problem in one line, the two or three steps that solve it, and the result. Say the numbers out loud so you know how long each beat runs. Two minutes is a generous ceiling for a demo that lives on a landing page or in an inbox, and most good ones are shorter. Then set up the data you will be showing, ideally in a demo account with names and figures you are happy to have on screen forever, because a screen recording keeps whatever was on screen.

Set the capture up so you do not need a second take

Record a single window rather than a whole display when you can. It excludes your desktop, your tab strip, and everything you did not tidy up, without you having to tidy up. Then silence notifications, close the tabs you would not screenshot, and check the corners of the frame for anything you missed. Turn on the microphone if you are narrating, and system audio if the product itself makes sound, which the desktop app captures on macOS and Windows. The camera is a judgment call, and a cheap one, because Supercut records it as its own track: you can move, shrink, or delete the bubble after the take rather than committing now. Set a capture quality a step above where you will publish if you plan to zoom, and give yourself a count-in so your first sentence is not a scramble.

Record in takes, not in one perfect run

The pressure to nail a demo in one continuous pass is what makes people stiff. You do not need it. Pause when you reach the end of a beat, reset the app to where the next beat starts, and resume. The paused time is folded out of the final length, so the recording behaves as if you never stopped, and the cursor track is retimed to match so automatic zooms still land on the right moments. If you fumble a sentence, pause, take it again from the top of that beat, and cut the bad one later. The finished length comes from the recorder's own clock rather than from the container, so a paused, resumed, restarted take still reports a length you can trust when you start trimming.

Polish, then export something you can send

The take lands on the timeline already sitting on a backdrop with padding, rounded corners, and a shadow, so the first thing that usually made a demo look raw is handled. Cut the dead air, especially loading spinners and the seconds where you were finding your next word. Add zooms at the moments where a viewer needs to see a small thing, and let a zoom hold long enough to read. Then add captions, because demos get watched on mute in inboxes and Slack threads, and Supercut transcribes on your device rather than sending your audio anywhere. Decide the camera bubble question now: keep it small and out of the way, or drop it entirely. Export an mp4 for a landing page or an email, or a GIF for a doc or an issue thread. Nothing was uploaded at any point, which is what makes this workable for a product that has not shipped yet.

Step by step

  1. 1

    Script the beats and prepare the data

    Write the problem, the two or three steps that solve it, and the result. Set up a demo account with figures and names you are happy to show, since the recording keeps whatever is on screen.

  2. 2

    Set up the capture

    Pick the window rather than the whole screen, silence notifications, and close stray tabs. Turn on the microphone, add system audio if the product makes sound, and set a count-in.

  3. 3

    Record beat by beat

    Run each beat, then pause while you reset for the next one. The paused time is folded out of the final length, so pausing costs you nothing and saves you the perfect-run pressure.

  4. 4

    Trim and add zooms

    Cut loading spinners and hesitations. Add a zoom where the viewer needs to see something small, and let it hold long enough to read. On the desktop app, zooms from your cursor are already there to edit.

  5. 5

    Caption and export

    Add captions for the people watching on mute, then export an mp4 for a page or an email, or a GIF for a doc. It renders on your machine, with no watermark.

Tips

  • Show one job done end to end. A feature tour is a longer video that convinces fewer people.
  • Use a demo account with data you would be comfortable seeing on a landing page a year from now.
  • Record the window, not the display, and your tab strip and notifications never become a problem.
  • Decide the camera bubble after the take, not before. It is recorded as its own layer, so keeping it is not a commitment.
  • Export a GIF of the single best twelve seconds for docs, changelogs, and issue threads, and keep the mp4 for the page.

Do it in Supercut

Related use cases

Frequently asked questions

How long should a product demo video be?

Aim under two minutes for a demo on a landing page or in an email, and shorter if the job you are showing is simple. Length is not the goal; showing one job completed, without a tour of everything else, is.

Do I need a camera on screen for a product demo?

Not necessarily. A face helps a sales or founder demo feel personal and adds nothing to a support walkthrough. Supercut records the camera as its own track, so you can size the bubble down, hide it during zooms, or delete it after the take.

How do I record the product's own audio, not just my voice?

The desktop app captures the audio playing on your machine on both macOS and Windows. In the browser, Chrome can capture the audio of a shared tab, which covers a web app demo.

Is it safe to demo an unreleased product this way?

The recording, the editing, and the export all happen on your device, and there is no upload and no share link, so no copy of your screen exists on anyone else's server. That is the practical reason to record locally when the product has not shipped.

What should I export for a landing page versus a Slack thread?

An mp4 for a landing page, an email, or anywhere with a real player. A GIF of the best few seconds for docs, changelogs, and chat threads, where autoplay and no sound are the norm. Supercut exports both from the same timeline.