Skip to the content
Agent Tools

Slides, from our own test

fframes vs Remotion in 10 slides

The numbers from our render test of fframes and Remotion on one 1080p scene, as slides. Every figure is from the full post, which has the method, the run file and the sources.

These slides have one link to Gamma that may later earn us a commission. It earns nothing today and is marked below.

1 / 10

fframes vs Remotion: render speed on one 1080p scene

26 timed renders in 3 sessions, plus one test of the edit loop. All runs are ours, made on 2026-10-10.

2 / 10

The result

26 of 26timed renders won by fframes

1.8 to 8.1×fframes' lead on the median, by session

9.1 s vs 16.5 smedian edit to new clip: Remotion first

3 / 10

Setup

  • Apple M5 Pro, 18 cores, 48 GB of memory
  • fframes 1.2.0, drawing on the GPU through Apple's Metal
  • Remotion 4.0.531, default settings except the quality setting
  • Runs on 2026-10-10, the intro run on 2026-10-09
  • A busy Mac: load average 65 to 78 in session 2 and 17 to 41 in session 3, where 18 means every core busy

4 / 10

Why we ran it

The maker of fframes quoted a user whose heavy 81 second video went from 700 seconds in Remotion to under 21 in fframes.

We pick a renderer for short product videos, so we timed a plain clip built in both tools. We did not rebuild the heavy video, so these slides do not test the 700 to 21 claim.

5 / 10

How each tool draws a frame

Remotion

Renders a React page in headless Chrome, screenshots each frame and hands the frames to FFmpeg. It ran 8 browser tabs in parallel by default on our Mac.

fframes

Draws each frame as an SVG straight to the GPU with Skia, the graphics library inside Chrome. No browser, no screenshot step.

6 / 10

The scene

  • 1920 by 1080 at 30 frames a second
  • A drifting glow, a headline that springs in, a growing underline, a subtitle, a frame counter, DM Sans
  • Both encode with x264 at CRF 20, medium preset; fframes also sets x264's animation option
  • Same picture: SSIM 0.997 frame by frame, where 1 means identical

7 / 10

Render times: 6 second clip

Sessionfframes, fastest / median / slowestRemotion, fastest / median / slowestMedian gap
12.3 / 2.3 / 3.4 s9.8 / 13.0 / 14.7 s5.6×
21.0 / 1.3 / 5.9 s8.1 / 10.2 / 21.1 s7.6×
30.85 / 0.89 / 0.96 s6.9 / 7.3 / 8.2 s8.1×

8 / 10

Render times: 60 second clip

Sessionfframes, fastest / median / slowestRemotion, fastest / median / slowestMedian gap
112.3 / 21.5 / 22.1 s37.3 / 38.1 / 40.2 s1.8×
26.6 / 9.0 / 23.9 s37.1 / 50.0 / 60.1 s5.6×
35.8 / 8.8 / 11.3 s30.9 / 36.0 / 40.2 s4.1×

No fframes run was slower than any Remotion run of the same clip in the same session.

9 / 10

The edit loop: Remotion is quicker

5 one-line edits, to a finished 6 second clipFastest / median / slowest
fframes: release rebuild, then render14.1 / 16.5 / 22.8 s
Remotion: render, no compile step8.1 / 9.1 / 10.8 s

Remotion was quicker in all 5 pairs. fframes renders in under a second; nearly all its time is the Rust compile.

10 / 10

Which one to pick

fframes

You render many videos from a fixed scene, such as one template with new text per customer.

Remotion

You change the scene between short renders, or your team already writes React.

Not tested: a heavy scene in Remotion, an idle machine, Linux or CI, fframes on its CPU backend, Remotion Studio's live preview.

The Gamma link below goes to gamma.app through our own address, so we can count clicks. It earns us nothing today: we applied to the Gamma affiliate program, and if Gamma accepts us, a paid plan bought through it may earn us a commission.

Slides made with Gamma, then rebuilt as this page from the post's numbers.

The direct address, with no tracking, is https://gamma.app.