clip

In the editing suite, everything begins with the clip — the raw material of a single camera move, a take, or an audio recording. You unpack your rushes from the camera, organize them in your editor's timeline, and each of these discrete pieces is a clip. It's the smallest meaningful unit you can grab, move, trim, and combine with others.

In editing, the clip functions like a Lego brick — self-contained enough to work in isolation, but it's only in combination with others that the story emerges. You import a hard drive with ten takes of a dialogue scene: each take becomes a clip in your bin. Some editors distinguish between a master clip (the original file reference object) and a subclip (a trimmed portion of it), but practically on set and in post-production, you talk about clips when you're swapping or rearranging material. A clip can be three seconds of music or two minutes of B-roll — the length is secondary, the demarcation is primary.

The critical distinction: A clip is not your sequence (the finished timeline with all stacked tracks) and not your entire project (the meta-level that manages all bins, settings, and renders). A clip is material. You collect clips, select, arrange, and cut them — and from that, you build sequences. Many beginners confuse this and try to export a single clip as a project, which leads to confusion in most modern NLEs.

In practice: During import, you tag clips with metadata (scene, take, camera, length) to find them later. You apply color correction or audio normalization to a clip, and this change affects every reference to it in your sequences — that's the advantage of the referential system. Simultaneously, you can place the same clip multiple times in different sequences or use it multiple times within the same sequence without wasting storage. This is the power of digital editing architecture: clips are windows to data, not the data itself.