Snapshot Node

Overview

Stores the current result for comparison. Evaluation continues, allowing the stored reference and live current value to be viewed side by side. It is ideal for deciding whether a result looked better before or after an adjustment.

Usage tips

• The basic workflow is to capture before adjusting colors or filters, then compare before and after while changing parameters.
• Do not confuse it with bake_subgraph: Snapshot does not stop evaluation. Bake for performance; Snapshot for comparison.
• Recapture when the current good state should become the new reference.

Related nodes

• bake_subgraph — fixes a result and stops evaluation
• preview — displays the comparison
• patch_toggle — compares manual corrections ON/OFF, a different comparison axis

Read this first

• Snapshot is for comparison.
• Unlike Bake or Freeze, it does not stop reevaluation.
• It compares a stored value with the live current value.
• The most common use is retaining a reference for before/after comparison.

When to use it

• To store a result once and compare it after later changes
• To compare before and after color or filter adjustments
• To inspect changes in keyframes or procedural results
• To keep the current good state as a comparison reference

When not to use it

• When you want to stop reevaluation itself
  • Use BakeSubgraph or FreezeNode.
• When you want to restore the graph settings from this moment
  • SnapshotNode stores a result, not settings.
  • A Preset or Variant is a more natural fit.

How to use

1. Place SnapshotNode at the output of the result you want to compare.
2. Press Capture in the Inspector.
3. output becomes the live current value and snapshot becomes the stored value.
4. Compare current and snapshot in Preview compare.
5. Press Recapture to update the comparison reference.

Example

• PixelCanvas -> Brightness -> SnapshotNode -> Preview

Pressing Capture the first time stores the brightness result at that moment in snapshot. After changing Brightness:

• output
  • the new current result
• snapshot
  • the previously stored result

This makes it suitable for before/after comparison.

What is stored

• The node stores the output result at that moment.
• It stores an image for Image, a Path for Path, and a number for a numeric value.
• It does not store upstream node settings themselves.

SnapshotNode may let you return to an earlier appearance, but it does not restore the settings themselves.

Common workflow

• Press Capture before adjusting Brightness.
• Compare current and snapshot after the adjustment.
• If you dislike the change, manage state with Preset / Variant.

This division of responsibilities is the most natural.

Differences from Bake / Freeze

• Snapshot
  • For comparison
  • Does not stop reevaluation
• Freeze
  • Temporary fixation
  • Stops reevaluation while active
• Bake
  • Used as a baked deliverable

Notes

• Snapshot also appears as a dedicated compare candidate for easy Preview comparison.
• v1 provides the minimal checkpoint feature set.
• SnapshotNode alone cannot restore upstream settings.
• Think of restoring settings as the responsibility of Preset / Variant to avoid confusion.
• If stored data is malformed, disagrees with its declared type, or uses an unsupported newer version, the live output continues with a warning and no snapshot output.