Sampling

How many values per animation, how many frames per checkpoint, and how long a window may be.

On this page
  1. Samples
  2. Frames
  3. Concurrency
OptionDefaultDescription
capture.samples24Property samples per animation across its active duration (2–240)
capture.frames.enabledtrueRender a filmstrip per checkpoint
capture.frames.fps30Filmstrip frame rate (1–120)
capture.frames.maxFrames90Per checkpoint; the interval grows for long windows
capture.frames.format"png"png (lossless, enables frame divergence) or jpeg
capture.frames.quality80JPEG quality
capture.maxWindow5000Longest motion window replayed per checkpoint (ms)
capture.waitForAnimationsTimeout10000Upper bound for waiting until motion settles (ms)
capture.settleTime120Quiet period with no running or newly started animation (ms)
capture.navigationTimeout30000Page navigation timeout (ms)
capture.actionTimeout10000Default timeout for clicks, hovers, fills (ms)
capture.scenarioTimeout120000Whole-scenario timeout (ms)
capture.waitForNetworkIdletrueWait for the network to go quiet after navigation (warns on timeout)
capture.networkIdleTimeout5000Bound for network idle, fonts and images (ms)
capture.waitForFontstrueWait for document.fonts.ready; report failed faces
capture.waitForImagestrueWait for non-lazy images
capture.concurrency1Scenarios captured in parallel (separate contexts, one browser)

Samples

Samples are taken at evenly spaced times across each animation's active duration during replay. Each one holds computed values of the animated properties, the decomposed transform (translateX/Y/Z, scaleX/Y, rotate, skewX), opacity and the border box. They drive the trajectory, opacity and size comparisons and the inspector's value charts. Raise the count for long or complex animations whose path matters between the endpoints. Easing curves always use their own 65 samples, independent of this setting.

Baseline and candidate should use the same count: otherwise path comparisons fall back to endpoints and the comparison says so (SAMPLE_COUNT_DIFFERS).

Frames

Frames are rendered deterministically during replay, not recorded in real time. A window longer than maxFrames / fps seconds (3 s by default) gets a larger interval between frames, so a checkpoint never stores more than maxFrames. Frames are content-addressed: a frame in which nothing moved is stored once.

To make captures smallerCost
Lower frames.fps or frames.maxFramesCoarser filmstrips
frames.format: "jpeg"No frame divergence (it needs lossless PNG)
{ type: "capture", label, frames: false }No filmstrip for that checkpoint
{ type: "capture", label, screenshot: false }No visual comparison for that checkpoint

Concurrency

capture.concurrency runs scenarios in parallel contexts of one browser. Replay is deterministic, but start times and latency are observed live, and a loaded machine can make them noisier. Keep 1 for baselines on slow CI runners.