HyperFrames vs. Remotion: which engine for AI-made video?
Both let an agent write video as code and render it to MP4. They differ in what the agent writes and in licensing.
HyperFrames
- What you write: HTML, CSS and GSAP timelines. Agents already write this fluently.
- Rendering: a CLI (
npx hyperframes render) drives headless Chrome and FFmpeg, frame by frame, deterministically. - Built for agents:
checkruns lint, runtime, layout, motion and contrast audits;snapshotcaptures still frames so the agent can look at its own work before rendering. - License: Apache 2.0, free for commercial use. github.com/heygen-com/hyperframes
Remotion
- What you write: React components, with frame-based hooks (
useCurrentFrame). - Strengths: a mature ecosystem, great for data-driven and programmatic video at scale, and server-side rendering on Lambda.
- License: free for individuals and companies with up to three people; larger companies need a company license.
Which one we use
Every skill in our first collection runs on HyperFrames. HTML and CSS keep templates readable and easy to edit by hand, the built-in audits catch layout problems early, and the Apache license means there's nothing extra to buy when you use a skill at work.
If your team already builds with React and Remotion, the same motion ideas carry over. The craft (pacing, typography, easing, restraint) is what makes the video, not the engine.