An unwanted black frame is almost always a hole in the timeline. Somewhere a trim left one frame with nothing under it, and the export rendered that nothing as black.
One frame lasts around a 25th of a second, and most people won’t consciously see it. The client watching the final cut for the fifth time will, and so will a broadcaster’s QC.
In short
- Most black frames come from timeline gaps after late trims, cutaways a frame too short or export ranges that run past the last clip.
- Detection tools measure each frame’s brightness and flag dark runs, then a person decides whether each one was intentional.
- Search for gaps before every export, not only the final one.
- Check the exported file too, stepping frame by frame through every cut that changed.
What counts as an unwanted black frame
A black frame is a frame where the whole picture sits at or near video black. In 8-bit video in the standard (limited) range, black sits at code value 16 rather than 0 (a full-range file uses 0), so detection tools look for frames close to the file’s black level instead of absolute zero.
It’s unwanted when nobody put it there on purpose. A fade to black between sections, a beat of darkness before the logo or the black a broadcast spec asks for at the head of a programme are all deliberate.
Its cousin is the flash frame: one or two frames of the wrong picture at an edit point, usually left over from a clip that used to be there. Both come from the same kind of timeline accident, and both get caught the same way.
Where black frames come from
Most of them get in during the last round of small changes, when the edit is nearly locked and nobody is watching the whole timeline anymore. The usual causes:
- A one-frame gap after a trim or a move. Snapping was off, a clip got nudged, or a lift left a hole that a ripple delete would have closed.
- A cutaway that’s a frame too short. B-roll on an upper track meant to cover a lifted section of an interview, ending one frame before the hole underneath it does.
- An export range past the last clip. The out point sits a frame after the picture ends, or music runs a few frames longer than the last shot, so the sequence ends on black.
- A nested sequence or compound clip with empty frames at its start or end, which carries that black into every edit that uses it.
- A damaged source file or a failed render. Less common, and it only shows up in the exported file, never in the timeline.
How black frame detection works
Detection tools measure the brightness of every frame and flag runs that stay below a threshold for longer than a minimum duration. The threshold is usually set close to video black, and many tools also ask what share of the picture has to be dark before a frame counts.
The two settings pull against each other. Set the threshold too high and every night scene gets flagged. Set the minimum duration too long and the single black frame, the one you were looking for, slips through.
Good tools also look at how the black starts and ends. A fade dims over several frames, while a gap goes from a full picture to black in one, so a hard edge is a much stronger sign of a mistake.
Flash frames need a different test. A tool looks for one or two frames that differ sharply from the frames on both sides while those neighbors match each other. A normal cut changes once and stays changed, so it doesn’t match that pattern.
How to find them before you export
Search for gaps in the timeline before every export, not only the final one. Most editing software has a way to do it:
- Premiere Pro: Sequence > Go to Gap > Next in Sequence jumps from one gap to the next.
- DaVinci Resolve: Edit > Delete Gaps closes every gap at once. Check what moved afterwards.
- Final Cut Pro: an empty space in the primary storyline is a gap clip you can see and select.
Then check the exported file itself. Step frame by frame through every cut touched this round, a couple of frames on each side, and look at the first and last frames of the video.
Watch the export once at normal speed as well. A stray frame that’s easy to miss in the timeline is often easier to catch in a clean playback, and the final QC checklist covers the rest of that watch.
How to keep them out
A few habits in the edit prevent most black frames.
- Keep snapping on when you trim, and use ripple delete instead of lift when you remove a section.
- Make cutaways cover the whole hole, with a frame or two of overlap on each side.
- Set the export range to where the picture ends. If you want black at the tail, put it there on purpose.
- Check again after any late change, even a one-frame trim requested on delivery day.
If a black is intentional, say so in the notes that go with the cut. Whoever reviews or QCs it next won’t waste time on it, and nobody “fixes” a pause the director wanted. More on editing mistakes clients notice is in video editing mistakes to avoid.
How this works in RecReview
In RecReview, AI Review runs on a version when you ask for it, or on every upload if automatic AI Review is on for the workspace. It reads every frame of the uploaded file looking for the short defects that slip past at normal speed.
It flags a short black gap with a hard edge, from four tenths of a second up to a second and a half, and leaves out fades and the first and last half second of the video.
It also flags a stray frame inside a shot, one or two frames that differ from identical frames before and after, and a brief freeze between moving shots.
Each finding comes with the exact time of the frame and shows up as a marker on the player bar. A second check looks at the frames around it, and if it looks deliberate, like a fade, it moves to a collapsed list of low-confidence checks instead of disappearing.
It doesn’t catch everything. A single black frame on a hard cut between two different shots can get past it, so step through the cuts yourself.
In the player, the arrow keys move one frame at a time, C opens a comment on the current frame, and choosing Original in the quality menu plays the file you uploaded instead of the streaming copy.
