Start with the pixel result you want, not the mode name. For overall darkening, compare Darken, Multiply, and Color Burn; for brightening, compare Add, Lighten, Screen, and Color Dodge; for contrast, compare Overlay, Hard Light, and Soft Light; for a color-only change, use the HSL family and identify which component comes from each layer. In every case, confirm the blend layer, base layer, Composition Track, and Opacity. The examples below are hypothetical checks based on the official definitions, not software test results.
Judgment and steps
Kdenlive describes the upper track as the blend or active layer and the lower input as the base layer. A composition starts on the blend layer, while Composition Track determines which track supplies the base when it is not simply the track immediately below. The official blending-mode documentation groups modes by result, which is a useful starting point but does not make every mode in a group equivalent.
- State the visual trigger precisely. Choose Darker when bright areas should not become brighter and the darker value should win. Choose Multiply for a generally darker result where white in the blend layer leaves the base unchanged. Choose Color Burn when darkening should also increase contrast. For lightening, Add sums color values, Lighten keeps the lighter value, Screen brightens through inverted multiplication, and Color Dodge makes the base increasingly lighter as the blend layer becomes brighter.
- For contrast, use Overlay when the base determines whether the operation behaves like Multiply or Screen, Hard Light when the blend layer's brightness determines that behavior, and Soft Light when a gentler luminance-based change is intended. Treat these as different decisions, not interchangeable presets.
- For color attributes, use HSL hue to take hue from the blend while preserving base luma and saturation; HSL saturation to take saturation; HSL color to take hue and saturation; or HSL luminosity to take luma while preserving base hue and saturation. Kdenlive's composition terminology may show counterparts such as Hue, Saturation, and Color; verify the actual Composition Type label.
- Select the composition and inspect its Blend mode or Compositing method. Confirm the blend layer, choose the intended Composition Track, and then adjust Opacity to control how strongly the selected operation contributes. Opacity changes the amount of compositing; it does not replace choosing the correct operation. The Composite and Transform documentation lists several of these methods and identifies Opacity as the compositing-strength control.
Acceptance worksheet
Use a small, representative section containing shadows, highlights, a neutral area, and one colored object. The following is an author-created comparison worksheet, not a guarantee of Kdenlive output or a reported measurement.
| Hypothetical observation | First choice | Why | If it fails, change direction |
|---|---|---|---|
| A white title should leave the base nearly unchanged while a gray texture darkens it | Multiply | White is neutral in the documented multiplication relationship; darker blend values reduce the result | If the title must win by minimum value, compare Darken |
| A pale flare should brighten the background, with stronger effect where the flare is brighter | Screen or Color Dodge | Screen brightens through inverted multiplication; Color Dodge responds more strongly to bright blend values | If highlights become too forceful, compare Screen or Add with lower Opacity |
| Midtones should gain depth while dark and light areas move in opposite directions | Overlay | Its behavior changes around the base brightness | If the blend texture should control that split, compare Hard Light |
| A base portrait should keep its luminance while a tint supplies hue and saturation | HSL color | The base luma is preserved while blend hue and saturation are adopted | If only hue should change, use HSL hue |
Judge the intended local regions and their boundaries, then record which track supplied each input. Do not infer a mode from node color alone; use the actual type label.
Limits and next step
The documentation defines the operations and layer roles, but it does not promise that one mode will preserve detail, avoid clipping, or look natural on every clip. Add, Color Dodge, and Burn can produce strong changes in bright or dark regions; that is a reason to inspect the result, not proof that a particular value is wrong. If the selected mode misses the intent, first verify Composition Track and input order, then compare the neighboring mode in the same result family. If the operation is right but too strong, reduce Opacity. If the desired control is unavailable in the chosen composition type, use a documented composition that exposes the required method rather than treating an unrelated mode as an equivalent.
Three short questions
Does Opacity fix a poor mode choice?
No. It controls the amount of the selected compositing method. Choose the operation first, then use Opacity for strength.
Why does the same mode look different after changing tracks?
The blend layer and base layer have different roles, and Composition Track can select a different base. Changing either input changes the comparison.
Should I use HSL color for every tint?
No. Use it when hue and saturation should come from the blend while base luminance remains. For hue alone, choose HSL hue; for a luminance change, choose HSL luminosity.
Sources and next step
- Blending Modes — Kdenlive 26.08 Manual 26.08 documentation
- Composition Blend Modes — Kdenlive 26.08 Manual 26.08 documentation
- Composite and Transform — Kdenlive 26.08 Manual 26.08 documentation
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.