Sub-Composition Node

A Sub-Composition shows up in the main graph as a single node, but contains a potentially complex sub-graph inside. The inputs / outputs exposed on the container are wired to special nodes (Group Inputs / Group Outputs) inside.

It lets you build a hierarchy. For example: a "full keying" composite with 8-10 nodes can become a single "KeyingModule" node in the main graph. It improves readability, makes reuse easier, and hides the complexity from downstream artists.

• Creation: select several nodes → right-click → Group (or the shortcutCtrl+G).
• Effects Library: Tools > Flow > Sub-Composition to insert an empty one you fill in.

1. Select the nodes to wrap (selection rectangle or Ctrl+click).
2. Right-click → Group.
3. The cluster is replaced by a single container node.
4. To edit the contents: double-click or right-click → Expand Group. A new view opens.
5. Inside, the automatically created inputs / outputs expose the external connections.
6. Ungroup to undo the wrapping and get the individual nodes back.

Sub-Composition (Group)

Local to the current comp. Editable from any project where the comp is open. Not easy to export.

Macro

Reusable everywhere: saved in the Effects Library, available from every project. It shows up like a native Fusion node. Ideal for team modules.

Typical workflow: create a Sub-Composition first to prototype, then convert it to a Macro if you want to reuse it across projects.

• Making a complex comp modular - split a comp with 100+ nodes into several themed Sub-Compositions (KeyingModule, GradingModule, IntegrationModule).
• Local reuse - the same chain used in several places in the same comp = a copy-pasted Sub-Composition keeps things consistent.
• Team templates - standardized Sub-Compositions (e.g. "FilmEmulation_v2") shared through copy / paste.
• Hiding internal complexity - expose only the relevant parameters on the surface and hide the implementation details inside.
• Review workflow - a readable main graph with a few "black box" modules instead of a jungle of nodes for a client review.
• Pre-Macro - a Sub-Composition first (prototyping), then a conversion to a Macro once it is stable for global reuse.

• Name the Sub-Composition - a descriptive name (e.g. Keying_v1) instead of the default Group1 = a much more readable graph.
• Named Inputs / Outputs - rename the container's inputs / outputs to make clear what they represent (e.g. "Input_Plate", "Input_Greenscreen").
• Expose key parameters - expose the internal parameters at the container level so they are accessible without entering the sub-graph.
• No performance cost - a Sub-Composition is purely organizational. No overhead compared with individual nodes.
• Ungroup to debug - when something goes wrong in a Sub-Composition, Ungroup it temporarily to see the whole graph.
• Nesting is possible - a Sub-Composition inside a Sub-Composition. Keep it to 2-3 levels so you do not lose the big picture.
• Convert to a Macro to make it last - if the Sub-Composition is approved and reusable, convert it to a Macro for the Effects Library.
• For team workflows, standardize with Underlays + consistent naming to make sharing easier.