Overview
Sticky Note appears as a colored rectangle in the node graph holding a title and free text. No input or output - it lives outside the image flow. Its value is purely organizational.
It lets you document an area of the graph ("This is where we handle the green screen"), explain a non-obvious choice ("Intentional blur to match the plate"), or leave a TODO ("Revise after the client brief").
Where to find this node
- Effects Library:
Tools > Organization > Sticky Note - Quick add: right-click in the Node Editor →
Add Tool > Organization > Sticky Note - Typical shortcut: the S key (depending on the project mapping).
Sticky Note vs Underlay
- Sticky Note
- A discreet post-it, fixed size, mostly holding text. It does not group nodes, it only annotates.
- Underlay
- A visual grouping area that encloses several nodes. It gives a cluster a title and a background color.
Rule of thumb: a one-off note → Sticky Note. Visually grouping several nodes → Underlay.
Setup
Annotated keying workflow:
[Sticky Note "Cleanup keying"]
│
[MediaIn] → [Color Corrector] → [Ultra Keyer]
│
[Sticky Note "Spill removal" ]
Documentation for the client:
[Sticky Note "Final version - Brief 2024-04-12"]
[MediaIn] → [rest of the comp]
TODO list inside the comp:
[Sticky Note "TODO:
- Fix the roto at frame 240
- Update the grade after the client brief
- Check the shot match with shot B"]Controls tab
- Title (default: "Note")
- Title of the sticky, shown in bold at the top. Keep it short and descriptive.
- Comment (default: empty)
- The comment text, multi-line. It can hold paragraphs, lists, etc.
- Color (default: Yellow)
- Background color of the note. Use different colors for different categories: yellow = info, red = warning, green = done, blue = todo.
- Width / Height
- Size of the sticky in pixels. Adjust it to show more content without scrolling.
Use cases
- Documentation for collaborators - explain the reasoning behind a complex chain to a teammate who will take over.
- Versioning notes - note the version date, the matching brief, and the changes since the previous version.
- Built-in TODO list - a sticky with the remaining tasks, visible as soon as you open the comp.
- Critical warnings - a red sticky to highlight something not to forget ("Do not change - tracking approved by the client").
- Explaining a non-obvious choice - why this 0.7 blur? Why this color correction at -10 saturation? A sticky keeps people from drawing the wrong conclusions.
- The equivalent of a code comment - like comments in code, to explain the intent rather than the mechanics.
Tips
- Keep the title short - the title stays visible even when the sticky is small. 2-4 words max.
- Consistent color code - pick a team convention (red = problem, green = approved, yellow = info, blue = todo) and stick to it for readability.
- Next to the relevant node - place the sticky right next to the node (or group) it documents. Not isolated at the bottom of the graph.
- Multi-line for TODOs - the Comment supports multiple lines. List items cleanly rather than writing one long sentence.
- No impact on performance - purely visual, it costs nothing at render time. Add as many as you need.
- No markdown - the text is plain text, with no formatting. Use ASCII separators ("---", "*") if you need visual structure.
- For large visual groupings, prefer the Underlay, which encloses several nodes in a titled colored area.
