We tested Remotion's transitions package on three clip pairs
Remotion's transitions package joins two scenes with a fade, slide, wipe or other presentation. We used three of them to join pairs of 6-second clips from the open film Tears of Steel, timed the renders and checked the frames in and around each transition.
Tested by us on Nov 6, 2026, on the clips and machine listed below. Every number on this page was measured in that run.
The result
All nine renders worked: three presentations (fade, slide, wipe) on three pairs of 6-second clips each. Every output came out 11.008 seconds long against the 11 seconds the timeline asks for, at 1280x720 in H.264 with an audio track, in a median of 40 to 43 seconds per render on a busy laptop CPU with no GPU. Peak memory was 3.1 to 3.7 GB.
The pictures did what the names say. The fade stayed within 3.1 to 5.7 grey levels (out of 255) of a plain straight blend of the two clips at all nine points we checked inside the one-second transition. The slide brought the new clip in from the left, and the wipe revealed it from the left, and at 30, 50 and 70 percent of the way the frames matched the expected arrangement of the two sources to within 6 grey levels. No frame inside any transition was darker than both of its source clips.
The catch is layout. Our clips are 1280x534 and the frame is 1280x720. We placed them with no styling, and the fade left the clip at the top with black below, while slide and wipe centred it with black above and below. If you mix presentations in one video, set the position yourself.
What failed or surprised us
- Our first frame check was wrong, and it said the fade failed. It stretched the 534-row sources to 16:9 and compared them with a frame that shows the clip at its real size, so every frame looked about 55 grey levels off. We threw those numbers away, re-measured against the sources at native size, and the same renders pass.
- Fade placed the clip at the top of the frame, slide and wipe placed it in the middle. All nine renders came from one composition with the same clip files; only the presentation changed. We did not find out why and we report what the frames show.
- Outside the transition, fade frames matched the sources to within 1.4 grey levels, while slide and wipe frames were 3.7 to 5.2 off. The picture looks right by eye; we did not isolate the cause.
- Slide and wipe cannot be judged by asking whether the picture drifts from A to B, because they move or cover the picture sideways. For those two we tested the arrangement of the frames instead.
- One render of the first fade pair took 56.5 seconds as its cold run against about 40 for every other run. The laptop was shared with other work.
What we tested and how
- Tool: @remotion/transitions version @remotion/transitions 4.0.541, Remotion licence: free for individuals and companies of up to 3 people, a company licence above that.
- Settings compared: Fade, linearTiming 30 frames (1 s); Slide, linearTiming 30 frames (1 s); Wipe, linearTiming 30 frames (1 s).
- Input clips: Tears of Steel, (CC) Blender Foundation, mango.blender.org, CC-BY 3.0. 60 s excerpts re-encoded to H.264 720p.
tos_a: 60 s starting at 20 s of the film, SHA-256945262dcbe106f1e...tos_b: 60 s starting at 180 s of the film, SHA-2564097773b615cddfa...tos_c: 60 s starting at 360 s of the film, SHA-2563d3a8cd015310349...
- Machine: AMD Ryzen 7 7735U (8 cores, 16 threads), integrated Radeon 680M, not used (CPU-only runs), 31.2 GB RAM, Windows 11 10.0.26300. The laptop was shared with other work, so timings are what a busy machine gives, not a clean benchmark.
- Runs: one cold run, then three timed runs per clip and setting. Run on 2026-11-06.
We wrote a small composition that follows the transitions package's documentation: clip A for 6 seconds, a 1-second linear transition, then clip B for 6 seconds, both starting 10 seconds into their files, at 30 frames per second. We rendered each presentation on three pairs of Tears of Steel clips (A to B, B to C, C to A), once cold and three more times for timing, with a pinned headless Chrome.
Checks are measured on the rendered frames against the source frames they should show: frames well outside the transition, nine frames inside it, and the rows around the clip.
Measurements by clip
Fade, linearTiming 30 frames (1 s)
| Clips | Length (s, expected 11) | Clip top edge (px of 720) | Matches the expected transition | Direction found | Dark frames in the transition | Largest picture difference outside it (grey levels of 255) | Median render (s) | Peak memory (MB) |
|---|---|---|---|---|---|---|---|---|
| tos_a to tos_b | 11.008 | 0 | yes | n/a (blend) | 0 | 1.4 | 42.3 | 3696 |
| tos_b to tos_c | 11.008 | 0 | yes | n/a (blend) | 0 | 1.4 | 40.4 | 3154 |
| tos_c to tos_a | 11.008 | 0 | yes | n/a (blend) | 0 | 1.4 | 40.3 | 3249 |
Slide, linearTiming 30 frames (1 s)
| Clips | Length (s, expected 11) | Clip top edge (px of 720) | Matches the expected transition | Direction found | Dark frames in the transition | Largest picture difference outside it (grey levels of 255) | Median render (s) | Peak memory (MB) |
|---|---|---|---|---|---|---|---|---|
| tos_a to tos_b | 11.008 | 93 | yes | from left | 0 | 5.2 | 42.8 | 3284 |
| tos_b to tos_c | 11.008 | 93 | yes | from left | 0 | 3.8 | 42.6 | 3118 |
| tos_c to tos_a | 11.008 | 93 | yes | from left | 0 | 5.1 | 41.8 | 3214 |
Wipe, linearTiming 30 frames (1 s)
| Clips | Length (s, expected 11) | Clip top edge (px of 720) | Matches the expected transition | Direction found | Dark frames in the transition | Largest picture difference outside it (grey levels of 255) | Median render (s) | Peak memory (MB) |
|---|---|---|---|---|---|---|---|---|
| tos_a to tos_b | 11.008 | 93 | yes | B on left | 0 | 5 | 40.8 | 3184 |
| tos_b to tos_c | 11.008 | 93 | yes | B on left | 0 | 3.7 | 41.7 | 3110 |
| tos_c to tos_a | 11.008 | 93 | yes | B on left | 0 | 5.1 | 40.5 | 3237 |
Reproduce it
npx remotion render src/index.ts Joined out.mp4 --props='{"a": "tos_a.mp4", "b": "tos_b.mp4", "presentation": "fade"}'npx remotion render src/index.ts Joined out.mp4 --props='{"a": "tos_a.mp4", "b": "tos_b.mp4", "presentation": "slide"}'npx remotion render src/index.ts Joined out.mp4 --props='{"a": "tos_a.mp4", "b": "tos_b.mp4", "presentation": "wipe"}'Install Remotion and its transitions package, put the two clips in the public folder, then render the composition with the clip names and the presentation as props. This is the command we ran for each render.
Method and limits
- The fade check compares each frame inside the transition with a straight weighted blend of the two source frames. The slide and wipe check compares the left and right parts of the frame with the matching parts of each source at 30, 50 and 70 percent progress. A pass is a mean grey-level difference under 10 at every point; the numbers are on the clips table.
- We did not measure the audio between the clips beyond confirming an audio track exists, and we tested only linear timing and the three presentations named above, not the package's other presentations or spring timing.
- The Remotion licence is free for individuals and companies of up to 3 people and needs a company licence above that. Check the current terms before you use it for work.
- Clips are 720p, CPU only, on a laptop that was running other work. Timings are what a busy machine gives, not a clean benchmark.
- Footage: Tears of Steel, (CC) Blender Foundation, mango.blender.org, used under CC-BY 3.0.
Page checked on Nov 4, 2026.