vawe vs HyperFrames.
HyperFrames is HeyGen's open-source framework for rendering HTML to video. It is vawe's closest peer: Apache-2.0, headless Chrome, and a pitch aimed at agents. This page lists the differences that remain.
Facts read from HyperFrames's own pages on 2026-10-03. Sources are listed at the end. vawe runs on your machine, needs no account and has no per-render fee.
Choose HyperFrames when
- You want a block catalog and a browser Studio to start from.
- You want cloud rendering on Lambda, Cloud Run or HeyGen.
- You like GSAP timelines and data-attribute timing in the HTML.
- You want skills for a named workflow such as a launch video or a PR video.
Choose vawe when
- You want ordinary web code to keep working: vawe replaces Date, timers and Math.random with seek-driven versions, where HyperFrames forbids them.
- You want timing from CSS keyframes, element.animate() or a seek(t) function, with no timing attributes in the markup.
- You want built-in adaptive motion blur and a library of 94 moves with After Effects eases.
- You want a film judged by a fresh session that did not write it.
What HyperFrames is.
HyperFrames turns HTML, CSS, media and seekable animations into MP4. A composition is plain HTML with data attributes for timing and tracks, animated by GSAP, CSS, Lottie, Three.js, Anime.js or the Web Animations API.
Side by side.
| feature | HyperFrames | vawe |
|---|---|---|
| What it is | Open-source framework: HTML to deterministic MP4 | Framework to make films from one HTML page |
| Licence | Apache-2.0 | Apache-2.0 |
| Authoring model | HTML with data attributes for timing and tracks; GSAP, CSS, Lottie, Three.js, Anime.js, WAAPI | One HTML page timed by CSS keyframes, element.animate() or window.seek(t) |
| Rendering | Headless Chrome seeks each frame, FFmpeg encodes; local, Lambda, Cloud Run, HeyGen cloud | Headless Chrome seeks and screenshots each frame; renders on your machine |
| Determinism | Forbids Date.now, requestAnimationFrame, system timers and unseeded Math.random in a composition | A virtual clock replaces those calls with functions of the seek time |
| Agent support | 21 skills, a /hyperframes router skill, non-interactive CLI defaults | bin/vawe CLI and skills; a separate session critiques and judges the film |
| Editor | Studio browser editor and a block catalog | No timeline editor: the page is the film |
| Distributed rendering | Yes: Lambda, Cloud Run, HeyGen cloud | No |
Where HyperFrames is stronger.
- Ecosystem. The HyperFrames repo shows about 55,900 stars and ships 21 installable skills, a Studio browser editor and a catalog of reusable blocks such as transitions, overlays and charts.
- Render targets. Its docs list local, AWS Lambda, Google Cloud Run and HeyGen cloud rendering. vawe renders on one machine.
- Ready workflows. Its skills include product-launch-video, faceless-explainer, pr-to-video and music-to-video.
- Time in market.
Questions people ask.
- Are HyperFrames and vawe both open source?
- Yes. Both are Apache-2.0. Neither has a company-size clause in the licence.
- How do they keep renders deterministic?
- HyperFrames states a rule: no Date.now, requestAnimationFrame or system timers, and no Math.random without a seed. vawe lets a page call them, and replaces them with functions of the seek time before any page script runs.
- Which one has more templates and blocks?
- HyperFrames. It ships a block catalog and a template gallery. vawe ships 94 moves and film templates in its prompts folder.
- Does vawe have cloud rendering?
- No. vawe renders on your machine. HyperFrames lists local, AWS Lambda, Google Cloud Run and HeyGen cloud rendering. Its hosted price is not public, so this page gives none.
Try vawe on one page.
Write a page, run one command, get an MP4. The quickstart takes a few minutes.