Overview

ScreenCI treats product videos as code. Instead of editing screen recordings by hand, you describe a flow once as a Playwright-based script. ScreenCI drives your app, adds narration and camera motion, and renders a polished video. When the UI changes, you rerun the script and the video regenerates.

How it works

Record with the CLI, render in the cloud, then deliver the final video where your team needs it.

01

Capture

The ScreenCI CLI runs on your machine or in CI, capturing the product flow and uploading the raw recording plus timing data.

02

Render

ScreenCI renders that raw recording in the cloud, syncing narration, zooms, and animations to the timing data.

Only the raw recording and timing data leave your machine, never your source code, browser session, or credentials.

03

Deliver

Download the finished video and subtitles yourself, or publish them to a CDN-backed static URL that always serves the latest approved version.

The CLI runs everything that touches your app locally, so the only thing that leaves your machine is the raw recording plus timing data, not your source code. The CLI itself is open source.

Two ways to set up

Pick the path that fits how you work.

• Agent integration (recommended). Point a coding agent (Claude Code, Codex, Cursor, or similar) at the integration brief. It scaffolds ScreenCI, authors a video for the flow you describe, and records it, with you mostly reviewing the result.
• Manual setup & first video. Scaffold ScreenCI yourself, write the .screenci.ts script by hand, run it locally, and record the final video.

Either way, once a video exists you can dig into the rest of the docs to refine it: Video Script Basics, Camera and Zooming, Narration, and Public URLs and Embeds.

Community

Need support, hit a bug, or want to share what you recorded? Join the ScreenCI community on Discord to get help, report issues, and talk to other users.