Render a project
Sign in once, then render the current project:renders/.
Choose a composition or output path when the defaults are not right:
Choose the output
Check what will upload
Media files of 5 MB or more that the project names by path upload as HeyGen assets and are referenced by public, unsigned URL, so large footage and audio do not count against the 200 MB project archive limit. Uploads are cached, so re-rendering uploads only new or changed media. Media is streamed from disk as it uploads, so a large file never has to fit in memory; editing one while the command is preparing it stops the run. Inspect what will upload before starting a render:.hyperframesignore when needed:
.git, node_modules, root-level renders/, and root-level snapshots/.
Fill template variables
Use the variables declared by the composition:--variables-file.
For a local project, variable validation uses the entry selected by
--composition, or index.html when omitted. --strict-variables stops before
upload when a value does not match that entry’s declarations.
The first hyperframes cloud render that uploads a local project prints an asset_id. Reuse it to
render the same uploaded project with different values:
Run asynchronously
Submit without waiting and receive a webhook when the render finishes:--idempotency-key so an interrupted request can be replayed safely.
Choose another renderer
- Use
hyperframes renderwhile authoring or when the machine running the command should do the work. - Use AWS Lambda or Google Cloud Run when you need to own the rendering infrastructure.
- Use a deployment template when you need a working hosted starting point rather than the full distributed-rendering stack.