Screen Browser
Documentation

Getting started

From a plan to the first video in about ten minutes, in the app.

The whole loop in 2 minutes and 13 seconds: connect an app, paste a few sentences, check, generate. Screen Browser recording itself; the guide behind it.

What you need

  • A web app we can reach over HTTPS, on port 443 (the default), 80, 3000, 8000, 8080 or 8443, and a demo user that signs in with email and password only: no OAuth, no two-factor codes, no captcha, no new-device emails. Give it realistic data to show.
  • A plan. There is no free plan; pick one on the pricing page and the button takes you to registration for that plan.

1. Create the project

Click New project. The wizard asks for:

  1. The app: its name, the URL the walkthrough starts from and the language its screens are in (the videos are narrated in it).
  2. The login gate: what proves the login worked. Either a URL fragment that only appears after signing in (/dashboard) or text only a signed-in user sees ("Sign out", your name). Single-page apps often land on the last page you visited, so prefer the text for those.
  3. The demo user's credentials. They are stored encrypted and only ever typed inside the browser.
  4. An attestation that you are allowed to record this app: you own it, a client authorised you, or it is an internal tool.

The wizard then signs in once, without recording, to prove the gate works.

2. Write the first guide

Paste ten to twenty-five steps, one per line, or let your coding agent write the guide from your source code (see For coding agents). Name things the way a person sees them:

Go to https://app.acme.com/projects
[CAPTION "Let's create your first project."]
Click the button named "New project"
Type "Spring launch" into the field labelled "Name"
Click the button named "Create"
Confirm text "Spring launch" is visible

Add a quoted sentence every one to three steps: that becomes the narration and the captions. The guide syntax page has every form a line can take.

3. Check first

Check first (also the 🔍 button on every guide later) walks the guide in your real app without recording. It is free and shows a screenshot after every step and how each target was found. It does perform the steps, so a guide that creates a record creates one.

4. Record

Record signs in, records, narrates, adds the effects and merges the video. A typical two-minute guide takes three to five minutes. The run page shows progress and, when it is done, the video and what it cost. If a step fails, the run stops there, the page names the line, and nothing is charged.

5. Narration and output

The project's Voice tab sets the language and the voice (with a sample to play for each); its Video tab sets the quality (1080p or 4K), the device and whether subtitles are shown in the picture. A single video can use a different voice and device from the dropdowns next to Generate. See Voices and languages.