Your first motion project
Compose a scene, animate it on a timeline, and render it to PNG or MP4.
Motion projects are declarative scenes: a tree of visual nodes whose properties are animated by tracks across integer frames.
Create from a template
Start from a template — for example landscape — to get a working scene with
sensible defaults. Templates are the recommended path: they contain approved
node types, default properties, and animatable fields.
Understand the scene graph
A project is a tree of nodes:
| Node | Typical use |
|---|---|
| Text | Titles, captions, numeric labels |
| Rectangle / Line | Layout, rules, frames |
| Chart | Embed a live or snapshotted chart |
| Counter | Animated numeric readouts |
| Callout | Highlighted annotations |
| 3D objects | Three-dimensional scenes |
No JavaScript, expressions, or HTML are ever evaluated — motion is data, so what you can build is exactly what the schema allows, and rendering is deterministic.
Animate on the timeline
Animation tracks target individual node properties with keyframes and easing functions, evaluated across integer frames within visibility windows. A node that is not visible in a frame costs nothing. See motion timeline.
Render
Rendering is an asynchronous job:
- Apply your edits — they become an immutable revision.
- Request a render for a specific format: PNG frames or MP4.
- Poll the job until it completes, then download the output.
For animations, check the first, middle, and final frames before committing to a full MP4 render. See exports for the job lifecycle and output formats.