Soupbear - Blueprint Diff Tool

Blueprint Diff Tool provides a snapshot-based workflow for tracking, comparing, and restoring Blueprint changes in Unreal Engine. If you've ever needed to understand how a Blueprint evolved over time, or review what changed since your last refactor, this tool gives you clear visibility without requiring Perforce or external diff tooling.

The system lets you create named snapshots of any Blueprint, compare snapshots against each other, compare a snapshot to the currently open Blueprint, view detailed text-based change reports, and (when desired) restore a Blueprint to a previous state with automatic backup protection. A visual overlay mode highlights differences directly in the Blueprint graph editor, making it easy to see added, removed, and modified nodes and connections at a glance.

Key Features

Snapshot Management

  • Create snapshots of individual Blueprints with optional notes

  • Bulk snapshot all Blueprints in the project

  • Search and browse Blueprint assets

  • Snapshots are stored as portable text files for versioning and archival

Diff & Compare

  • Compare two snapshots to see changes in node structure, pin values, and wiring

  • Compare snapshots to the live Blueprint currently open in the editor

  • View a structured text diff report for review or documentation

Visual Graph Highlighting

  • Highlight added, removed, and modified nodes directly in the Blueprint graph

  • Display removed nodes as temporary ghost outlines for context

  • Show removed and changed connections with ghost wires

  • Press ESC to clear the visualization at any time

Restore & Version Safety

  • Restore a Blueprint to a previous snapshot when needed

  • Automatic backup ensures changes can be reversed safely

  • Event nodes are preserved during restore to avoid breaking Blueprint entry points

  • Blueprint is automatically refreshed and recompiled after restore

When This Helps

  • Solo developers needing quick and easy visual version control

  • Reviewing changes after long development sessions

  • Understanding refactors or reorganized logic

  • Rolling back experiments without relying solely on source control

  • Working in teams where members use different version control systems

  • Maintaining clarity and confidence while iterating on complex Blueprint graphs

If this was priced lower I’d totally try it as a lightweight source control. The idea has potential.

Thank you for your input!

I think I agree with your comment so I’ve reduced the price a bit to help more people get a chance to try it out.