What is UI Testing Inspector?
UI Testing Inspector is a free Chrome extension for visual regression testing, pixel perfect mockup comparison and responsive testing of websites. It compares a page with a saved baseline or a design mockup, audits the layout at 320, 768, 1024 and 1440 px and shows a report with findings outlined and numbered on the screenshot. It is made by Ana Do, works in Chrome 132 or later, needs no account and keeps all data in your browser. The current version is 1.2.0.
How do I compare a web page before and after changes?
Open the page, click the extension icon and click Take baseline. After you change the page, click Compare with baseline. The report opens in a new tab and lists only what changed since the baseline, with carousels, timers, videos and ads masked.
Can I compare a live page with a Figma design?
Yes. Export the frame from Figma as PNG, JPG or WebP and drop it into the Mockup tab of the side panel, or copy it as PNG and paste it there with Ctrl+V. Switch between Overlay, Slider, Toggle and Differences only views. The report lists mismatches such as shifted text, a different text size, text or background color and missing text.
How to export a Figma frame for mockup comparison
Can I do visual regression testing without CI, setup or writing tests?
Yes. Install the extension, take a baseline and compare. The extension takes both screenshots and runs the screenshot comparison for you, so there are no test scripts, no CI pipeline and no dependencies to install. If you later want checks on every commit, screenshot tests in CI are the better fit for that part.
How do I check if CSS changes broke my website?
Take a baseline of the page before you change the CSS, on localhost or on the live site. After the change, click Compare with baseline. The report shows what moved, disappeared or changed size. Then run the responsive check to see how the change behaves at 320, 768, 1024 and 1440 px.
Visual regression testing without CI or a subscription
Can I run visual regression tests on localhost?
Yes. It works on localhost, on staging behind a password and on live sites, because it captures what your browser already shows. Take a baseline on localhost, change the CSS and compare before you deploy. Chrome's own pages and the Chrome Web Store cannot be captured.
Can it find overlapping elements and clipped text automatically?
Yes. In Compare mode new overlaps are flagged as Broken layout, and clipped text and elements that overflow their container appear under Shifts and sizes. The responsive audit finds the same problems at each width, plus horizontal scroll and the element that causes it.
How does it avoid false positives from animations, carousels and ads?
When you take a baseline, the extension reads the page twice 1.5 seconds apart and masks areas that change on their own, such as carousels, timers, videos and ads. CSS animations are paused during capture. Content pushed down by an inserted block is matched with the shift, so you get one finding instead of a hundred. Usually both snapshots come from the same browser, and the report warns you if the screen scale, window width, operating system or fonts differ.
More on reducing false positives in visual regression tests
Which screen widths does the responsive check cover?
By default it checks 320, 768, 1024 and 1440 px, and you can choose your own widths. It reports horizontal scroll and the element that causes it, overflowing blocks, items that drop out of their row onto a new line, clipped text, broken images and images without alt text.
Can I test 320 px when a Chrome window cannot get that narrow?
Yes. Chrome windows cannot get narrower than about 500 px, so narrow widths are reached with tab zoom, the same method W3C uses to test Reflow. You see the browser's real layout at that CSS width, and the report notes when zoom was used.
How tab zoom reaches 320 px
Which WCAG 2.2 criteria does it check?
It checks target size (2.5.8), focus not obscured by a sticky header (2.4.11) and text spacing (1.4.12). An optional pseudo-localization test makes all text 35% longer to show what breaks after translation. It is not a full accessibility audit.
Three WCAG 2.2 criteria you can check with geometry
Where is my data stored?
Everything is stored and processed in your browser. The extension has no server and no account and sends your data nowhere, so screenshots, baselines and reports stay on your computer. It does nothing on a page until you click its icon. Your last 10 reports are kept so you can reopen them.
Is it free?
Yes. The extension is free, needs no account or subscription and works in Google Chrome 132 or later.
Do I need Playwright to test UI changes?
No. The extension is enough for checks you run by hand, such as before a commit, after a deploy or CMS update, or when you need to send a client a clear report. If you need automated checks on every commit, Playwright screenshot tests in CI are the right tool.