Render

To render a video is to compute every frame of a project and encode the frames, together with the sound, into a file such as an MP4. The word comes from computer graphics, where rendering means producing an image from a description of it. A video editor renders when it exports; a code-based tool renders when it turns a page or a script into frames.

How rendering works with code

In HyperFrames, a video is a web page. Rendering steps through it frame by frame: for each frame the renderer works out the exact time, moves every animation to that moment, captures the picture in Chrome and passes it to FFmpeg, which encodes the video and mixes in the sound. At 30 frames per second, a 6-second reel is 180 frames.

Because each frame is asked for at an exact time, the result is deterministic: the same project renders the same frames every time.

Settings that matter

Higher quality means bigger files; apps compress uploads again, so give them a clean master rather than the smallest file.

Rendering many versions

A template with variables can render one file per row of data, for example one video per product, in one command. That is batch rendering; see batch-rendering video variants.

Where it runs

Rendering runs on your own computer, or in a cloud session when you work from a phone. No upload or render credits are needed with HyperFrames. A short reel takes minutes, most of it while the frames are captured; heavy effects and long videos take longer.

In Motion Cheat Code

Every template in the pack renders with one command or one sentence to Claude Code, and the prompts end with a render step that checks the project, looks at snapshots and fixes problems before the final file is made.