hyperframes-launches: HeyGen's launch video compositions, open for remixing

One directory per launch, each a self-contained composition

The repository holds the source for HeyGen's HyperFrames launch videos, and the unit of work is the directory. Each subdirectory is a standalone HyperFrames composition, and you open index.html in a browser or through the HyperFrames CLI to preview, render or remix it. The Videos table in the README lists twenty entries covering a range of launches, from the HF HeyGen x Stripe collaboration and the Claude paper launch to the Cloud Render launch, the Figma integration launch, the Frame.md storyboard launch, the Inspector launch, the PR-to-video launch, the SFX music launch, the Texture launch video, the Timeline editor launch, the Variables launch and the Website to HyperFrames demo. There are also four re-brandable templates in the heygen-apple-motion directory, plus standalone pieces such as the Kimi K3 promo, the SpaceX launch, the Liquid brand refraction and a Codex five-hour-limit replica. Most entries have a public video to watch on the HyperFrames viewer; the re-brandable templates, the Liquid brand refraction and the Send to HyperFrames launch are the ones without. That distinction is the point of the repository. A launch video is one specific piece of brand communication, while a template is a starting point you are meant to restyle.

The per-project layout is small and consistent

Every video directory follows the same shape, and the consistency is what makes the repository useful as a reference rather than as a pile of files. There is a top-level composition in index.html, a compositions directory holding scene-level compositions, an assets directory for the video, audio and image inputs, a renders directory for locally rendered videos, a STORYBOARD.md that is the shot-by-shot plan, and a meta.json holding project metadata. The Git policy is stated as precisely as the layout. Generated files under each top-level project's renders directory stay local, and you are asked to commit the composition source and the required input media under assets, while files under assets/renders remain tracked when they are an input rather than output. That distinction between a render that you produced and a render that is an input is the kind of detail that saves a repository from accumulating gigabytes of duplicated output, and it is written down rather than left to a gitignore guess. The top level of the tree also carries a NOTICE file and a .gitattributes file, the latter being what makes the Git LFS pickup of binary assets automatic.

Cloning needs Git LFS, and there is a text-only route

The repository uses Git LFS for video, audio, image and font assets, while HTML, CSS, JS, JSON and Markdown are stored as regular text. The setup instructions start with the one-time LFS installation.

# one-time: install Git LFS
brew install git-lfs     # macOS
git lfs install

# clone (LFS assets download automatically)
git clone https://github.com/heygen-com/hyperframes-launches.git
cd hyperframes-launches

If you cloned without LFS installed, the assets are pulled afterwards.

git lfs pull

And there is a third option for when you only want the text, with the smudge step skipped so the large media stays on the server and you fetch just the subset you need.

GIT_LFS_SKIP_SMUDGE=1 git clone https://github.com/heygen-com/hyperframes-launches.git
cd hyperframes-launches
git lfs pull --include="hyperframes-launch/assets/*"   # or any subset you need

For a repository of this size, with twenty launch videos and their media, that last route is the sensible default for anyone who wants to study the compositions rather than watch the videos. The media are the heavy part and the composition source is a few kilobytes of text per project.

Previewing and rendering a composition

Working on a video means two commands in the project directory.

cd hyperframes-launch
hyperframes preview     # open the studio
hyperframes render      # render to mp4

The preview opens what the README calls the studio, and the render produces an mp4. The HyperFrames CLI documentation is linked from the README for the full command set, which tells you that the two commands here are the common cases rather than the whole interface. This is the part of the project that depends on software not in this repository. The compositions here are HTML, CSS and JavaScript, but they are written against the HyperFrames runtime, so opening index.html directly in a browser works for preview while rendering, and anything that depends on the studio tooling, expects the CLI to be installed. That dependency is worth checking before you plan around the repository, because a composition is not a self-contained HTML file that renders the same way in any browser. The four re-brandable templates in heygen-apple-motion are the entries most likely to reward a close read, since a template is written to be modified rather than only watched.

The licence is two licences, and only one of them is permissive

The license section is the most consequential paragraph in the README and it deserves to be read closely. Original composition source code, configuration and documentation authored by HeyGen in the repository are licensed under the Apache License 2.0, unless a file states otherwise. That license does not apply to bundled media, brand assets or fonts, including logos, photos, audio, video and screenshots, or to third-party software, and those materials remain subject to their respective owners' terms and may require replacement or separate permission before redistribution. The Apache License also does not grant permission to use HeyGen's or any third party's trademarks. The practical reading is that the code is yours to study, modify and reuse under Apache terms, while the assets that make a launch video look like a HeyGen launch video are not. Anyone planning a remix that gets published has to replace the media, which is exactly what the re-brandable template directory exists to support, and the repository also asks you to see the license before redistributing bundled assets. The repository itself is licensed Apache-2.0, and the last push was on 2026-10-04 with no GitHub releases published, so there is no version to pin to.

Adding a launch video to the collection

The contribution path is four steps, and it is short because the tool does the scaffolding. You create a new subdirectory with mkdir my-launch, change into it, and run hyperframes init, which generates the project structure for you. Then you build the composition. Then you commit, and the README notes that Git LFS will pick up the binary assets automatically via the root.gitattributes. Finally you add a row to the Videos table at the top of the README, which is a manual step worth not forgetting, since a project without a table row is effectively invisible to anyone browsing the repository. The four re-brandable templates are the only entries the README describes as templates, and they are among the few rows with no public video linked, so the difference between a launch record and a template is present in the table itself. The top level of the tree confirms the naming convention, with a directory per launch named after the launch, in lowercase and hyphenated, apart from the HF-heygen-stripe directory which follows the product naming.

Why this is a reference and not a component library

The alternative to using this repository is to build a launch animation from scratch, which for a product launch means designing type, timing, transitions and sound, and then rendering it. A general animation tool, from a browser-based timeline editor to a code-driven motion system, gives you more control and asks you to make more decisions, and it will not hand you a working example of how a company in this space structures a thirty second product film. That is the value here, and it is a real one, because the compositions are the ones HeyGen actually shipped. The limits follow from the same fact. You cannot lift the finished videos, you cannot use the brand assets, and you cannot assume the HyperFrames runtime you have matches the one these were authored against, since the repository pins no version of the CLI. The compositions are also not a general design system: each project has its own storyboard, its own assets and its own meta.json, and there is no shared component layer across the twenty directories, so learning from one project does not give you reusable parts. Treat the repository as a set of worked examples of a particular kind of motion design, with the code open and the media closed.

Editorial conclusion

Adopt hyperframes-launches if you want to learn from or rebuild a real product launch animation, since each directory is a self-contained composition with a shot by shot storyboard and a working preview and render path. Skip it if you intend to publish a remix unchanged, because the Apache-2.0 grant covers the composition source and configuration only, not the logos, photos, audio, video, screenshots or fonts, and the licence grants no trademark rights at all. Verify first that you have Git LFS installed before cloning, that the media you plan to keep is either your own or separately licensed, and that the HyperFrames CLI version you install matches the composition structure in the directory you are opening.

Frequently asked questions

Official sources

1. heygen-com/hyperframes-launches on GitHub
2. Issues
3. License: Apache-2.0
4. README