Extract the animations from any website — exact durations, curves and triggers
You have seen a piece of motion on a site and want to know exactly how it works — not roughly, exactly. mvoom opens the page in a real browser, asks the animation engine what is running, samples what the engine does not declare, and hands you the numbers: 620 ms, cubic-bezier(0.23, 1, 0.32, 1), 40 ms of stagger per card, triggered when the section enters the viewport.
First the page is scouted: mvoom lists the pieces that move and names them — a hero that staggers, a gallery that fades in, a counter that ticks — so you pick one instead of reading a whole page. Then five passes run on the piece you chose: the animation engine is queried, transitions are triggered, scroll-linked effects are scrubbed, canvases are probed, and anything the engine does not declare is sampled frame by frame.
The result is a recipe per mechanism: which properties move, from what to what, over how long, on which curve, after which delay, on which trigger. Elements that move the same way share one recipe, with their delays listed — that is what turns 186 fading cards into one line you can implement.
The text, the images, the fonts and the brand are destroyed inside the worker before anything is stored. What you get is the mechanism — durations, curves, structure — never the content. A site owner can exclude their domain with one DNS record, and it stays excluded.
- 01Paste the URL
At https://mvoom.cc, paste the page. mvoom lists what moves and names the pieces worth reading.
- 02Pick a piece
One piece per read. The engine measures it and shows the choreography: what moves, when, for how long.
- 03Read the recipe
Every mechanism with its numbers, plus a brief you can paste into your own AI. That much is free.
- 04Buy the component if you want the code
Between 1,200 and 12,000 credits ($12 to $120) depending on how much the piece does. You get a React component built from the measurement, with no dependencies.
- The choreography of the piece: every mechanism, timed
- Duration, easing, delay, trigger and properties for each recipe
- A brief written to be pasted into Claude, ChatGPT or Cursor
- A live reconstruction of the piece running on the measured numbers
How many reads are free?
A read is a page, and every piece on it is included. 2 pages a day without an account, 3 a day and 10 a month with a free account. Rereading a page you already read is free and does not count — it comes from a seven-day cache.
Does it work on GSAP, Framer Motion, Webflow or Lottie?
The engine reads the browser, not the library. Anything that ends up as a Web Animation, a CSS transition, a scroll-linked transform or a canvas draw is measured. Lottie and canvas pieces are measured as canvases: what moves, how fast, and a 3D reconstruction when it is WebGL.
Is this legal?
mvoom measures mechanics — timing, curves, structure — and never takes content, images, fonts or brand. Numbers are not copyrightable; a site's design is, and that is why the content is destroyed inside the worker. Site owners can opt out with one DNS record.
Reading is free and needs no account. Everything above is what runs today — nothing here is a roadmap.
READ A PAGE FOR FREE →