Make a free video

How to Create an Interactive Product Demo (2026)

Create an interactive product demo step by step: plan the flow, record clean, pick a method, write step copy, place hotspots, add a call to action, embed, measure.

By Bibin Mathew, founder of Nook · Published · 11 min read

An interactive product demo lets someone click through your product without signing up, installing anything or booking a call. They see a real screen, a marker that says "click here", and a short line of text. They click, the next screen appears, and a minute later they have seen the workflow that matters.

This guide shows you how to build one: planning, recording, three ways to build it, step text, hotspots, the ending, embedding and measuring. Most of it is tool-agnostic. You can follow every step without using our product.

Short answer

To create an interactive product demo, pick one workflow with one outcome, record it cleanly in a tidy account, and turn each click into a step: a screenshot, a hotspot on the control to click and one or two lines of text. Keep it to roughly 5 to 15 steps, end on the result with one clear call to action, embed it where people already look, and watch where viewers drop off.

What an interactive demo is

An interactive demo, also called a click-through demo or interactive product tour, is a sequence of captured screens that the viewer moves through by clicking. Each screen usually has three parts:

  • The screen itself, captured from your real product.
  • A hotspot, a marker on the element the viewer should click next.
  • A text card, a heading and a sentence or two explaining the step.

The viewer controls the pace. Nothing is live, so the demo cannot break and does not touch a real account.

That is the main difference from a demo video, which plays at your pace with your voice. If you are still deciding between the two, read interactive demo vs video.

Where interactive demos are used

  • On your website. A "see it in action" demo on the homepage, a product page or a pricing page lets visitors try before signing up. It works well for products with a signup wall or a long setup.
  • Sales follow-up. After a call, send a link to the exact workflow you discussed. The buyer can click through it again and forward it to colleagues who were not on the call. More on that in sales demo videos.
  • Onboarding. Show a new user the first task before they face an empty account. A short demo in a welcome email or an empty state can replace a long checklist.
  • Docs and help centers. Embed a click-through next to a how-to article so readers can follow along. It suits tasks with several screens, like connecting an integration or setting permissions.

Plan the flow before you record

Most weak demos are weak because they try to show everything. Plan first.

  1. Pick one job. "Create an invoice and send it" is a demo. "Our whole billing module" is a tour nobody finishes.
  2. Write down the outcome. What does the viewer see on the last screen? A sent invoice, a published page, a chart with real numbers. The demo should end there.
  3. List the clicks. Walk through the task and write each click as a short line. This becomes your step list.
  4. Cut what is not the point. Logins, loading screens, settings you would never change on a first visit and confirmation dialogs that add nothing. Each step should move the story forward.
  5. Aim for 5 to 15 steps. This is a rule of thumb, not a law. Short enough to finish, long enough to reach the result. If you need more, split it into two demos.

Record clean

Every builder works from captures of your screen, so the capture quality sets the ceiling.

  • Use a demo account with realistic data. Empty tables and "test test 123" make the product look unused. Use believable names, numbers and dates.
  • Remove private data before you record. Real customer names, emails, phone numbers, invoices and API keys have no place in a public demo. Use fake data where you can and check every screenshot anyway.
  • Tidy the screen. Close unrelated tabs, hide the bookmarks bar, turn off notifications and dismiss banners and cookie prompts.
  • Pick a sensible window size. Very wide screens shrink badly when embedded. A laptop-sized browser window with readable text works better than a full 4K desktop.
  • Click slowly and deliberately. Pause a moment before each click and let pages finish loading. Rushed clicks produce half-loaded screens.

For more general recording advice, see demo video best practices. Most of it applies to demos too.

Three ways to build it

Method 1: Screenshots and hotspots by hand

This works with almost any slide or prototyping tool, or a basic screenshot-based demo builder.

  1. Take a screenshot at each step, just before the click.
  2. Put the screenshots in order, one per slide or frame.
  3. Draw a hotspot over the element to click and link it to the next frame.
  4. Add a text card to each frame.
  5. Add a start screen and an end screen with your call to action.

