Capturing Multiple Pages

One command, many URLs#

capture accepts one or more URLs:

npx rollberry capture \
  https://example.com \
  https://example.com/pricing \
  https://example.com/contact \
  --out ./artifacts/site-tour.mp4

Rollberry visits each page in order and produces a single output video.

Add a hold between pages#

Use --page-gap to hold the last frame of each page before the next one starts:

npx rollberry capture \
  https://example.com \
  https://example.com/pricing \
  --page-gap 1.5 \
  --out ./artifacts/tour.mp4

This is useful when viewers need a beat to absorb a section before the next page begins.

Best use cases for multi-page capture#

• homepage to pricing to contact walkthroughs
• simple release previews across a few routes
• fast visual recordings when no interaction is needed

When capture stops being enough#

Switch to render when you need:

• named scenes
• clicks, typing, hover states, or key presses
• custom pauses inside a single page
• desktop and mobile outputs from one definition
• audio, subtitles, or transitions

Keep outputs explicit#

Use a real path for the resulting video so the sidecars land where you expect:

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

That produces:

• ./artifacts/about-tour.mp4
• ./artifacts/about-tour.manifest.json
• ./artifacts/about-tour.log.jsonl

Next step#

Move to Project Rendering once page order is not enough and you need a real scene graph.