Groups Node

"Groups are used to keep complex node trees organized. You can select any number of nodes in the node tree and then group them to create a single node icon in the Node Editor. Groups are non-destructive and can be opened at any time."

Different from a Sub-Composition (similar purpose): a Group is simpler, with no explicit handling of named inputs / outputs. Ideal for quick clusters.

• Creation: select several nodes → right-click → Group (or the Ctrl+G shortcut).
• Category: Flow Organizational Nodes in the jayaretv classification.

Create a Group

Right-click the selected nodes in the Node Editor → choose "Group" in the contextual menu.

Expand / Edit

Right-click a group → "Expand Group" to see and edit the individual nodes in a floating window. The group hovers over the existing elements while you edit it.

Ungroup

Right-click the group → choose "Ungroup" to break it apart and get the individual nodes back in the main graph.

Groups

Local to the current comp. Quick to open / edit with Expand. Cannot be exported as a "Fusion node".

Macro

Global: saved in the Effects Library, reusable in every project. Shows up as a native node. Edited with the Macro Editor to expose the relevant parameters.

Typical workflow: Group first to prototype, then convert to a Macro for reuse across projects.

• Organizing a complex comp - split a comp with 100+ nodes into several themed Groups (Keying, Grading, etc.).
• Hiding internal complexity - expose a "black box" module without its internal details showing in the main graph.
• Local reuse - the same chain used in several places in the comp = a Group you can copy and paste.
• Review workflow - a readable main graph with a few Group modules instead of a jungle of nodes for the client review.
• Pre-Macro - Group to prototype, then convert to a Macro once it is stable.

• Non-destructive - full flexibility, ungroup at any time to get the individual nodes back.
• Name the Group - give it a descriptive name (e.g. Keying_v1) for clarity in the graph.
• Nesting is possible - a Group inside a Group works, but keep it to 2-3 levels so you don't lose the big picture.
• No performance cost - purely organizational. No overhead compared with individual nodes.
• Expand to debug - when something goes wrong inside a Group, expand it temporarily to see its content without ungrouping.
• Convert to a Macro to make it last - if the Group is validated and reusable across projects, save it as a Macro in the Effects Library.
• For team workflows, standardize Group naming (e.g. prefixes per owner) for a consistent organization.