It is cheap and you control every pixel. The downside is time: every UI change means retaking screenshots. It suits a single demo you will not update often.

Method 2: HTML-capture builders

A category of interactive demo software, the kind you see in our Arcade alternatives and Supademo alternatives roundups, usually works through a browser extension. You click through your product while it captures each step. Some tools capture screenshots, and some capture the page's HTML and styles so the demo looks like a live page and text can be edited after capture.

Common strengths: fast capture, editable text in captured pages, branching paths, lead forms and analytics dashboards. Common limits: they usually need their own extension in your browser while you record, HTML capture can struggle with some apps (canvas-heavy screens, desktop software, mobile apps), and paid plans are often priced per seat. Check what a specific tool supports before you commit.

Method 3: Generate it from a screen recording (Nook)

If you already have a screen recording, or prefer recording with whatever tool you use today, you can build the demo from the video. This is what we built Nook to do.

  1. Upload your recording. Any existing screen recording, up to 15 minutes on paid plans.
  2. Choose "Interactive demo" on the first create step instead of "Video".
  3. Nook finds the steps. It takes one screenshot per step, just before each click.
  4. It places each hotspot by following the mouse pointer in the recording and reading the text on screen. The hotspot is a normal arrow pointer with a faint pulsing ring, and you can pick its colour.
  5. It writes a heading and short text for each step's card. Edit any of them.
  6. Fix what it got wrong. Click "Move hotspot" and then the right spot on the screen, or mark a step as "no click" when it is just there to explain a screen.
  7. Add a call to action if you want: a button label and a URL, shown on the end screen or kept on screen the whole time. Button clicks are counted.
  8. Share the link or copy the embed code.

Viewers click the pointer or Next, go Back, or use the arrow keys. There is a start card and an end screen.

The honest limits: Nook does not record your screen, so you need a recording first. Demos have no voice. Hotspot placement depends on how clearly the pointer and the click show in the recording, so check every step. There is no branching and no lead form inside the demo, and the screens are screenshots, not captured HTML, so text on the screen itself cannot be edited. The free plan covers one video or demo up to 3 minutes with a "Made with Nook" badge, and paid plans start at $9 a month. See pricing.

By handHTML-capture builderFrom a recording (Nook)
How you captureScreenshotsTheir extension while you clickAny screen recording you upload
Hotspot placementYou draw each oneCaptured from your clicksFrom the pointer in the video, editable
Step textYou write itYou write it, some draft itDrafted per step, editable
Edit text on the screenNoOften yesNo
Branching and formsDepends on toolOftenNo
Best forOne small demoMarketing teams with many web-app demosTeams that already record their screen

Write the step text

The text card does most of the explaining, so treat it like copy, not a caption.

  • Lead with the action or the benefit. "Pick a template" beats "This is the template gallery."
  • One idea per step. A heading of a few words and one or two short sentences.
  • Say why, not only what. "Turn on reminders so late invoices chase themselves" gives a reason to care.
  • Use the words on the screen. If the button says "Publish", write "Publish".
  • Make the first card about the outcome. "See how to send your first invoice in under a minute" tells the viewer why they should start.

Our demo video script guide covers structure in more depth. The same beginning, middle and end works for demos.

Place hotspots well

  • Put the hotspot on the exact control. Not near it, on it. The viewer should never wonder what to click.
  • One hotspot per step. Two markers on one screen split attention.
  • Keep the text card off the target. If the card covers the button, move the card or the hotspot side.
  • Use a pointer colour that stands out on your UI. A dark pointer disappears on a dark theme.
  • Use "no click" steps sparingly. An explanation step without a click is fine to show a result or a chart, but too many turn the demo into slides.

End with one call to action

