Probe versions

Last updated

February 5, 2026

Probe versions represent the results of individual runs of a probe.

Each time a probe is run, Uiprobe creates a new version. This version captures a snapshot of the visual comparison between the Figma design and the live webpage at that moment in time.

Previous versions are never overwritten.

What a probe version contains

A probe version contains:

the captured visual state of the webpage
the reference design used for comparison
the set of detected issues for that run

All issues, markers, and annotation cards you see in the Probe Inspector belong to the currently selected probe version.

Creating new versions

A new probe version is created whenever a probe is run again.

(Visual reference: Run probe action in the Probe Inspector toolbar.)

This can happen, for example, when:

the implementation has changed
the design has been updated
you want to recheck the page at a later moment

Each run creates a new version, even if no visual differences are detected.

Working towards zero issues

Probe versions make it possible to iteratively reduce visual differences over time.

As issues are addressed in the implementation, running the probe again produces a new version with an updated set of issues. In many workflows, the goal is to eventually reach a probe version with zero detected issues, indicating that the live webpage visually matches the design at that point in time.

Zero-issue versions are not treated differently by the system, but they provide a clear visual signal that the comparison passed without discrepancies.

Versions with no issues

A probe version can contain zero issues.

This means that, at the time of the run, the live webpage visually matched the design within the detection limits of Uiprobe. These versions are still stored and can be reviewed later.

Navigating between versions

Probe versions can be selected from the Versions panel in the Probe Inspector.

When you switch versions:

the canvas updates to show the selected comparison
the set of visible issues changes
markers and annotation cards update accordingly

When an older (historical) version is selected, the view toolbar shows a status indicator that you are no longer viewing the latest results.

From this status area, you can use the provided link to return to the most recent probe version at any time.

This makes it easy to explore past results without losing track of the current state.

Comparing changes over time

By reviewing multiple probe versions, you can see:

when issues were introduced
when issues disappeared
how existing issues changed between runs

This historical view helps teams understand the impact of design or implementation changes without relying on memory or external tracking.

What probe versions are not

Probe versions do not:

merge or reconcile issues across runs
represent a task history or approval flow
automatically indicate whether a change is good or bad

Each version is an independent snapshot of a visual comparison.