HyperFrames Studio vs the Open-Source HyperFrames Framework: Which One Do You Need?

Short answer: if you want to type a prompt (or upload an image) and get an AI-generated video clip back in your browser, you want HyperFrames Studio on hyperframes.net. If you are a developer who wants to write HTML, CSS and JavaScript and render that page frame by frame into an MP4 from the command line, you want the open-source HyperFrames framework published at github.com/heygen-com/hyperframes. They share a name, but they solve different problems, they are operated by different teams, and they are paid for differently.

This guide exists because the name causes real confusion. In our own Google Search Console data for the last 28 days, the query "hyperframes" produced 2,161 impressions but only 3 clicks to this site, and related searches such as "que es hyperframes", "hyperframes license" and "hyperframes pricing" keep appearing. Most of those people are trying to work out which HyperFrames they are looking at. Below is a plain comparison so you can pick the right one in a minute.

What the open-source HyperFrames framework is

The framework is a code-first video renderer. According to its README, it turns HTML, CSS, media and seekable animations into deterministic MP4 videos. You author a composition as a normal HTML file with timing data attributes, preview it locally, and render it with a CLI:

• npx hyperframes init my-video creates a project.
• npx hyperframes preview opens a local preview.
• npx hyperframes render --output final.mp4 renders the file.

Under the hood it drives a headless Chrome page and encodes frames with FFmpeg. It is published under the Apache 2.0 license, and its README states there are no per-render fees for running it yourself. It is built with AI coding agents in mind: agents already write HTML, the CLI is non-interactive by default, and the project ships "skills" that teach an agent its composition rules. You bring your own animation runtime (GSAP, CSS animations, Lottie, Three.js and others), and the same input always produces the same frames, which makes it a good fit for CI pipelines and automated, templated videos such as product explainers, data visuals or pull-request recaps.

What it is not: it is not a text-to-video model. It will not invent footage of a person walking on a beach from a sentence. Every pixel comes from the HTML page you (or your agent) wrote.

What HyperFrames Studio on hyperframes.net is

HyperFrames Studio is an independently operated, hosted AI generation workspace. You do not install anything or write code. You open the Studio in a browser, pick a workflow, and a hosted AI model generates the media for you. The public Studio currently exposes five workflows:

1. Text-to-video: describe a shot and generate a clip.
2. Image-to-video: animate an authorized first frame, with an optional last frame for shot control.
3. Reference-to-video: guide a clip with supported reference media.
4. Text-to-image: generate still images from a prompt.
5. Image-to-image: edit or restyle a source image.

Before you submit a task, the workspace shows the selected model, duration, resolution and the exact credit cost. On the current pricing page, a 4-second video costs 40 credits and the default 15-second video costs 150 credits. The one-time Try pack is $49 for 500 credits, and monthly and annual plans are listed on the pricing page. The Studio also has limits worth knowing up front: it accepts prompts and supported media references, but it does not ingest websites, documents, PDFs or code repositories today, and any media URL you paste must point directly to a public file.

You can try the text-to-video workflow on this page without leaving the article.

Side-by-side comparison

How to choose in practice

Pick the Studio when the content does not exist yet and you want an AI model to imagine it: a cinematic B-roll shot, an animated version of a product photo, a short social clip from a one-line idea, or a set of concept images. You care about speed and visual variety more than frame-level control, and you would rather not maintain a rendering pipeline.

Pick the framework when the content is structured and you want exact control: a branded lower third, a chart that animates from real data, a templated video you need to regenerate hundreds of times with different text, or a video an AI coding agent should assemble from code. You care that a re-render gives identical output, and you are comfortable with npm and a terminal.

Many teams will use both. A common pattern is to generate a few B-roll clips or illustrations with a generative tool, then place those files inside a code-driven composition for titles, captions and data overlays. The two products do not depend on each other; they just fit at different points of the same production.

Common mix-ups and how to avoid them

Searching the brand name only. Typing "hyperframes" into a search engine returns both projects. Add "studio" or "AI video generator" if you want the hosted generator, and "github", "npm" or "CLI" if you want the framework.

Expecting the Studio to render your HTML. It will not. If you have an HTML composition, the open-source CLI is the tool that renders it.

Expecting the framework to generate footage from a prompt. It will not either. It renders what your page draws. Generative footage needs a generative model, which is what the Studio provides.

Assuming one account covers both. The Studio has its own accounts, credits, billing and support on hyperframes.net. The framework is self-hosted and documented in its own repository. Our AI wrapper disclaimer explains that hyperframes.net is an independently operated product and is not an official upstream vendor portal.

Frequently asked questions

Is HyperFrames free?

The open-source framework is free to run yourself under the Apache 2.0 license. HyperFrames Studio on hyperframes.net is a paid, credit-based hosted service; the credit cost of each task is shown before you submit it, and plans are listed on the pricing page.

Is HyperFrames Studio the same as the HyperFrames GitHub project?

No. The GitHub project is a code framework for rendering HTML into video. HyperFrames Studio is a hosted, no-code AI video and image generator with its own accounts and billing.

Do I need to code to use HyperFrames Studio?

No. You choose a workflow, write a prompt or upload an authorized image, review the settings and credit cost, and submit. Everything runs in the browser.

Can HyperFrames Studio turn a website or a PDF into a video?

Not today. The public Studio accepts prompts and supported media references only. If you need to turn structured content into a video with code, the open-source framework is the closer fit.

How much does a HyperFrames Studio video cost?

On the current pricing page a 4-second clip costs 40 credits and the default 15-second clip costs 150 credits. The one-time Try pack is $49 for 500 credits. Always check the live cost in the workspace, because it changes with duration, resolution and workflow.

Bottom line

Both projects carry the HyperFrames name, but the decision is simple. If you want an AI model to create video or images from a prompt, start with the Studio embedded below this article. If you want to write HTML and render it into a reproducible MP4, go to the open-source repository and follow its quickstart.