Productivity
Stop scrubbing screen recordings: get the real numbers behind any animation
Frame-stepping a screen recording to guess durations and easing wastes hours. Capture the animation instead and read its real keyframes, delays and curves.
You see a menu on a site you admire. It opens with a lovely little overshoot and the items arrive one after another. You want that feel in your product, so you open a screen recorder, capture it, and start stepping frame by frame. Was that 300 ms or 400? Is the curve ease-out or something custom? How far apart are the items?
An hour later you have a guess. It feels close, but not quite right, and you cannot say why.
Why guessing from video never quite works
A recording shows you pixels, not intent. It cannot tell you:
- The easing curve. Two animations with the same duration can feel completely different because of their curve. A precise
cubic-bezier()and a plainease-outlook similar in a few frames and feel different in the hand. - The delays. A stagger is a list of delays. At 60 frames per second, a 40 ms gap and a 50 ms gap land on almost the same frames.
- What is actually moving. A card that seems to slide may really be scaling and fading at the same time, with each property on its own timing.
So you rebuild from an approximation. Then a developer rebuilds your approximation, and the drift grows at every step.
Capture the motion, not a video of it
The Capture Motion Chrome extension records the animation itself. The routine takes about a minute:
- Click the extension icon, then click the element. Pick the smallest container that holds the whole motion: the whole menu, not one item.
- Trigger it the way a visitor would: reload, scroll, click or hover. For hover, the extension applies a real
:hoverstate while the capture runs, so you do not have to hold the pointer perfectly still. - Check the preview. It replays what was recorded and lists every animated property with its keyframes, durations, delays and easing.
It reads the main ways sites animate: CSS transitions, CSS keyframes, the Web Animations API, GSAP and Lottie. You do not need to know which one the site uses. Finding out is part of the capture.
Capturing and previewing need no account, and captures are unlimited and saved on your device.
What you get instead of a guess
The difference is that the numbers are no longer opinions:
| Question | From a recording | From a capture |
|---|---|---|
| How long is it? | Counted frames, rounded | The duration of each property |
| What is the curve? | "Something like ease-out" | The easing value as written |
| How is the stagger spaced? | Hard to see below 50 ms | Each item's delay |
| What actually moves? | What it looks like | Every animated property, listed |
Once the preview matches what you saw, you can take it straight into your work. The popup has code tabs for CSS, React and GSAP (plus Lottie when the source is Lottie). Copy for LLM gives Claude or ChatGPT the capture with a ready-made instruction. The JSON goes into the Figma plugin as a Figma Motion timeline. Copying and downloading need a free account.
Where the hours come back
The obvious saving is the frame-stepping itself. The bigger saving comes later:
- No second guess in code. The developer gets the same values the designer saw, so nobody re-derives the timing.
- Fewer review loops. "It feels a bit off" usually means a rounded duration or a swapped curve. With the real values in hand, you can check instead of debate.
- Reusable references. A capture can be saved to My Gallery and opened again on the next project, instead of hunting for the original site, which may have changed by then.
Habits that keep captures clean
- Close cookie banners and pop-ups before you capture. Anything that animates during the capture becomes a stray track.
- Use the window size you are designing for. Many sites change their motion at different breakpoints.
- For a list that staggers in, pick the list. The stagger lives in the differences between items.
- If the replay is missing part of the motion, capture the parent. If it has extra tracks, pick something smaller.
Respect the source
Capturing is for learning how a piece of motion is built and reusing timing ideas in your own design. The look of someone else's product (their layout, brand and illustrations) is still theirs. Take the curve and the rhythm, then make the rest yours.
Try it now. Install the Capture Motion extension from capturemotion.dev, pick one animation you have been meaning to copy, and compare the capture with the guess you had in your head. The gap is usually in the easing.
Questions
Which kinds of animation can the extension read?
CSS transitions, CSS keyframes, the Web Animations API, GSAP and Lottie. You do not need to know which one a site uses before you capture.
Do I need an account to capture?
No. Capturing and previewing need no account, and captures are unlimited and saved on your device. Copying and downloading need a free account.
