The Uiprobe Chrome Extension connects the page you have open in Chrome to its probes. You can create a probe, run it again and follow its progress without leaving the page you're inspecting.
It acts as a lightweight control surface that sits alongside the web app, optimized for quick checks and repeat runs during development and review.
When you open the extension on a webpage, Uiprobe first checks whether you're signed in.
If you're not signed in, the extension asks you to sign in with Figma. Once signed in, this authentication is reused across Uiprobe, so you don't need to sign in again when moving between the extension and the web app.
If you're signed in, the extension checks which probes exist for the current URL:
The extension works on webpages only. On a browser page such as a new tab or Chrome's settings, it asks you to open the page you want to compare first.
One page can have several probes, for example to compare different states, sections or viewports of the page against different Figma frames.
The list shows every probe on the current page that you can open, including probes your team members created. Each card shows:
Select a card to open the probe page. The + button opens a menu with New probe and Select from drafts. When you have no drafts, Select from drafts is greyed out.
The list shows probes that were last run from the extension. Probes created in the web app for a public URL don't appear here.
The probe page shows one probe:
From the probe page, you can:
While a probe runs, the page shows its progress in four stages: pending in queue, extracting data, mapping data and analyzing data. Open in Uiprobe stays available throughout.
When a run fails, the page says why and offers the next step. For example, when the Figma frame no longer exists, Change Figma frame lets you link the probe to another frame.
Running a probe from the extension never overwrites previous results. Each run creates a new version, just like running a probe from the web app.
Choose Create new on a page without probes, or + and then New probe on a page that has some. The probe uses the current tab as its webpage.
The Create new probe screen has four settings:
After you click Create:
Stay on the tab until the capture finishes. If you switch to another tab while the page is being captured, the capture stops, nothing is uploaded and no run is used. The extension then shows Capture stopped, and you can try again.
Capture at frame width is on by default, and we recommend leaving it on. The extension then captures the page at the width of the Figma frame, for example 1440 px for a desktop frame or 375 px for a mobile frame.
We recommend it for two reasons:
Turn the setting off to capture the page at the width of your browser window instead.
When the setting is on:
Some frames can't be captured at their width:
In these cases, the extension says so under the setting before you click Create, and captures the page at your window width. Create is never blocked. If the window can't be resized during the capture itself, the probe page notes that the page was captured at your window width.
The setting stays with the probe. When you click Run probe on a probe created with Capture at frame width on, the page is captured at the frame width again.
If you have draft probes waiting to be completed, you can pair one with the current page. Choose Select from drafts on the "No probe found" screen, or + and then Select from drafts on a page that has probes.
The list shows each draft with a thumbnail of the frame, the frame name and when it was sent. Select a draft to open the create screen with the Figma frame URL filled in and locked. The probe name starts as the draft's name and can be changed. Save to and Capture at frame width work as for a new probe. A draft sent to a team stays within that team.
Click Create to pair the draft with the current page URL. The draft converts to a standard probe, the first comparison runs automatically, and the extension opens the probe page.
On a plan with a run allowance, the extension shows how many runs you have left: on the list, on the create screen and next to Run probe. A run counts once it completes. A failed run doesn't count.
When no runs are left, you can still open the list, the probe pages and the web app. Create, Run probe and creating from a draft show a message instead of starting a run. See Plans and billing.
Probes created via the Chrome Extension can only be re-run from the extension. The web app does not show a re-run action for these probes.
To create a new version, return to the page in Chrome, open the probe from Probes on this page and click Run probe.
The exception is if you replace the webpage URL via Probe Settings with a publicly accessible URL. At that point the probe can be re-run from the web app like any other probe.
The Chrome Extension is designed to complement the web app, not replace it.
You can use the extension to:
You must use the web app to:
This separation keeps the extension fast and focused while leaving deeper analysis to the full interface.
The Chrome Extension is intentionally limited in scope.
It does not:
Its role is to make running and accessing probes frictionless while you're working on a live page.
The fastest way to see how your implementation compares to the design. No screenshots, no guessing
Compare
© 2026 · Built by UIPROBE
