HyperFrames: HeyGen's bet that agents should write video as HTML

HyperFrames is HeyGen's open-source answer to a real problem: coding agents are good at HTML and bad at timelines. A composition is just a web page where elements carry data-start and data-duration attributes. The renderer pauses the page and seeks headless Chrome to each exact frame before capturing it, so the same input produces the same MP4 every time. That matters if you batch-render variants or cache renders in CI.

The part that makes it agent-native is the skills pack. After installing the core skills (npx skills add heygen-com/hyperframes), you start every request with /hyperframes. That router reads what you hand it and routes it: a product URL becomes a launch video, a script becomes a faceless explainer, a GitHub pull request becomes a PR-to-video, talking-head footage becomes captions or a designed recut, and a music track becomes a music-driven piece. Domain skills cover animation rules, creative direction, media (TTS, transcription, background removal) and the CLI loop: init, preview, lint, check, render.

Community reaction is mixed, and we think that's useful to know. Reddit testers say it's easier to start with than Remotion and the motion feels smooth, but it eats tokens and one-shot results are inconsistent. One person who made about ten Remotion videos and one HyperFrames video called it buggy. HeyGen's own comparison page is unusually candid: Remotion is more mature, and HyperFrames breaks quietly if you use wall clocks or unseeded randomness.

Our take: if your motion work already lives in HTML, GSAP or Lottie, or you want deterministic batch renders, put HyperFrames on your shortlist. If your team writes React, Remotion is still the safer default. Requirements: Node 22+ and FFmpeg.