Output Artifacts

Capture artifacts#

If you run:

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

Rollberry writes:

artifacts/
├── demo.mp4
├── demo.manifest.json
└── demo.log.jsonl

The sidecar paths are derived from the output path unless you override them with --manifest and --log-file.

Capture manifest#

Current capture manifests use schemaVersion: 2.

Typical top-level areas:

• status
• startedAt and finishedAt
• environment
• options
• artifacts
• result
• warnings
• error

Example:

{
  "schemaVersion": 2,
  "status": "succeeded",
  "options": {
    "urls": ["https://example.com/"],
    "viewport": { "width": 1440, "height": 900 },
    "fps": 60,
    "duration": "auto",
    "motion": "ease-in-out-sine",
    "waitFor": { "kind": "load" },
    "hideSelectors": [],
    "pageGapSeconds": 0
  },
  "artifacts": {
    "videoPath": "/abs/path/demo.mp4",
    "manifestPath": "/abs/path/demo.manifest.json",
    "logFilePath": "/abs/path/demo.log.jsonl",
    "videoCreated": true
  }
}

Render artifacts#

For project rendering, each named output writes its own video and sidecars. Rollberry also writes a project-level summary manifest.

Example output layout:

artifacts/
├── demo-desktop.mp4
├── demo-desktop.manifest.json
├── demo-desktop.log.jsonl
├── demo-mobile.webm
├── demo-mobile.manifest.json
├── demo-mobile.log.jsonl
└── demo.render-summary.json

Render manifests#

Current render manifests use:

• schemaVersion: 1
• kind: "render"

They include:

• project metadata
• output metadata
• serialized scene definitions
• capture metrics and composed artifact metrics
• warnings and errors

Render summary manifests use:

• schemaVersion: 1
• kind: "render-summary"

They provide one row per named output with status, paths, warnings, and errors.

Debug frames#

Debug frames are optional and are written only when:

• --debug-frames-dir is used for capture
• debugFramesDir is set for a render output

They are stored as numbered PNG files and can consume substantial disk space on long or high-FPS runs.

Overwrite behavior#

Rollberry does not silently replace existing outputs. Use --force when the target paths already exist.