Skip to main content
Start here
How HyperFrames fits into an application
Understand the composition contract, editing surfaces, Player, CLI, and rendering layers before choosing an integration.
Building on HyperFrames means using an editable HTML composition as the shared source for automation, playback, editing, and rendering.
The runtime reads the timing attributes and controls clip visibility and media
playback. When the composition uses an animation runtime, HyperFrames seeks its
registered timeline as well. The HTML remains inspectable and editable by
normal web tooling.
Use the composition and schema reference when generating compositions or building a new authoring surface.
Use the CLI guide for the everyday commands and the complete CLI reference for flags and automation.
Use it for agents, backend jobs, custom editors, versioned template systems, or any application that must change the source rather than merely play it.
Start with the SDK quickstart.
Use its JavaScript API to play, pause, seek, change playback rate, and listen for timeline events. It does not edit or render the composition.
See the Player reference.
Every surface works on the same source. Choose the smallest layer that produces the result your application needs, then move lower only when the higher-level layer removes control you genuinely require.
Start with the composition contract
A composition is a finite HTML document with an explicit viewport, timed clips, media, and zero or more seekable animation runtimes.Choose the smallest integration surface
Do not start with the rendering engine when the CLI already performs the complete job. Do not add the SDK when the application only needs playback.
CLI: operate complete projects
The CLI is the highest-level technical surface. It creates projects, opens Studio, validates compositions, captures review frames, renders files, publishes projects, and drives cloud render backends.SDK: inspect and edit
@hyperframes/sdk opens composition HTML, gives elements stable data-hf-id identifiers, applies typed edit operations, emits JSON patches, supports undo and redo, and persists through adapters.
Player: embed and seek
@hyperframes/player is a web component that loads a composition in an isolated iframe and exposes video-like playback controls.
index.html
Rendering: choose the layer you need
- CLI — complete local and automated rendering.
- Producer — the Node rendering pipeline: capture, encode, and audio mix.
- Engine — lower-level seekable page capture and exact-frame control.
- Managed cloud — hosted rendering without operating Chrome or FFmpeg.
- AWS Lambda or Google Cloud Run — infrastructure you deploy and control.
