Capture
Read the room.
We fetch the public page and its linked stylesheets and scripts within strict size and network limits. With the crawl on, the same read travels through the site's own links.
Motion forensics for the web
Motion forensics / public read
No. 001Paste a link. webcopy reads the delivered HTML, CSS and JavaScript, then counts every keyframe, transition, scroll rig, library and design token it can find — and gives you the receipts.
01 / Method
Most motion audits rely on a recording. We prefer the source. webcopy fetches the public document, follows its stylesheets and scripts, and reconstructs what the page intends to do.
That means you see the systems — not just the frames that happened to be on screen. The result is a dense, exportable readout for designers, engineers and the incurably curious.
Read the room.
We fetch the public page and its linked stylesheets and scripts within strict size and network limits. With the crawl on, the same read travels through the site's own links.
Follow the signal.
Every @keyframes block, animation shorthand,
transition, scroll timeline and JavaScript trigger is pulled into
one normalized record. Libraries and browser APIs are named.
Leave with receipts.
Colors, type stacks, radii, shadows, assets, headings, links and forms become a searchable field report. Download the whole thing as clean JSON — or copy a single agent prompt that carries the motion and design system into your next build.
02 / Scope
Four ledgers, one read — plus a copy-ready agent brief. The report is built to be browsed like a specimen: start with motion, then wander into the design system, the asset list and the source inventory.
A fictional studio site, built to exercise every corner of the report. No network required.
03 / Begin
Public pages only. Static analysis. Built for people who open the inspector before they take a screenshot.