The last screen is where interest turns into a next step. Give it one clear button, not five links.

  • Match the CTA to the context. On a homepage: "Start free". In sales follow-up: "Book a call" or "Talk to us". In onboarding: "Try it in your account". In docs: "Open the settings page".
  • Show the result first. The end screen should come right after the outcome so the button feels earned.
  • Consider a persistent button for high-intent pages like pricing, where some viewers decide halfway through.

Embed and share

  • Embed it where the question is asked. A homepage section, a feature page, a help article, an onboarding email linking to the share page.
  • Size the embed for the screen. Check it on a laptop and a phone. If text becomes unreadable on mobile, consider showing a link or a short video there instead.
  • Use the share link in emails and chat. Email clients do not run embeds, so link to the demo page.

Measure what happens

Whatever tool you use, look at a few simple numbers:

  • Starts. How many people who see the demo actually begin it.
  • Completion. How many reach the last step.
  • Drop-off by step. Where people stop. A big drop at one step usually means a confusing screen, a missed hotspot or a boring stretch.
  • CTA clicks. How many click the button at the end.

Change one thing at a time, then compare. Analytics vary a lot between tools, so check what a tool reports before relying on it.

Common mistakes

  1. Showing the whole product. One workflow per demo.
  2. Starting with setup. Skip logins. Start close to the interesting part.
  3. Hotspots that miss the control. Check every one in the final embed.
  4. Text that describes the screen. Say what to do and why.
  5. Private data left in. Real emails, names and keys are easy to miss.
  6. No ending, or several CTAs. Show the result, then one button.
  7. Never updated. The demo still shows the old UI.

Checklist

AreaCheck
PlanOne workflow, one outcome, written down
PlanClick list of roughly 5 to 15 steps
RecordingDemo account, realistic data, no real customer data
RecordingClean browser, notifications off, readable window size
StepsEach step moves the story forward
TextHeading plus one or two short lines, action first
TextFirst card states the outcome
HotspotsOn the exact control, one per step, visible colour
EndingResult shown, one CTA that fits the context
PrivacyEvery screenshot checked for personal data
EmbedTested on laptop and phone
MeasureStarts, completion, drop-off and CTA clicks tracked

FAQ

What is the difference between an interactive demo and a product tour?

The terms overlap. "Interactive demo" usually means a standalone click-through of captured screens that runs outside your product, for example on your website. "Product tour" can mean the same thing, or an in-app walkthrough that highlights elements in the live product for logged-in users. This guide is about the first kind.

How many steps should an interactive demo have?

As few as it takes to reach the outcome. Roughly 5 to 15 steps is a good range for most single workflows. If you need more, split it into separate demos, each with its own result.

Can I make an interactive demo from a video I already recorded?

Yes, with tools that work from recordings. Nook takes an existing screen recording, takes a screenshot before each click, places hotspots by following the pointer and drafts the text for each step. You can then move hotspots, edit text and add a call to action.

Should an interactive demo have a voiceover?

Usually not. Viewers move at their own pace, so narration timing does not fit, and many will view it on mute anyway. Put the explanation in the step text. If voice matters for your audience, make a video as well.

Can I embed an interactive demo on my website?

Most tools give you an embed code and a share link. Embed it where visitors ask "how does it work", such as the homepage, a feature page or a help article. Check it on a phone, since dense screens can get hard to read when scaled down.

How much does interactive demo software cost?

It varies widely. Some tools have free tiers with limits, and many price per seat each month. Nook prices by the number of videos and demos, with a free demo up to 3 minutes, a one-off $4 unlock for a single video or demo, and plans from $9 a month, excluding tax.

Make your first interactive demo

You can build a good click-through demo with screenshots and patience. The planning, step text and ending matter more than the tool. If you already have a screen recording and want a draft to start from, Nook turns it into an interactive demo with hotspots, step text and a call to action you can edit, or into a narrated video from the same recording. See how it fits product demo videos, or make your first demo free.

Make your first demo video free

Upload a screen recording. Nook writes and voices the script, adds captions and writes the step-by-step guide.

Make a free video