Help videos that never go stale.
Stepthrough turns a help article into a narrated walkthrough video by using your product in a real browser. When your UI changes, it re-records the video from the same script. No screen recorder, no reshoots.
- Narrated videoA finished MP4, voiced and paced to the footage.
- CaptionsA WebVTT file that matches the narration.
- ChaptersChapter marks timed to the final video.
- Publish descriptionTitle, link and chapter list, ready to paste.
Every release quietly breaks your help videos.
A button moves, a page is renamed, a menu gets a new item, and every video that shows the old screen is now wrong. Fixing it means recording again, voicing again and captioning again, one video at a time.
So video help either goes out of date or never gets made. Stepthrough makes updating a video a job you can run.
Recorded by hand
- Re-recorded manually after every UI change
- No reliable way to tell which videos are out of date
- Narration re-recorded to match the new footage
- Captions and chapters redone by hand
With Stepthrough
- Re-rendered from the same script
- Guides flagged stale when an app they use changes
- Narration re-timed to the new recording
- Captions, chapters and description regenerated with every cut
From a help article to a video you never re-record
You describe the walkthrough. Stepthrough handles the rest, and every step can be run again.
- 1
Write a brief
Describe what the walkthrough should show in a sentence or two, or start from a help article you already have.
- 2
Stepthrough records a take
An agent works through your product in a real browser, narrating as it goes, and writes the walkthrough down as a script.
- 3
Get a finished cut
The recording is cut into a narrated video with captions, chapters and a description, ready to publish.
- 4
Re-render when the UI changes
When your product changes, affected guides are flagged stale. Re-render them from the same script.
Your product, used for real
Stepthrough opens your product in a real browser and works through the brief. It clicks, types and waits for pages the way a person would, and narrates each step as it goes. There's nothing to install in your product and no special mode to add.
- Starts from plain English. A brief or an existing help article is enough.
- Signs in as a persona, so the video shows the right seat and permissions.
- Invents realistic example data when a walkthrough needs a record to create or edit.
A script you can read, edit and re-run
Every take leaves a script: the chapters, scenes and narration of the walkthrough, with each step described in plain English alongside the details needed to find it on the page. The plain-English description is what lets a re-render find a button after it has moved.
- Edit visually or as YAML: drag scenes, rewrite narration, adjust steps.
- Every version kept. Compare any take's script with the one in use, and promote the one you want.
- Notes become direction. Pinned notes shape the next take.
Finished, not just recorded
A cut turns a take into a video you can publish. The narration is voiced and timed against the recording, waits are shortened, and moving to another app is marked with a transition. Every cut comes with its captions, chapters and a description to paste alongside it.
- One take, many cuts. Try a different voice or pace without recording again.
- Branded bookends. Intro title, chapter dividers and an end card with a QR code.
- Regenerated every time. Captions and chapter marks are rebuilt with every re-render.
Know exactly which videos are out of date
Every guide knows which apps its walkthrough passes through. When one of them changes, the guides that touch it are flagged stale with a one-line reason. Re-render a single guide, or every stale guide at once.
- Adapts to small changes. A re-render follows the script and handles controls that moved or were renamed.
- Nothing changes behind your back. If a walkthrough turns into a different one, the new script waits for your approval.
- Clear outcomes. Each re-render says whether the guide was verified, adapted or needs a look.
- Invite a teammateUp to date with Your productFresh
- Create your first projectUp to date with Your productFresh
- Export a monthly reportUp to date with Your productFresh
- Share a calendar inviteUp to date with Calendar appFresh
Try it: change the product and watch what happens.
The details that make a walkthrough usable
Logins, third-party tools and runs that get stuck are part of real products, and Stepthrough is designed around them.
Signs in as the right person
Each guide acts as a persona, such as an admin or a new user, so every video shows the account your customers are actually using.
Walkthroughs across tools
A guide can move between your product and the third-party tools your customers use alongside it, with a clean transition at every switch.
Review with notes
Watch a take, pin notes to the exact moments that need to change, and take it again. You decide which take becomes the guide.
A person can step in
If a run gets stuck, it pauses and sends a live link to the browser. Take control, show it the way, and it carries on.
Voices, cards and pacing
Choose a narration voice, add an intro title, chapter dividers and an end card with a QR code. Re-cut a take without recording it again.
Clean footage
Long waits are sped up, failed attempts are cut out and sign-ins never appear on screen, so the video shows only the path your customer should follow.
Your help videos, from your AI tools
Every Stepthrough workspace includes an MCP server. Connect Claude Code, Codex or any MCP client, and it can create guides, start takes, check which guides are stale and fetch finished cuts. It can do everything a person does in the app, with access you approve.
Stepthrough can also record an AI agent at work: a walkthrough can put a terminal running Claude Code or Codex next to your product and show it using your integration.
create_guidetakestale_guidesrerender_staleget_cutwrite_scriptWhat kinds of products does Stepthrough work with?
Any web application that runs in a browser, including single-page apps and pages with embedded third-party panels. Recordings run in Chromium. Native desktop and mobile apps are not supported.
How does it sign in to our product?
Each guide acts as a persona. A persona can hold a username and password that Stepthrough fills in at the start of each take, or someone on your team signs in once through a secure browser link and that session is reused, which also works for single sign-on and two-factor authentication.
Credentials are stored encrypted in your workspace, are never shown to the AI model, and sign-in screens are cut from the finished video.
Do we have to write scripts?
No. Your first take starts from a brief or a help article, and Stepthrough writes the script as it goes. You can edit any script afterwards, either in a visual editor or as YAML.
What happens when our UI changes?
Every guide records which apps its walkthrough passes through. When one of them changes, those guides are flagged stale with a one-line reason. Re-rendering follows the existing script with the live page in view, adapting to controls that moved or were renamed.
Each re-render is labelled with what happened. If the product changed so much that the walkthrough became a different one, the new script waits for a person to approve it instead of replacing the published guide.
What does a finished video include?
An MP4 (1920×1080 by default), a WebVTT caption file, chapter marks and a publish description with your link and chapter list. You can also add an intro title card, chapter dividers and an end card with a QR code.
Can we choose the narration voice?
Yes. Narration is generated with text-to-speech, and a take can be cut again with a different voice or pace without recording the product again. Supported providers include ElevenLabs, Deepgram and OpenAI-compatible speech APIs.
Where are the videos published?
Wherever your help content already lives. The output is a standard video file with captions, so it works with YouTube, Vimeo, your help centre or your learning platform.
Will recordings show our real customer data?
Recordings show whatever the persona’s account can see in the environment you point Stepthrough at. We recommend a demo or staging account. When a walkthrough needs example records, such as a teammate to invite, Stepthrough makes up realistic ones instead of using anyone’s real details.
How do we get started?
Book a demo. We set up each workspace with the team that will use it, starting with a help article you want turned into a video.
See your own help article as a video
Send us a help article you wish were a video. We'll set up a workspace and walk you through the result on your own product.
Or email hello@stepthrough.ai