Tutorials
The Capture Motion Chrome extension: a complete guide
A reference to the Capture Motion extension: picking elements, triggers, what it captures, the preview, code tabs, Copy for LLM, HTML download and accounts.
The Capture Motion Chrome extension records an animation on a live page and turns it into data you can reuse: code, a prompt for a language model, a self-contained HTML file, or JSON for Figma. This guide is a reference to the extension itself. It goes through each part of the popup in order and says what it is for.
If you want the background first, on why copying motion by eye is slow and how the extension compares with Chrome DevTools, read how to copy an animation from any website.
Install and pin it
Add Capture Motion from the Chrome Web Store, then pin it so the icon stays in the toolbar. You will use the icon every time you start a capture, so pinning saves a trip into the extensions menu.
Step 1: pick the element
Click the Capture Motion icon in the toolbar, then click the element on the page. What you pick decides what is recorded, so it is worth a moment's thought.
The rule is: pick the smallest container that holds the whole motion.
| If you pick | You get |
|---|---|
| A single child, such as one icon in a button | That child's motion only. The parent's movement is missing. |
| The component, such as the whole button or card | Every track that makes up the effect, and nothing else. This is usually right. |
| A large section or the full page | Extra tracks from unrelated elements that you will have to ignore later. |
For a list that staggers in, pick the list, not the first item. The stagger lives in the differences between items, so you need all of them.
Step 2: trigger the animation
Trigger the animation the way a visitor would. Animations can behave differently when started out of order, so use the real trigger.
- On load: reload the page.
- On scroll: scroll the element into view.
- On click: click it.
- On hover: hover it. The extension applies a real
:hoverstate through the Chrome DevTools Protocol, attached only while the capture runs. That means you do not have to hold the pointer perfectly still. Capturing hover animations covers hover in more depth.
Close cookie banners and pop-ups first, and use the window size you are designing for, since many sites change their motion at different breakpoints.
What it captures
The extension reads motion from the four main ways websites animate:
| Source | Typical use on a site |
|---|---|
| CSS transitions | Hover and state changes, such as a button lifting or a menu opening |
| CSS keyframes | Entrances, loaders and looping effects |
| Web Animations API | Motion started from JavaScript with element.animate() |
| GSAP | Timelines, staggers and scroll-linked sequences |
| Lottie | Illustrations and icon animations exported from After Effects |
You do not need to know which one a site uses before you start. That is part of what the capture tells you. If you want to understand the differences, see our Web Animations API guide, GSAP vs CSS animation and CSS animation vs Lottie.
Step 3: check the preview
When the capture finishes, the popup replays what it recorded, and shows each animated property with its keyframes, durations, delays and easing. Capture and preview need no account.
Use the preview as a check before you export anything:
- Does the replay match what you saw? If part of the motion is missing, you probably picked too small an element. Capture again with its parent.
- Are there tracks you did not expect? If so, the element was too large, or something else animated at the same moment. Pick a tighter container or close whatever got in the way.
- Read the easing. This is the part that is hardest to judge by eye, and the preview gives it to you as values. Finding the easing curve of an animation explains how to read it.
- Note the delays. A row of small, even delays is a stagger. Uneven delays are usually deliberate choreography worth keeping.
Step 4: take it out
The rest of the popup is about getting the capture into your work. Copying and downloading need a free account.
Code tabs
The popup shows the capture as code in three tabs: CSS, React and GSAP. When the source is Lottie, there is a Lottie tab as well. Each tab has its own Copy button.
Pick the tab that matches your stack, not the source. A motion captured from a GSAP site can go into the CSS tab if your project has no GSAP, and the other way round. Every tab is built from the same capture.
Copy for LLM
Copy for LLM copies the capture JSON with a ready-made instruction for ChatGPT or Claude. Paste it into the chat and the model returns a self-contained HTML file, or a component, that uses the captured timings and easing.
A few habits help:
- Ask for React or Tailwind if that is your stack.
- Ask the model to keep the timings as given.
- Then ask for your own content and colours.
Recreating a website animation with Claude walks through a full session.
HTML download
You can also download a self-contained HTML and CSS file. It opens in any browser with nothing else installed, which makes it useful for a quick demo, a review link, or a file to attach to a ticket.
The Capture Motion button
The main Capture Motion button copies the capture to the clipboard as JSON. That JSON is the most portable form of the capture. You can:
- Paste it into the Figma plugin. The Capture Motion plugin rebuilds it as a Figma Motion timeline in Figma Design. See the Figma plugin guide.
- Keep it in My Gallery. On the website, My Gallery has a Paste JSON tab for Capture JSON. See saving animations to My Gallery.
When you need an account
| Action | Account needed? |
|---|---|
| Pick an element and capture | No |
| Preview the replay and read the values | No |
| Copy from the CSS, React, GSAP or Lottie tab | Free account |
| Copy for LLM | Free account |
| Download the HTML and CSS file | Free account |
| Capture Motion button (JSON to clipboard) | Free account |
So you can try the extension on any page and see exactly what it records before you sign up. For what plans add, see pricing.
Quick reference
- Click the icon, then click the smallest container that holds the whole motion.
- Trigger it as a visitor would: reload, scroll, click or hover.
- Check the preview against what you saw. Recapture with a different element if it is off.
- Choose the output: a code tab for your stack, Copy for LLM for a model, the HTML download for a demo, or the Capture Motion button for JSON.
Questions
What kinds of animation can the extension capture?
CSS transitions and keyframes, Web Animations API animations, GSAP and Lottie. It records each animated property with its keyframes, durations, delays and easing.
Do I need an account to use the extension?
Not to capture and preview. A free account is needed to copy or download anything: the code tabs, Copy for LLM, the HTML download and the Capture Motion button that copies the JSON.
How does it capture hover animations?
It applies a real :hover state through the Chrome DevTools Protocol, attached only while the capture runs, so you do not have to keep the mouse still over the element.
Which export should I use?
Use a code tab if you are building it yourself, Copy for LLM if you want ChatGPT or Claude to rebuild it, the HTML download for a self-contained demo, and the Capture Motion button for the JSON that goes into the Figma plugin or My Gallery.
