---
title: "Discussion on \"Video as Code: A Deep Dive into HeyGen’s Hyperframes\" | Hashnode"
description: "Discussion on \"Video as Code: A Deep Dive into HeyGen’s Hyperframes\". For years, the \"holy grail\" for web developers has been the ability to treat video as just another part of the DOM. We’ve had CSS animations and Canvas for the browser, but converting those into a pro"
url: "https://hashnode.com/posts/video-as-code-a-deep-dive-into-heygen-s-hyperframes/69e5186c13e74eec583611c7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Video as Code: A Deep Dive into HeyGen’s Hyperframes](https://blog.nidhin.dev/video-as-code-a-deep-dive-into-heygen-s-hyperframes?utm_source=hashnode&utm_medium=feed)

For years, the "holy grail" for web developers has been the ability to treat video as just another part of the DOM. We’ve had CSS animations and Canvas for the browser, but converting those into a pro

Apr 19 · 4 min read · blog.nidhin.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#heygen](https://hashnode.com/tag/heygen)
-   [#hyperframes](https://hashnode.com/tag/hyperframes)
-   [#html5](https://hashnode.com/tag/html5)
-   [#animation](https://hashnode.com/tag/animation)
-   [#video](https://hashnode.com/tag/video)
-   [#ffmpeg](https://hashnode.com/tag/ffmpeg)

## Written by

[nidhinkumar](https://hashnode.com/@nidhinkumar)

@nidhinkumar · Coimbatore, Tamilnadu, India

  
[View profile](https://hashnode.com/@nidhinkumar)

Software Engineer

## Responses 1

Markdown supported · ⌘↵ to post

[Sifat Ahmed](https://hashnode.com/@sifat0078)

[Sep 29](https://hashnode.com/posts/video-as-code-a-deep-dive-into-heygen-s-hyperframes/69e5186c13e74eec583611c7/comment/6abb6eb5f43652cda17fa11e)

Good rundown - the "Rule of Three" section is the part people skip and then regret. The GSAP { paused: true } + window.\_\_timelines requirement trips up almost everyone coming from a normal animation background, because your timeline plays perfectly in a live browser tab (wall-clock driven) and then renders as a single frozen frame, because the render pass seeks the timeline instead of letting it run. Same failure mode shows up with anything counter/ticker-based: if the number is driven by requestAnimationFrame deltas instead of being seekable to an exact timestamp, you get a frozen or wrong value on export even though it looked fine in preview. Worth calling out as its own gotcha since the error Hyperframes gives you when this happens isn't very descriptive. I ended up writing these up in more detail (this one plus four others) after hitting all of them myself - happy to share the notes if useful to anyone else going down this path.
