From a Framer or Webflow animation to code you own
Builders are great until you leave. A Framer or Webflow interaction is locked to the tool that made it; the exported code, when there is one, carries the runtime with it. mvoom measures the published page — the browser does not know it was a builder — and gives you the mechanism as code with no runtime at all.
Whatever the builder's timeline says, the page performs something specific: this opacity over these 480 ms on this curve, starting when this box enters the viewport. mvoom reads that performance. Several of the reference pieces in Teardowns are Framer sites, measured exactly this way.
- 01Paste the published URL
Not the editor — the live site. Pick the piece.
- 02Get the recipe
Every interaction timed and curved, free.
- 03Buy the component
A React component with the Web Animations API, tokens and a preview. No builder runtime.
- The interaction as measured recipes
- A dependency-free React component
- Measured colour and type tokens as CSS custom properties
Can I measure my own Framer site to move off Framer?
Yes. Verify the domain under Settings → Your domains and read as much of it as your plan allows; the pieces come out as code you own.
Does it capture Webflow's scroll interactions?
Yes — scroll-linked transforms are scrubbed and recorded with their scroll range.
Reading is free and needs no account. Everything above is what runs today — nothing here is a roadmap.
READ A BUILDER SITE →