Findings

Last updated

March 23, 2026

Findings are the visual differences Uiprobe detects when comparing a Figma design to a live webpage. Each finding shows where the implementation differs from the design — what's different, and by how much.

For each finding you can see:

Where the difference occurs on the page
What property or element is visually different
How the design and webpage values differ

The Findings panel

All findings are listed in the Findings panel, organised into three sections:

Properties — verified differences in visual properties like size, typography, style, and content
Spacing — verified differences in spacing between elements
Unverified — elements the system detected but couldn't fully map to the design

Properties

Verified property-level differences between the Figma design and the live webpage. Properties findings are grouped into four categories:

Size — differences in rendered element width or height. Padding differences are detected as element size, not as CSS padding values.
Typography — differences in font size, family, weight, line height, letter spacing, casing, or text decoration. Text color is not included here — it appears under Style.
Style — differences in color, border width, border style, border radius, opacity, and text color.
Content — differences in rendered text or images. Elements that are missing or extra appear in the Unverified section rather than here.

You can filter Properties findings by category using the filters in the Findings panel.

Spacing

Verified differences in spacing between elements. Spacing findings are displayed with distance-line indicators on the canvas, showing direction and magnitude.

A tolerance filter controls which spacing deviations are surfaced. Three levels are available:

Pixel-perfect — all detected deviations
Standard — moderate deviations (default)
Flexible — significant deviations only

Unverified

Unverified findings are shown separately. These are elements the system detected but couldn't fully map to the design. It's worth taking a look to confirm the element mapping is correct and the detected difference is what you'd expect.

Unverified findings come from two sources:

Low-confidence property findings — detected but could not be fully mapped; follow the same structure as Properties findings
Missing element findings — an element present in Figma has no match on the webpage, or vice versa; identified by element type (text, image, shape) and which side it came from

Findings on the canvas

Findings are visualised on the canvas using markers. Each marker indicates where a finding is located. Selecting a marker opens the corresponding annotation card, which shows the finding details and the expected → actual comparison values. When multiple findings exist on the same element, they share a grouped marker. When markers would otherwise overlap on the canvas, they appear clustered.

Findings groups

When multiple related findings occur together, they are grouped for review.

Two grouping types exist:

Element findings — multiple findings on the same element, grouped by element identity.

Recurring findings — multiple findings with the same property and the same difference, spread across different elements on the page. When these are present, the Probe Summary shows how many findings belong to how many distinct patterns.

Grouping does not merge or remove individual findings. Selecting a group in the Findings panel selects the first child finding — both in the panel and on the canvas.

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.

Findings across versions

Findings belong to a specific probe version. When you switch to a different version in the Versions panel, the set of visible findings updates to match that version.

This makes it possible to see when a finding appeared, when it was resolved, or how it changed — without overwriting earlier results.

What findings are not

Findings cover visual differences only. They don't represent bugs, accessibility problems, or tasks — and they don't assign ownership to anyone.