Getting Started
Verify your environment
Run the diagnostics command to check for required dependencies:Expected output:
Terminal
Preview your composition
Before rendering, preview your composition in the browser to verify it looks correct:
Terminal
Rendering Modes
- Local Mode
- Docker Mode
Local Mode (default)
Uses Puppeteer (bundled Chromium) and your system’s FFmpeg. Fast for iteration during development.Requires: FFmpeg installed on your system. See Troubleshooting if FFmpeg is not found.Terminal
- Fast startup, no container overhead
- Uses your system GPU for hardware-accelerated encoding (with
--gpu) - Best for iterative development
- Output may vary across platforms due to font and Chrome version differences
- Not suitable for CI/CD pipelines that require reproducibility
When to Use Each Mode
| Scenario | Recommended Mode |
|---|---|
| Local development and iteration | Local |
| CI/CD pipeline | Docker |
| Sharing renders with a team | Docker |
| Quick preview export | Local |
| AI agent-driven rendering | Docker |
| Benchmarking performance | Local |
Options
| Flag | Values | Default | Description |
|---|---|---|---|
-f, --fps | 24, 30, 60 | 30 | Frames per second |
-q, --quality | draft, standard, high | standard | Encoding quality preset |
-w, --workers | 1-8 | auto | Parallel render workers |
--gpu | — | off | GPU encoding (NVENC, VideoToolbox, VAAPI) |
-o, --output | path | — | Output file path |
--docker | — | off | Use Docker for deterministic rendering |
Tips
- Use
npx hyperframes benchmarkto find optimal settings for your system - 4 workers is usually the sweet spot for most compositions
- Docker mode is slower but guarantees identical output across platforms
- For compositions with many frames,
--gpucan significantly speed up local encoding
Next Steps
Deterministic Rendering
Understand the determinism guarantees
CLI Reference
Full list of CLI commands and flags
Troubleshooting
Fix common rendering issues
Common Mistakes
Avoid pitfalls that affect render output