Probe versions

Last updated
March 24, 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 findings for that run

All findings, 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. 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 findings are detected.

Working towards no findings

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

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

No findings

No findings means the probe ran and nothing was off. That's a result worth sharing — use the Share button to send a read-only link to anyone who needs to see it.

These versions are stored like any other and can be reviewed at any time.

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 findings changes
  • markers and annotation cards update accordingly

When an older version is selected, the view toolbar shows a status indicator that you are no longer viewing the latest results. From there, you can use the provided link to return to the most recent version at any time.

Comparing changes over time

By reviewing multiple probe versions, you can see:

  • when findings were introduced
  • when findings disappeared
  • how existing findings 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 findings 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.

Related concepts

Close Modal