Introduction

What Rollberry is#

Rollberry is an open-source CLI and Node API for turning web pages into launch-ready videos with a real Chromium browser and FFmpeg.

It supports two primary workflows:

• npx rollberry capture for one-off URLs or multi-page stitched captures
• npx rollberry render for project JSON files with scenes, actions, timelines, and multiple outputs

Both workflows write machine-readable sidecars so you can automate around the result, not just watch the video.

Capture vs render#

Use capture when you want a direct CLI entry point:

npx rollberry capture https://example.com --out ./artifacts/example.mp4

Use render when you want repeatable scene orchestration:

npx rollberry render ./rollberry.project.json

That project file can define:

• scene URLs
• setup actions such as click, hover, type, and press
• timeline segments such as scroll, pause, and mid-capture actions
• multiple named outputs such as desktop MP4 and mobile WebM

What you get from each run#

For a capture output like ./artifacts/example.mp4, Rollberry writes:

• example.mp4
• example.manifest.json
• example.log.jsonl

For project renders, each output gets its own video, manifest, and log file, and Rollberry also writes a project-level *.render-summary.json.

Why teams use it#

• Real browser capture via Playwright-backed Chromium
• Localhost support with retry behavior and localhost HTTPS tolerance
• Repeatable scene automation from JSON instead of ad-hoc screen recording
• Structured artifacts for CI, QA evidence, approvals, and release workflows
• A Node API for integrating the same pipeline into custom tooling

Current requirements#

Rollberry's current implementation expects:

• Node.js 24.12.0 or later
• ffmpeg on your PATH

Chromium is installed automatically on first run when Playwright does not find it locally.

Next steps#

• Start with Installation
• Follow the Quick Start
• Jump to Project Rendering if you want repeatable multi-output videos