62–81s
For a 16-minute film
Quick enough to render the whole film again after every edit, not once at the end of the day.
Livea 16-minute film is rendering behind this page
Overcrank renders the videos you build in code. A 16-minute film that takes Chrome 36 minutes comes back in about a minute, so you can watch every change instead of waiting for it.
The whole film163 × 183
Every cell is one frame of the film. They are filling in while you read this.
Every frameFull HD
In order, with the sound mixed in. The pictures in these cells are stand-ins drawn for this page. The speed is real.
Checked392 frames
Sample frames are compared with what Chrome would have drawn. On this film, none of the 392 came back different enough to flag.
Speedmeasured 19 to 20 Nov 2026
62–81s
Quick enough to render the whole film again after every edit, not once at the end of the day.
26–35×
The usual route draws every frame in a browser. For the same film that takes 36 minutes.
6–7¢
What the cloud billed for the GPU machine to render a 15-minute film.
0of 392
Sample frames from the film, compared with Chrome's. None was different enough to flag.
The detail: times are inside one Modal L40S machine; a machine that has to start first adds 4 s to several minutes. Chrome is HyperFrames on 16 CPU cores, 2,146 s. Median match with Chrome's frames is 38.24 dB. Cost is from runs of a 15-minute film on 16 Nov 2026.
Formatswhat it renders
Web video
The kind coding agents write: an HTML file per scene, animated with GSAP. Point it at a HyperFrames project folder as it is. Landscape or vertical, any size; a 43-second short takes 11 to 14 seconds.
3D
3D scenes sit between your ordinary layers and follow the same timeline. Ray-traced light is there for the shots that need it.
Film
Hand it a .blend file and get the film back. Blender's own renderer draws it, so it
looks like Blender. You choose how much quality to wait for: a preview takes less time than the
film runs. At a film's full settings it is no faster than Blender.
| Quality | Ready in |
|---|---|
| preview | 38 s |
| fast | 3 min 15 s |
| full | 8 min 39 s |
How it works4 steps
Point one command at your project folder. Only the files that changed since last time are uploaded.
The film is drawn and encoded on a cloud GPU instead of being filmed in a browser. That is where the speed comes from.
Each scene is compared with Chrome on chosen frames. A scene that looks wrong is redrawn by Chrome and dropped into place.
The MP4 comes back with its sound, along with a summary of what the render cost.
Uploads and checks are remembered. Change one scene and only that scene is sent and checked again.
Pricing3 commands
Ask for a quote, take a cheap look at the first few seconds, then render the whole film with a spending cap. If it would cost more than you said, it stops.
Your coding agent can do the same: kf mcp hands it the tool.
There is no public service yet. To try it you need access to a private one.
# 1. a quote. nothing is uploaded yet
$ kf render my-project --estimate
# 2. a cheap look at the first five seconds
$ kf render my-project --seconds 5 --fallback never -o look.mp4
# 3. the whole film, capped at 50 cents
$ kf render my-project --max-cost 0.50 -o film.mp4
Status20 Nov 2026
Since you opened this page00:00
Chrome is on frame 0 of 29,676.