Component

You're sitting at your compositing setup and need to adjust a single effect without destroying the entire layer – this is precisely what components are for. A component is the smallest, independently controllable unit of work in your composite. It can be an image, a text layer, a particle effect, a glow, or even just a rotation keyframe. The crucial part: you pack it into a container, give it a hierarchy, and then manipulate it individually without affecting neighboring layers.

In practice – let's take Nuke or After Effects – for a shot with an exploding window, you create multiple components in parallel: one for the shattered glass as a particle element, a separate one for the smoke effect with its own opacity and motion blur, a third for light flares dancing on the window frame. Each component has its own render order, its blend mode, its masks. You can accelerate the particle component by 20% without changing the smoke timing. That's the point: modularity through isolation. If the supervisor says "The glass debris needs to be less dense," you only change the corresponding component, not your entire composite.

Components are often confused with channels or passes – this is a mistake. A channel is mathematical information (RGB, Alpha, Depth), a pass is an entire render layer from the 3D system. A component, however, is your organizational structure in the editing workflow. You could name a component "Lens Flare," which internally combines three different passes: a glow pass, a diffraction pass, plus a self-drawn shape layer. The component is the overarching unit into which you pack everything.

For VFX-heavy shots, you need this granularity. You're not in Photoshop, where you simply stack layers – you need dependencies, keyframe control at the effect level, and rapid iteration. If your compositing supervisor wants to disable the "Muzzle Flash" component to test how the shot looks without it, you click a button. No recalculation, no dependency errors, no 40 minutes of render time wasted.