Chapters. Click one to play the video from there.
This is the whole loop, once. The video above was made the same way every other video on this site was made: a guide, a check, a run. The only unusual thing about it is the app in the browser, which is Screen Browser.
What you need
- A web app we can reach over the public internet, on the usual web ports. Staging is fine; localhost, bare IP addresses and apps behind a VPN are not.
- A demo user for it that signs in with email and password. No OAuth, no two-factor codes, no captcha on that account. Give it seeded data worth showing; the recorder shows whatever the account sees.
- A plan. There is no free plan. Registration starts from the pricing page, from $49 a month for about twenty minutes of finished video.
The video connects Chatamatic, the demo app in every example on this site. Any web app with a sign-in form works the same way: a SaaS product, an internal tool, a self-hosted admin.
1. Connect the app
Click New project. The first screen asks for four things:
- A name, which becomes the project's name in your library.
- The address the walkthrough starts from, usually the sign-in page.
- What proves the login worked: a piece of the address that only appears after signing in, such as
/dashboard, or a word only a signed-in user sees. The video uses the word "Campaigns", the menu item that appears once the demo user is in. Without a gate a run never starts recording, so a wrong password is never filmed. - An attestation that you are allowed to record the app: you own it, a client authorised you, or it is an internal tool you have authority over. You give it once per app.
The second screen takes the demo user's email and password. They are stored encrypted and are typed only inside a separate browser that is never recorded; they never appear in a video or in a run's log. In the video the password stays off camera for the same reason.
Screen Browser then signs in once, without recording, to prove the gate works. If that sign-in fails you find out here, before a guide is written. From then on the project is ready, and every guide in it becomes one video.
2. Write the guide
Click New guide. A guide can start from a help article's address, from an uploaded document, from a template, or from pasted text. The video chooses Paste text and pastes this:
Create a keyword campaign. Open Campaigns and click New campaign. Name it Free checklist
and set the keyword GUIDE. Click Create campaign. In the editor, write the reply message
with your link, set the status to Active and save.
Three sentences in the app's own words, no syntax, no selectors. Analyze doc turns them into a guide: one line per step, in the wording the app uses on screen, with a caption for the narrator where the text explained something. Lines Screen Browser had to guess are flagged, and the editor opens in review mode so you look those over before anything runs. Say Looks right and the editor is yours.
In the editor every line is a step, a caption or an effect. Click a line to change it; the target picker under a step lets you point at the exact button or field without learning any syntax. Every save is a new version, and the version history compares any two. A guide is ten to twenty-five steps; videos are capped at five minutes.
3. Check, then generate
Check guide signs in and performs every step in your app without recording a video. It is free, it takes about a minute, and the report lists every step, what the recorder found for it, and a screenshot of each. A step the recorder had to work out is marked learned, and the guide remembers the answer for the next run. A step that does not resolve is the thing to fix before spending anything. Starter plans include twenty free checks a day, Pro plans a hundred.
Generate records the walkthrough in a fresh browser, narrates it in the voice the project uses, adds the captions and effects, and renders the video. A few minutes later it is in your library. Next to the MP4 you get an animated GIF, one GIF per chapter, subtitles as VTT and SRT, a chapter list for the video's description, and a thumbnail. The run page has a download for each and a share link. A run that fails costs nothing.
What happens next
When the app changes, you do not record again by hand. You edit the line that changed and generate again; the narration, the captions and the effects are all in the guide, so the rest of the video is exactly as before. The next guide shows that in under a minute.
If you work with a coding agent, it can do all of the above from your source code: Make a demo video of your web app with Claude Code.
Do it with your app
Connect your app, paste the help page you already have, and run a free check. The first video is a few minutes away.
Ten to twenty-five plain sentences become a narrated video of your app, and stay one when the app changes.
From $49 a month. A run that fails costs nothing.