Skip to main content
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. The whole loop: the project, the render command, progress, and the finished file playing. The flags shown are the ones people actually reach for — format, resolution, frame rate, quality.

​
Render a normal video

From the project folder:
If you omit --output, HyperFrames writes the result under renders/. The normal workflow is:
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

Examples:
GIF has no audio and limited transparency. Prefer MP4 or WebM for normal playback.

​
Transparent video

Use WebM for a transparent web overlay or MOV for a ProRes 4444 editing intermediate. Leave the composition background unpainted wherever the output must remain transparent; an opaque html, body, or full-frame background will be encoded as visible pixels.
MP4 is the normal opaque delivery format. After rendering transparency, inspect the file over a contrasting background rather than trusting a player that always shows black behind alpha.

​
Input video codecs

Studio, preview, check, and published projects normally create cached browser proxies for local video that Chrome cannot decode reliably, including common HEVC and ProRes inputs. The original file stays in the project and remains the render source. If a clip is black only in preview, keep automatic proxying enabled, confirm the source is local, and run npx hyperframes check. Disable proxying only when the browser already supports the source or you are diagnosing the proxy itself.

​
Choose quality and frame rate

The default standard quality is the right choice for most finished work.
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:
It starts quickly and can use the computer’s browser GPU. Use Docker when a controlled Chrome, FFmpeg, and font environment matters:
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:
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 and use the complete CLI reference when you need every flag.

​
Render provenance

Rendered video carries two container metadata tags that say which tool wrote the file:
That is the whole of it. The tags name the renderer and its version, and nothing else: no file paths, usernames, machine names, project names, or anything about the composition. They are container metadata, not a visible watermark, so no pixel of your video changes. Matroska uppercases tag names on read, so a .webm reports HYPERFRAMES_RENDERER. Strip them whenever you like:
These tags are an unauthenticated diagnostic hint, not proof of origin. They are ordinary unsigned container keys, so anything can write the same two values with a single ffmpeg -metadata command: a tag that is present means the file claims to be HyperFrames output, not that HyperFrames wrote it. A tag that is absent means just as little, because re-encoding, remuxing, or any tool that drops unknown keys strips it, and files rendered by older versions never carried it. Treat it as a “what probably produced this file?” hint for support and debugging, never as an authenticity, attribution, or licensing check. Verifiable provenance needs signed claims such as C2PA.

​
If rendering fails

Run:
Keep the first exact error rather than only the final “render failed” message. See Troubleshooting for the next checks.
Always watch the exported file itself. Preview proves that the project can play; the output file proves that the delivery is correct.