A molecular animation studio · in the browser · no backend
Real structural data in. Cinematic motion and poster-resolution stills out. A responsive live preview and opt-in ray-traced final light — all in the tab you just opened.
Direct the scene in a fast screen-space preview, then let the final frame converge — traced shadows, occlusion, bounce light, and glossy reflection accumulating pass after pass. No farm. No queue. The shot list:
Any saved selection becomes a component. Components stack seven general behaviours — phased, copied, attached to other moving parts — into an editable graph of machinery. Molecular motion from first principles, no code:
No-code · Unconstrained
Build motion from anything
Start anywhere. Protein domains, ligands, DNA strands, waters, or a custom residue query can all be components.
A demonstration should never quietly become evidence. Annotations and shots carry provenance — the studio itself tells your audience that a camera move makes no claim about the molecule, that staged motion is illustrative, that deposited coordinates were never touched. Citations export with the frames.
Scene: yours · Take: 001
One HTML file, WebGL 2, no account. Your project lives in a client-side document; the deposited atoms are never modified.
No. Browser-only, WebGL 2, no backend. Serve the folder over HTTP so the local material atlas loads — that's the whole stack.
In a client-side project document — shots, cameras, components, annotations. Deposited atom coordinates remain unchanged.
No — Motion Lab is a visual motion system for demonstration, and it says so on every annotation via provenance labels.
High-fidelity stills at poster resolution via tiled rendering — with AgX or ACES colour, depth of field, bloom, and fog baked into the frame.
Yes — the studio is one readable HTML file plus a deterministic atlas pipeline. Issues and PRs welcome on GitHub.