Getting started
Capture Motion for developers
How front-end developers use Capture Motion: copy exact timings from any site, export gallery animations as HTML or React, and get accurate code from Claude with an LLM prompt.
Most animation work in a codebase starts with someone else's motion: a design file, a reference site, a "make it feel like this" link. The slow part is not writing the CSS. It is finding out what the numbers are. Capture Motion reads them for you, from its gallery or from any live site, and hands them over as code or as data you can feed to a model.
Read the real numbers from any site
Install the Chrome extension, click the element, then trigger the animation: reload, scroll, click or hover. The extension reads CSS transitions and keyframes, the Web Animations API, GSAP and Lottie, and replays every animated property with its keyframes, durations, delays and easing.
That last part matters most. Easing is the hardest thing to judge by eye, and the capture gives it to you as a value: a cubic-bezier(), a GSAP ease or a linear() curve. A row of small, even delays tells you it is a stagger, with the exact gap.
From the popup, copy the motion as CSS, React or GSAP. Pick the tab that matches your stack, not the source site: a GSAP animation can come out as CSS if your project has no GSAP. The extension guide covers tricky cases like hover states and scroll-linked motion.
Ship a gallery animation
The gallery is 40 production-quality interactions you can drop into a project: tab bars, switches, toasts, sheets, pickers and expanding cards. Open one with View, set it up in Customize, and use the Copy menu:
| Format | What you get |
|---|---|
| HTML / CSS | A standalone page with the animation and its interactions. Open it in a browser to check before you move anything. |
| React | A .jsx component with the markup, the capture and the small player it needs, in one file. |
| LLM prompt | Instructions, the capture JSON and the card's own markup, for Claude or ChatGPT to rebuild in your stack. |
| JSON | The raw capture: layers, tracks, keyframes and timing. Useful for your own tooling and for the Figma plugin. |
Whatever you set in Customize (colour, text, speed, background, and card-specific options such as a light or dark theme) is in every format, so the code matches what you saw. From the gallery to a React component walks through dropping the component into an app.
Get accurate code from Claude or ChatGPT
Asking a model to "make a stretchy tab indicator" gets you a generic one. Giving it the capture gets you the real one. The LLM prompt contains the full instruction, the timing data and a visual reference, so the model rebuilds the animation with the same durations and curves.
- Copy the LLM prompt from a gallery card or a capture.
- Paste it as the first message of a new chat, then add one line about your stack: "Build this as a React component with Tailwind."
- Check the timings against the JSON before you change anything.
Good follow-ups and a timing checklist are in recreating an animation with Claude or ChatGPT.
Work from the same numbers as design
When a designer captures or customizes an animation, the same JSON goes to Figma (through the plugin) and to you. There is no translation step where 320 ms becomes "about a third of a second". If you are the one capturing, send the JSON or a saved My Gallery item back to design, and they can open it in Figma as layers.
Good habits
- Capture clean. Pick the smallest container that holds the whole motion and close cookie banners first. Stray tracks become stray animations.
- Pull timings into variables. Move durations and easings into CSS custom properties or a motion token file, so the whole product can be tuned in one place.
- Add a reduced-motion path. Every export is a good base for a
prefers-reduced-motionversion: keep the fades, drop the movement. See the reduced-motion guide. - Keep sources. Save captures you build from to My Gallery, so the reference survives when the original site changes.
Try it in five minutes
- Open the gallery and pick Liquid Tabs. Its indicator's two edges ride different springs, so it stretches ahead and catches up.
- Download the React export and render it in a scratch project.
- Now capture the tab bar of a product you use every day with the extension, and compare its timings with yours.
New to Capture Motion? Getting started is the ten-minute tour.
Questions
What code formats can I get?
From a gallery card: JSON, an LLM prompt, a standalone HTML / CSS page and a React component. From the Chrome extension: CSS, React and GSAP tabs, plus Lottie when the source is a Lottie file.
Do the exports need a runtime library?
No npm package. The React component carries the small player it needs inside the file, and the HTML page is self-contained. The 3D cards, such as Glass Switch, load three.js from a CDN.
Is my Customize choice in the code?
Yes. The colour, text, speed, background and any card-specific options you set in Customize are in every export, including the React component.
How many downloads do I get for free?
The free plan includes 15 HTML / React downloads a month from a card's popup, and unlimited JSON and LLM prompt copies.
