Video: frame inspection & motion verification

Two jobs. Both end in reading PNG frames as images — the only way to judge how motion actually looks (jank, easing, flashes, layout shift, banding). A screenshot proves a final state; getComputedStyle proves the mechanism is wired. Neither shows what an animation looks like. Frames do.

1. Analyze any video — a clip the user hands you, a screen recording, an observed capture. Extract frames, inspect. No self-capture needed.
2. Capture → extract → verify loop — drive a UI interaction, record video, extract frames, look. This is the global Testing rule: verify animations/transitions/motion by recording video, not by static checks.

When to use