Understand detected issues

Last updated
February 5, 2026

When a probe runs, Uiprobe may detect visual differences between the Figma design and the live webpage. These differences are shown as issues.

Issues help you understand where the implementation differs from the design.

What an issue represents

An issue is a visual discrepancy detected during a probe run.

  • issues are tied to a specific probe version
  • a probe version may contain zero or more issues
  • issues describe what differs, not why it happened

Issues are generated automatically. You cannot manually create or place them.

Where issues appear

Issues are shown in two places:

  • on the canvas, as markers at the affected location
  • in the Issues panel, as a structured list

Selecting an issue in either place highlights it everywhere else.

Issue categories

Each issue belongs to a category that describes the type of difference detected, such as:

  • layout and spacing
  • typography
  • color
  • content & assets

You can filter issues by category in the Issues panel to focus on specific types of differences.

Issue grouping

When multiple related issues occur on the same element or within the same segment, they are grouped.

Grouping reduces visual noise while reviewing results. Individual issues are not merged or removed and remain available for inspection.

Zero-issue probes

If a probe version contains no issues, it means no visual differences were detected during that run.

Many teams use this as a signal that an implementation visually matches the design at that point in time.

Next steps

After reviewing issues, you can:

  • switch view modes to inspect differences more closely
  • re-run the probe after changes are made
  • compare results across probe versions

Continue with:

Close Modal