Files
heygen-com__hyperframes/docs/guides/rendering.mdx
2026-07-28 19:16:15 -07:00

126 lines
3.6 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Render from the command line"
description: "Check a project and render MP4, MOV, WebM, GIF, or PNG output."
---
Studio is the simplest place to export a project. Use the command line when an agent, script, CI job, or advanced delivery workflow needs to control the render.
## Render a normal video
From the project folder:
```bash
npx hyperframes render --output final.mp4
```
If you omit `--output`, HyperFrames writes the result under `renders/`.
The normal workflow is:
```bash
npx hyperframes lint
npx hyperframes check
npx hyperframes render --output final.mp4
```
`lint` checks the project structure. `check` opens the project in a browser and looks for runtime, layout, motion, media, and contrast problems.
## Choose a format
| Format | Use it for |
| --- | --- |
| MP4 | Normal sharing, publishing, and delivery |
| MOV | ProRes workflows and transparent editing intermediates |
| WebM | Web delivery and transparent overlays |
| GIF | Short previews in issues, pull requests, and documentation |
| PNG sequence | Frame-by-frame handoff to compositing software |
Examples:
```bash
# Transparent web overlay
npx hyperframes render --format webm --output overlay.webm
# ProRes editing file
npx hyperframes render --format mov --output master.mov
# Short looping preview
npx hyperframes render --format gif --fps 15 --output preview.gif
# RGBA frames in a directory
npx hyperframes render --format png-sequence --output frames
```
GIF has no audio and limited transparency. Prefer MP4 or WebM for normal playback.
## Choose quality and frame rate
The default `standard` quality is the right choice for most finished work.
```bash
# Faster review version
npx hyperframes render --quality draft --output review.mp4
# Larger final master
npx hyperframes render --quality high --output master.mp4
# Explicit frame rate
npx hyperframes render --fps 60 --output final-60fps.mp4
```
Use a higher frame rate only when the source or destination needs it. It creates more frames, so rendering takes longer.
The CLI uses the composition’s `data-fps` when present and otherwise defaults to 30 fps.
## Local or Docker
Local rendering is the normal choice:
```bash
npx hyperframes render --output final.mp4
```
It starts quickly and can use the computer’s browser GPU.
Use Docker when a controlled Chrome, FFmpeg, and font environment matters:
```bash
npx hyperframes render --docker --output final.mp4
```
Docker adds startup and infrastructure overhead. It is useful for CI and repeatable production environments, not a requirement for every final render.
## Render another composition
The root `index.html` is rendered by default. To target another standalone composition:
```bash
npx hyperframes render \
--composition compositions/intro.html \
--output intro.mp4
```
Nested compositions that use `<template>` wrappers should be rendered through the root composition that includes them.
## Batch and cloud work
For several variable-driven versions, use batch rendering. For remote infrastructure, use HyperFrames cloud, AWS Lambda, or Google Cloud Run.
Those workflows involve output naming, credentials, concurrency, and infrastructure choices. Start in the [CLI guide](/developers/cli) and use the complete [CLI reference](/packages/cli) when you need every flag.
## If rendering fails
Run:
```bash
npx hyperframes doctor
npx hyperframes lint
npx hyperframes check
```
Keep the first exact error rather than only the final “render failed” message. See [Troubleshooting](/guides/troubleshooting) for the next checks.
<Tip>
Always watch the exported file itself. Preview proves that the project can play; the output file proves that the delivery is correct.
</Tip>