CleanEdges

CleanEdges belongs to the Krokodove tools integrated into DaVinci Resolve 21 and Fusion 21. Blackmagic lists it among Image Pixel Tools: it removes or replaces image FRAME-edge pixels by duplicating nearby values or using a solid-color style. Do not confuse it with CleanPlate, DeltaKeyer or hair-edge cleanup inside a keyed subject.

A common use is a thin, exposed strip at the frame perimeter after a move, slight reframing, tracking or stabilization. CleanEdges can hide narrow border flaws by treating the surrounding pixels; it does not invent missing architecture, people or perspective-correct textures.

The archived Controls screenshot shows exactly three effect-specific sections: Lock, Pixels and Type. Lock is a dropdown, Pixels a numeric control and Type a Solid/Duplicate choice. Animation diamonds appear beside the controls. Settings is a separate shared tab, not a hidden set of extra CleanEdges-specific sliders.

The Lock dropdown visibly offers All Sides, Vert./Horiz. and None. These are grouping choices for border controls, not switches that enable or disable the whole node. Change one at a time and verify any revealed sub-controls in your particular Resolve build.

All Sides is a reasonable starting point for a defect affecting the entire perimeter. Vert./Horiz. suggests grouped controls per orientation; None removes grouping. Because the saved screenshot shows only the collapsed All Sides state, this article does not invent the exact secondary field labels that may appear after switching modes.

Pixels specifies the size of the treated border in pixels. The screenshot shows 10, which is merely the captured Inspector state, not a universal recommendation. The greater the repaired strip, the easier it becomes to see stretched detail or repetitive artifacts.

Type = Duplicate repeats or extends neighboring image values across the frame border. That can look reasonable for a thin sky or flat wall but may create visible streaks, repeated text, hard lines or temporal motion artifacts on detailed material.

Type = Solid produces a solid-style border fill. The official Krokodove overview calls it a solid color; there is no separate Color picker visible in the supplied Controls captures. The exact source of its color must be observed in the target Resolve version instead of fabricated.

CleanEdges is about the IMAGE boundary. Green spill around a person’s hair, light fringe around a cutout in the middle of the shot, or a hole in an alpha matte should be repaired with the keyer, Despill, Matte Control or appropriate masking tools—not by blindly raising Pixels.

When a transformation creates the defect, place CleanEdges after the actual Transform or stabilization step. Placing it before that operation will not protect against a new border being revealed downstream. Large gaps are better addressed by reframing, overscan or more sophisticated filling.

Compare Solid versus Duplicate at an identical Pixels value on the exact same frame. Inspect the corners, where the horizontal and vertical edges meet, and the most contrast-heavy subject matter near the boundary; the central Viewer region is not informative.

The original article lists an optional Effect Mask connector, but the two archived shots show only Inspector controls, not a physical Flow socket map. The mask exercise is explicitly a provisional teaching diagram: confirm port existence and behavior for Krokodove CleanEdges in Resolve 21/21.1 before treating it as a native wiring recipe.

Check motion. A pattern that hides a gap in a still frame may stretch into a prominent repeating strip when the image changes. Animating Pixels can similarly make a border pulse from frame to frame.

Distinguish frame-edge pixels, alpha transparency and Domain of Definition. A black border can actually be an exposed transparent canvas or a crop issue. Inspect Alpha and upstream bypass before expecting CleanEdges to fix it.

This is an editorial learning article, not a certified measured Resolve render. Solid color derivation, Lock layout, mask socket behavior, alpha handling and corner fill all require native testing in the target build.