Skip to main content
@hyperframes/studio contains the React application, editor components, player, timeline, and hooks that power HyperFrames Studio. Most people should not install this package directly. To open a project in the complete Studio application, run:
Install the package only when you are extending Studio or building an editor that uses its lower-level parts:
The exported components are building blocks, not a drop-in embedded editor. Components such as EditorShell, NLEPreview, Timeline, PropertyPanel, and FileTree require project state, callbacks, or Studio contexts. Use StudioApp when you need the complete application, or inspect the component types before composing a custom host.
When you run Studio from the monorepo, its dev server listens on http://localhost:5190.

Entry points

Peer dependencies are React 19, React DOM 19, and Zustand 4 or 5.

Main exports

Complete application

Editor structure

Playback and timeline

Hooks and utilities

The package also exports CompositionLevel, TimelineElement, PickedElement, and PatchOperation.

How Studio stays connected to a project

  1. Studio loads the composition in an iframe with the HyperFrames runtime.
  2. Player controls communicate with that runtime to play, pause, and seek.
  3. The editor and timeline send changes through the Studio API.
  4. The Studio server writes those changes back to the project files.
  5. External file changes refresh the preview while keeping the current position when possible.
Preview and render use the same seekable composition contract. Preview still depends on the browser playing in real time, while render captures frames one at a time. A heavy project can therefore stutter during preview and still render every frame.

Tailwind preset

Use Studio

Learn the complete editing workflow.

Studio server

Connect project files, media, linting, and render jobs.

Player

Embed playback without the editing interface.

SDK

Query and edit compositions without Studio.