Jump cut: how to cut dead time out of a shot

What a jump cut is, and when it works

Wikipedia's definition is the plain one: "A jump cut is a cut in film editing that breaks a single continuous sequential shot of a subject into two parts, with a piece of footage removed to create the effect of jumping forward in time" (third party, read October 25, 2026). The same article notes that the camera position "should vary only slightly to achieve the effect", and that jump cuts "are considered a violation of classical continuity editing" while still being used on purpose.

That last point is the practical rule. A jump cut reads as a jump because the picture moved. If the subject shifted position between the two parts, the viewer sees a jump and reads it as time passing. If the picture before and after the cut is almost identical, the viewer sees a glitch and reads it as a mistake.

The opposite trick is in the same article: continuity editing uses the "30-degree rule", which says the camera has to move at least 30 degrees between two shots for them to look continuous. A jump cut is what you do when you deliberately do not move the camera, so the rule that makes a normal cut invisible makes a jump cut obvious.

Editors build the same thing with a different command: Final Cut Pro has a "Remove a gap between clips" command in its user guide (official, read October 25, 2026), and other editors use ripple delete. Either way you keep the first part, you keep the last part, and you throw away what was between them.

How to make one in three steps in your browser

The jump cut itself is not a special tool. You already have the pieces you need: cut out the dead part, then join what is left. Here is the path we ran on our test clip on October 26, 2026, with what each step produced.

1. Open the free trim tool and choose your video. It reads the length of the file in your browser; nothing is uploaded.
2. Trim the part you keep at the front: start 0, end 3.0 on our clip. The tool decoded and re-encoded exactly that range.
3. Trim the part you keep at the back: start 4.5, end 8.0. The tool reads the same file again, so the frame rate and the picture match the first part.
4. Open the free merge tool, choose the two parts in the order you want them, pick the output shape and merge. The result is one file with the dead time gone.
5. Play it once from the first frame. If the join is visible, the reason is in the table below, not in the tool.

Source: our own run on October 26, 2026, in headless Chromium against the live site, with every download checked with ffprobe 6.1.1. Method: the same 1280x720 H.264 test file went into the trim tool twice, then both parts went into the merge tool with the horizontal shape selected; each downloaded file was probed and counted.

One thing to expect: the merge tool re-encodes into the shape you pick, so two 1280x720 parts came back as 1920x1080 with the picture padded, not stretched. If you want the file to stay 1280x720, merge it and then trim it down to the shape you want, or cut the parts with a command that keeps the frame.

What the cut looks like, measured

A jump cut is easy to recognise by eye and easy to prove by number. For every frame of a file we take the difference with the frame before it and read the average brightness of that difference. Inside a shot the number is tiny. At a cut it jumps.

Source: our own measurement on October 26, 2026. Method: ffmpeg 6.1.1 with the tblend difference filter and signalstats, one value per frame, written to a text file in the published log. In the original clip the median frame difference was 0.96 and the largest was 2.26 (the rotors turn all the time, so the ordinary values are higher than for a static shot). In the cut version the largest value in the whole file was 3.13, at 3.000 s, which is exactly where the two parts were joined.

The same cut made with the browser tools gave the same answer at the same place: 3.16 at 3.000 s in a file whose largest other change was 2.21. Two different tools, one place.

The same cut with one ffmpeg command

If you work from a terminal, the cut is a trim, another trim and a join. This is the command we ran on our test file: it takes the first 3 seconds and everything after 4.5 seconds and joins them in one pass, so the file is encoded once.

The result of that command: 6.500 s, 195 frames, 494,257 bytes, 608,316 bits per second. The file is smaller than the original (569,934 bytes, 569,934 bits per second) because it is shorter; the bit rate is slightly higher, not lower.

ffmpeg -i clip.mp4 -filter_complex "[0:v]split[v1][v2];[v1]trim=start=0:end=3,setpts=PTS-STARTPTS[a];[v2]trim=start=4.5,setpts=PTS-STARTPTS[b];[a][b]concat=n=2:v=1:a=0[v]" -map "[v]" -c:v libx264 -crf 22 -preset medium jumpcut.mp4

Why the jump shows

When a join looks wrong, the cause is almost always one of these five, and none of them is the tool.

Source: our own test for the third and fourth rows (October 26, 2026, on a file with no sound). The first two rows and the last row are the usual advice in editing guides; we did not test them on a camera, because we have no camera. One thing we did see: in our clip the helicopter and its rotors move in every frame, and the cut was still the largest change in the file and visible as a jump in the position and the rotor angle (frames above), so continuous motion alone does not hide a jump cut.

Files you can download and check

Everything here was made by us on October 26, 2026 from the first 8 seconds of one CC0 clip published on Wikimedia Commons (a helicopter carrying a fire-fighting bucket over the Elbe, own work of the uploader). We removed the sound from our working file, so the cut is picture only.

• Download tool-jumpcut.mp4 (571,147 bytes): the jump cut made with the browser tools.
• Download test-results.txt: every command, every ffprobe line and every measured number.

The third file, tool-jumpcut.mp4, is the same cut made in the browser with the trim and merge tools. It is 6.500 s and 195 frames as well, but it is 1920x1080 because the merge tool padded it to the shape we picked, and the seam measured 3.16 against 3.13 for the ffmpeg file: the two paths agree to a few hundredths. Download it from the link below and compare the two joins side by side.

What we did not test

We tested two ways of making the same cut on one clip. Here is what that does not cover.

We did not test an editing application. Premiere Pro, DaVinci Resolve, CapCut, iMovie and every phone editor were not run, so this page gives no steps for their menus. The official Final Cut Pro command is named in the first section, read from Apple's guide; we did not run it.

We did not test a talking-head shot, a phone recording, a clip with music, or a clip with a fade at the cut. Our clip is one helicopter shot with no sound, which makes the cut easy to measure and easy to see.

We did not test the 30-degree rule in practice, and we did not test whether a jump cut reads well to a viewer. That is a craft judgement, and we are not the ones to make it for you.

The trim tool says its cut is not frame-exact. We checked the frame counts, and both of our parts landed on the frames we asked for, but we did not test the boundary on a file with a complicated frame rate.

What to do next

The situation you are in decides the next step.

• The join is visible because the subject did not move: cut on motion, or put a cutaway over the join.
• You need the sound to match the picture: cut picture and sound on the same frame, then listen to the first second after the join.
• You want to keep the same camera angle but hide the jump: use a cutaway, or change the framing by the 30-degree rule.
• You want the same result without a second encode: cut and join with the ffmpeg command above, which encodes once.
• You need the two parts to end up in one file at the shape you want: merge, then check the frame shape of the result, because the merge tool pads to the shape you pick.