A website walkthrough answers the question your visitor arrives with
A new visitor signs in to your web app. A sidebar. 12 menu items. An empty dashboard. Where do they click first?
A museum audio guide doesn't describe the whole building. It tells you which room to walk into next. A website walkthrough video does that job for your product: it walks one buyer from the first screen to the result they came for.
But visitors don't all arrive with the same question. Where do I start? What will this do for my work? How does it actually work? Is it built for someone like me?
The short answer: the website walkthrough videos that work answer one visitor question at a time. Signpost answers “where do I start?” by naming every click. Through Line answers “what will it do for me?” by following one piece of work from input to result. Cross Section answers “how does it work?” by opening the product up. Role Lens answers “is it for me?” by walking the product from one viewer's seat. The 19 guided walkthroughs below are sorted by the question they answer.
Planning a website walkthrough?
Talk to the Advids team about style, budget and timeline before you record a single screen. Start with the one question your visitor arrives with.
A trail map is useless without the signs on the path. Your product's menu is that map. New visitors need the signs: go here, click this, type that.
I call it the Signpost: each step of the walkthrough names a place and a verb, so the viewer could repeat it from memory. Five examples.
Microsoft Security Copilot agent walkthrough
Microsoft's walkthrough shows security teams how to build a custom Security Copilot agent with no coding. Every step names where to go, starting with “Head to Build.”
What works here:
The first instruction is a place. “Head to Build” tells the viewer where to begin in the Security Copilot portal.
Each step has a verb: type the request, fine-tune it, test it, review it in the activity map, publish it. You could follow along live.
A second route serves developers: enable the Sentinel MCP server and build in your own dev environment. Two paths, each named once.
The move: Write your walkthrough as a list of places and verbs. If a viewer can't repeat the clicks from memory, a signpost is missing.
Google Cloud Gemini Cloud Assist walkthrough
Google Cloud walks through Gemini Cloud Assist one problem at a time: design, an outage, a query and rising costs. Each problem gets its own destination in the console.
What works here:
Problems work as signposts. “Key services down?” leads to Cloud Hub. Rising cloud cost leads to Cloud Hub and the FinOps hub.
The shortcut is spelled out: press Option plus G, or click the Gemini button. Nobody has to hunt for the chat window.
It names the services it already sits inside, such as Cloud Observability and Database Center. There's nothing new to find.
The move: Label each part of your walkthrough with the question a user arrives with. Then show the one screen that answers it.
Freshdesk Email AI Agent walkthrough
Freshdesk's walkthrough builds one Email AI Agent in the AI Agent Studio. It opens on the cost first: thousands of repetitive emails that slow a support team down.
What works here:
Setup runs in order: name, language, avatar, knowledge sources, tone, then handover rules. Nothing appears out of sequence.
Knowledge sources include website URLs, files, solution articles and guided Q&As. The viewer sees content they already have put to work.
A built-in simulator comes before go-live. The agent is tested on real customer scenarios, then deployed with a single click.
The move: Show the test step before the launch step. If your walkthrough jumps from setup straight to live, the viewer is left wondering what breaks.
Immigration New Zealand online visa walkthrough
Immigration New Zealand's animation walks applicants through applying for a visa online. The promise is in the title: save time and money.
What works here:
The steps are few and plain: apply online, upload your documents, get an e-Visa.
“From anywhere, anytime” answers the first worry of an applicant who lives far from an office.
It's a public service, not software for sale. It's here for one technique: making an online form feel short before anyone opens it.
The move: Show your sign-up flow as 3 steps on screen. If it really takes more, show the first 3 and say what happens next.
Thinfinity Workspace browser walkthrough
Thinfinity Workspace runs remote applications inside a browser. The walkthrough's whole starting point is one action: click a URL.
What works here:
The first step is the whole setup. “Users click a URL and get straight to work,” with no local installs.
One number backs the speed claim: sub 100 milliseconds latency for office apps.
The device list is concrete: PC, Mac, tablet or thin client. An IT buyer can check it against their own fleet.
The move: If your product starts in a browser, make the URL step one. Then show real work happening in the very next shot.
Walkthrough 2 · Through Line
“What will it do for my work?” Follow one piece of work from input to result.
Once they know where to start, the next question arrives. What comes out the other end?
A parcel tracker doesn't show the whole depot. It follows one parcel to your door. I call it the Through Line: one input your buyer already has, followed until it becomes a result. Six examples.
Mural AI features walkthrough
Mural's walkthrough shows its new AI features working on real team work. Raw client notes go in. Clustered insights, sprint ideas and an alignment map come out.
What works here:
It starts with messy input: unstructured client notes. Mural AI summarizes and clusters them into key insights.
Then the work moves on. AI expands ideas for a sprint and organizes them into mind maps and tasks.
It ends with people, not output. A “What's on Your Radar?” diagram maps each stakeholder's priorities.
The move: Pick one messy input your buyer already has and follow it to a finished output. If the input looks staged, use a messier one.
Strolid AI for automotive walkthrough
Strolid's video, titled “Meet Sophia Outbound AI Bot,” shows AI built for car dealerships. It turns customer conversations into a short summary of what each customer needs.
What works here:
The input is the dealer's own pile: customer conversations spread across different formats.
The output is short. Each customer's needs and concerns are pulled out and summarized.
The handoff is named. The summary lands with dealership staff, ready to use.
The move: End the walkthrough on the screen your buyer's team reads next. If nobody acts on your last frame, it's the wrong last frame.
Dynamo Software investor portal walkthrough
Dynamo Software's walkthrough moves investor reporting from piles of paper into the Dynamo Investor Portal. The before and the after sit side by side.
What works here:
The before is physical: a desk covered in paper. The after is a portal on desktop and mobile.
The work keeps moving. Documents go out, then investors open performance summaries and transaction data on their own.
Setup gets a scene too. Firms edit or build workspaces from a drag-and-drop content library, in their own brand colors.
The move: Give the old way one shot before the walkthrough starts. Then keep every other shot inside your product.
Zoho Creator AI walkthrough
Zoho Creator's walkthrough follows one app from a typed description to deployment. Zia, Zoho's assistant, helps at each step.
What works here:
It opens on the builder's pressure. Requirements evolve. Timelines shift.
The path is one line: describe the app, refine it, automate it, connect it, brand it, deploy it.
The app's own users get a scene. A theme gallery and portal customization show what they'll see on phones and tablets.
The move: Name the start and the end of your walkthrough in one phrase, like Zoho's “Idea to deployment.” Cut any scene that sits outside that line.
Miro Flows walkthrough
Miro's walkthrough introduces Flows, visual AI workflows that start from what's already on a team's board. In Miro's words, “Your canvas becomes the prompt.”
What works here:
Nothing starts from scratch. Board content turns into next steps: prototypes, diagrams and tables.
Every step stays visible. “Jump in, tweak, redirect” keeps the person in charge of the AI.
It closes on two ways in: ready-made flows, or flows built for your team.
The move: If your product uses AI, show the moment a person changes the AI's work. That's the step a careful buyer looks for.
Splunk Federated Search walkthrough
Splunk's walkthrough shows Federated Search for Amazon S3. It starts with scattered data and ends with one search across Splunk Cloud Platform, Splunk Enterprise and S3.
What works here:
The problem is drawn first: different data types and storage policies, kept in different places.
Setup is shown step by step: federated providers first, then indexes.
The payoff is one keyword. “sdselect” runs the search across sources without extra data ingestion.
The move: End on the one command or button your user will repeat every day. That's what they'll remember from the walkthrough.
Walkthrough 3 · Cross Section
“How does it work?” Open the product up and show the inside.
Results raise a harder question. What's happening between the input and the output?
A car showroom puts a cutaway engine on the floor for exactly this buyer. Infrastructure and security buyers ask the same thing about your product. I call it the Cross Section: one view that shows the inside working. Four examples.
Shufti address verification walkthrough
Shufti's walkthrough opens up address verification. It starts with synthetic identity fraud that begins with a fake address, then shows what happens to an address between upload and answer.
What works here:
The document gets taken apart on screen. Street, city and postcode are each matched on their own.
The routing is a decision. Shufti tries docless checks against national eID databases first, then falls back to a document.
The coverage is concrete: 10,000-plus document types in 95-plus languages.
The move: If your product makes a decision, draw it as a fork on screen. Then show what happens when the first branch fails.
BLUETTI EP900 energy system video
BLUETTI's EP900 video isn't a website walkthrough. It's a whole-house battery. It's here for one technique: drawing energy flow as colored lines the viewer can follow.
What works here:
Blue and orange lines carry solar power from the panels to every appliance, with live wattage on screen.
Hard moments get their own scene: a blackout handled by on/off-grid switching under 10ms, and self-heating batteries for winter.
An app screen closes the loop, showing when to charge, when to discharge and when to sell surplus energy back.
The move: If your product moves something invisible, like data or money, give it a color and a line. Then follow the line on screen.
OSHIMA fabric spreading machine walkthrough
OSHIMA's video walks through its KP-Series fabric spreading machine, inside and out. It's industrial, but its touch control screen gets a scene of its own.
What works here:
3D animation opens the machine and shows its internal parts handling fabric with no tension.
The PLC touch control system is shown on screen, with network integration, so the operator's view is part of the story.
It ends on the output: fabric unwound, layered and stacked evenly.
The move: Pair each screen in your walkthrough with the change it makes in the real world. A setting means more when the viewer sees its effect. For more machines shown this way, see these 3D industrial walkthrough videos.
BlueSword Kangaroo Robot walkthrough
BlueSword's video shows a warehouse robot, not a web product. It's here because it walks one physical workflow in full, from stack to station.
What works here:
No racks. Cases stack straight up to 11 layers, and the robot picks from the stack.
The specs appear while the robot works: 1,000mm aisles at 1.5 m/s, up to 10 totes per trip and a 30 kg payload.
It ends at the handoff: docking with conveyors, picking stations or stacking machines.
The move: Put each spec on screen at the moment the product does the thing it measures. A number next to its action needs no explaining.
Walkthrough 4 · Role Lens
“Is it for me?” Walk the product from one viewer's seat.
The last question is personal. Is this built for someone like me?
A theater's seat map shows the view from your seat, not the whole hall. Your buyer wants the same view of your product. I call it the Role Lens: one viewer's job, named up front, with the walkthrough seen through their eyes. Four examples.
Wix Studio agency walkthrough
Wix Studio's walkthrough is made for one viewer: the agency building websites for clients. Each step follows an agency project from kickoff to handover.
What works here:
The audience is in the title: “The ultimate design experience for agencies.”
The steps match an agency's project: kick it off, design the layout, manage content, make it responsive with AI.
It ends where agency work ends: “from draft to client handover.”
The move: Name your viewer's role in the title, then end on the moment their job ends. If the last frame belongs to a different role, recut it.
ProductPlan strategy walkthrough
ProductPlan's walkthrough speaks to product teams and gives them three reasons in under a minute.
What works here:
The first line names the viewer: a product team looking for a tool to communicate and execute strategy.
A count holds it together: “a standout for three reasons.” Ease of use, views for stakeholders and a Customer Success team.
Time is a number: boardroom-ready roadmaps in as little as 30 days.
The move: Open with your viewer's job in a question. Then promise a number of reasons and keep the count.
Oraichain Wallet walkthrough
Oraichain's walkthrough introduces its wallet to crypto users. It moves from what a first-day user needs to what a regular user wants.
What works here:
Basics first: create or import a wallet, check balances, send tokens with a QR code.
Then the ecosystem: NFTs through the aiRight webview, and staking to the Mainnet for rewards.
Small comforts last: contact management and one-click Dark Mode.
The move: Order your walkthrough by user experience: first-day tasks, then weekly tasks. A new user can stop after the part they need.
Uber and NO MORE safety walkthrough
Uber's animation is a safety guide made with NO MORE in Australia, not a product walkthrough. It's here for one technique: giving each viewer the action that fits their role.
What works here:
It defines the line first. Uber's Community Guidelines spell out misconduct, from inappropriate staring to sexual comments.
The app is part of the answer. The video shows how to report an incident inside the Uber app.
Bystanders get their own steps: disrupt the situation, check on the person affected, and call 000 for violent threats.
The move: If more than one role watches your walkthrough, give each role its own step. Name the role before the step.
Pick your walkthrough
Which walkthrough does your visitor need?
The short answer: ask one question. What does your visitor want to know right now: where to start, what they'll get, how it works or whether it's for them? The answer picks the walkthrough. One question per video. If two questions are loud, make two short walkthroughs instead of one long one.
Now go back to the visitor staring at 12 menu items and an empty dashboard. A tour of all 12 answers none of their questions. One walkthrough that answers the right one gets the next click.
The move: open your product analytics, find the screen where new visitors stall, and write down the question they'd ask there. Build your next walkthrough around that one question.
A menu shows what you built. A walkthrough shows them where to go.
FAQ
Website Walkthrough Video Examples FAQ
What is a website walkthrough video?
A website walkthrough video is a short guided video that takes a visitor through a web product, step by step, from the first screen to a result. The best ones answer one visitor question at a time: where to start, what it does, how it works or who it's for. Microsoft's Security Copilot walkthrough, for example, starts with “Head to Build.”
How long should a website walkthrough video be?
The most common length on this page is 1 to 2 minutes: 9 of the 19. Four run under a minute, like Thinfinity at 0:49. Six run past 2 minutes, mostly setup walkthroughs like Freshdesk's at 2:16. Let the number of steps set the length, then cut every step that doesn't answer the visitor's question.
What's the difference between a website walkthrough and a website overview video?
An overview sums up what a product is and why it matters, usually in one pass. A walkthrough takes the visitor through it step by step, the way they'd use it. For the overview format, see these website overview videos.
What's the difference between a website walkthrough and a product tour?
A product tour video shows the main rooms of a product to prove it's worth a look. A walkthrough follows one path through it, click by click, so the viewer can repeat it. Tours suit first visits. Walkthroughs suit sign-ups, setup and first use.
Should a website walkthrough use a screen recording or animation?
Use a clean screen recording when the viewer needs to repeat the exact clicks. Use animation when the screen is cluttered or the important part is invisible, like Shufti's routing between checks. Many product screencast videos mix both.
What should a website walkthrough show first?
The place the viewer starts. Microsoft opens its steps with “Head to Build.” Thinfinity's first step is “click a URL.” If your visitor doesn't feel the problem yet, give it one short scene first, the way Freshdesk opens on repetitive support emails.
How many steps should a website walkthrough show?
Only the steps on one path. Freshdesk's walkthrough runs name, language, avatar, knowledge, tone, handover, test and deploy, and every step belongs to building one agent. If a step belongs to a different job, it belongs in a different walkthrough.
How do you walk through an AI feature?
Show what the user types, what the AI builds, and where the person steps back in. Microsoft shows a typed request turning into an agent, then testing before publishing. Miro shows “Jump in, tweak, redirect.” The human step is what makes the AI believable.
How do you walk through a product people can't see working?
Open it up. Shufti splits an address into street, city and postcode on screen, then shows the fallback from docless checks to a document. BLUETTI draws energy as colored lines. Give the invisible part a shape, then follow it.
How do you make one walkthrough work for different roles?
Name the role before each step. Uber's safety video gives riders a reporting step and bystanders their own steps. If the roles need different paths, cut one short walkthrough per role instead of one long video.
Should a website walkthrough video use a voiceover?
Usually, yes. A voiceover can name the place and the verb while the screen shows the click, which is how Google Cloud spells out “press Option plus G.” Add captions as well, so the walkthrough still works with the sound off.
How do you measure whether a website walkthrough works?
Pick the goal before the metrics: sign-ups, setup completed or fewer support tickets. Then watch where viewers drop off in the video and compare it with where visitors stall in the product. The two drop-offs often point at the same missing signpost.
What call to action should a website walkthrough end on?
The next step on the same path. A setup walkthrough ends on going live, like Freshdesk's one-click deploy. A first-use walkthrough ends on the first task. Make it one clear call to action, not three.
Patterns from the analysis
Website Walkthrough Video Best Practices
Nine of the walkthroughs above were broken down from their full transcripts: Microsoft Security Copilot, Google Cloud, Freshdesk, Thinfinity, Zoho Creator, Miro, Shufti, Wix Studio and ProductPlan. Five patterns showed up. Nine is a small sample, so read each count as what these nine did, not as market data.
Named Place
Should a website walkthrough name where to click?
Observation
Microsoft says “Head to Build.” Google Cloud says “Head over to Cloud Hub” and “press Option plus G.” Freshdesk starts “from the AI Agent studio.” Thinfinity says “click a URL.” The other five describe features without naming a place.
Data
4 of 9 named the exact place or click where a step happens.
The move
Say where each step happens, out loud and on screen. A feature without a location is a promise. A feature with one is an instruction.
Problem First
Should a website walkthrough open on the problem?
Observation
Google Cloud opens on cloud management “getting complicated.” Freshdesk opens on repetitive emails. Zoho Creator opens on “the clock is ticking.” Shufti opens on fraud that starts with a fake address. ProductPlan opens on a question to product teams. Microsoft, Thinfinity, Miro and Wix Studio open on the product.
Data
4 of 9 opened on a problem. 1 opened on a question to its buyer. 4 opened on the product.
The move
If the visitor already has the problem, open on the first click. If they don't feel it yet, give the problem one scene, then start walking.
Plain Request
Should a walkthrough show what the user types?
Observation
Microsoft has the user type a request in natural language. Google Cloud says “Describe your application needs in natural language.” Zoho Creator says “Simply describe your requirements.” Miro uses the board itself as the prompt.
Data
3 of 9 started a task with a typed request in plain language. 1 more used existing work as the input.
The move
If your product takes plain-language input, show the exact words a user types. The viewer judges ease from the request, not the result.
Test Step
Should a website walkthrough show a test before launch?
Observation
Microsoft has the user test the agent, tune it with autotune and debug it in the activity map before publishing. Freshdesk runs a built-in simulator on real customer scenarios before go-live. The other seven go from setup to result.
Data
2 of 9 showed a test step before going live.
The move
For anything that acts on its own, like an agent or an automation, show the test. It answers “what if it gets it wrong?” before anyone asks.
Finish Line
Where should a website walkthrough end?
Observation
Wix Studio ends on “client handover.” Zoho Creator ends on deployment. Microsoft ends on “Publish it.” Freshdesk ends on deploying with a single click. The other five end on a slogan or a link.
Data
4 of 9 ended on the moment the work goes live or leaves the product.
The move
End on the moment the viewer's work is done: published, shipped or handed over. That's the frame they picture when they decide to try it.
How to plan
Where to use your website walkthrough video
Put the walkthrough where the question gets asked. That one rule decides most placements.
Sign-up and first login. A Signpost walkthrough shows the first 3 clicks before the visitor has to find them. It pairs well with user onboarding flows already in your product.
Feature and pricing pages. A Through Line walkthrough shows what a visitor gets out, not just what they put in.
Help docs. Short walkthroughs that answer a setup question before a support ticket does. They sit naturally beside your software onboarding videos.
Role pages. One Role Lens walkthrough per role, so each visitor sees their own path.
The homepage. Keep it short there, closer to a website tour video, and link to the full walkthrough.
The move: list the 3 pages where visitors stall or open support chats. Each one needs a walkthrough before it needs a redesign.
How do you script a website walkthrough video?
Eight decisions, in order. Each one narrows the next.
Question. The one thing the visitor wants to know. It picks Signpost, Through Line, Cross Section or Role Lens.
Viewer. Name the role. A developer and an admin don't need the same path.
Path. One start point and one finish line. Everything outside that path gets cut.
Steps. Write each one as a place and a verb: “Head to Build.” “Type your request.”
Script. Write the last line first. Then the first line. Then the middle.
Screens. Real screens where the viewer must repeat the clicks. Animation where the screen can't show the idea.
Test. If the product acts on its own, show it being checked before it goes live.
Ask. Decide the next step before you record, so the walkthrough builds to it.
Then read the steps against website usability basics. If a step is hard to say, it's often hard to click.
Jai Ghosh is a Video Producer at Advids, where he has planned and produced videos for B2B software and technology companies for 7 years. He works on product demos, explainer videos and brand videos, from the first script to the final cut, for clients from startups to enterprises.
Before Advids, Jai spent over 11 years in freelance media consulting, after starting out in digital journalism. He writes the Advids blog's breakdowns of product and demo videos, sorting real examples by the question each one answers for a buyer.
Focus: SaaS product demos, explainer videos and brand videos
Experience: 7 years at Advids, over 11 years in media consulting
