Cutsio Blog

How to use node-based compositing in DaVinci Resolve Fusion

DaVinci Resolve Fusion uses a node-based workflow for visual effects compositing where tools are connected in a flow chart. This guide covers the five basic operations, node tree organization, and how nodes compare to layer-based systems.

How does node-based compositing work in DaVinci Resolve Fusion?

Fusion uses a flow chart called a node tree that visually maps how effects are connected. Nodes represent individual tools — media inputs, effects, masks, transforms, and outputs. You build composites by stringing nodes together. The MediaIn node represents your clip from the edit timeline. To add a blur, drag the Blur node from the toolbar and connect its input to the MediaIn output. Tools can be combined in any order for unlimited creative possibilities.

Nodes are like building blocks. Each node performs one specific operation and passes the result to the next node. Because nodes are connected visually, you can see the entire processing pipeline at once. There are no hidden menus or nested layer stacks.

For more DaVinci Resolve tips, read our guide on DaVinci Resolve AI Tools for Colorists and Editors.

Master Fusion effects with How to use node-based compositing in DaVinci Resolve Fusion.

What are the five basic operations in Fusion compositing?

All Fusion work is built on five fundamental operations:

Merge images: The Merge node layers images together. Connect a background image to the yellow input and a foreground image to the green input. The foreground is composited over the background using the selected blend mode and opacity.

Insert effects: Over 200 tools are available in the effects library. Drag a tool into the node tree between the MediaIn and the Merge. Add a blur, a glow, a color correction — each tool operates independently.

Create masks: Masks define where effects are applied. Draw a mask shape using the Polygon or B-Spline tool and connect it to the blue mask input of any effect node. The effect is limited to the masked area only.

Adjust settings: The inspector on the right displays all controls for the selected tool. Adjust parameters and animate them using keyframe buttons.

Fine-tune animations: The Spline Editor and Keyframe Editor give advanced control over animation curves and timing.

Why are nodes easier than layers for complex composites?

Layer-based compositing stacks adjustments on top of each other, with each layer modifying everything below it. To change the order, you must restructure the entire layer stack. To isolate an effect to a specific area, you need an adjustment layer with a mask.

Node-based compositing represents each operation independently. To change the processing order, reconnect the nodes. To isolate an effect, add a mask node and connect it to the effect's mask input. Nodes can be bypassed individually without affecting other operations. Nodes can be connected in parallel for independent processing, then combined at a Merge node.

| | Nodes (Fusion) | Layers (traditional) |

|---|---|---|

| Processing order | Visible node connections | Stack order |

| Bypass an effect | Bypass the node | Toggle layer visibility |

| Isolate to area | Connect mask to specific node | Adjustment layer masks |

| Reorder operations | Reconnect nodes | Restructure stack |

| Parallel processing | Yes — parallel branches | No — sequential only |

| Reuse effect chains | Yes — copy node trees | Manual reconstruction |

How do you organize node trees for complex composites?

Label each node by selecting it and pressing F2. Group related nodes using the pipe router or by creating a macro — select the nodes, right-click, and choose "Create Macro." The macro appears as a single node representing the entire subtree.

Use different colors for different node types by right-clicking and selecting a color from the context menu. Color green for color correction nodes, blue for masking, red for effects. The visual organization makes the node tree scannable at a glance.

For editors who pre-select footage in Cutsio, the clips arriving in the Fusion page are already curated selects. Your node tree processes only the content that makes the final edit, reducing complexity and render time.