Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use Storybook stories to capture the UI states your team cares about, compare their rendered pixels with approved baselines, and review every difference before accepting it. Run checks during development and in CI before merge. For direct design comparison, embed Figma designs in Storybook or link published Storybook stories to Figma components with Storybook Connect.
What visual testing checks
Storybook describes the core check this way: “Visual tests compare the rendered pixels of every story against known baselines.” The comparison can flag visible changes in layout, color, size, and other details. It is a regression signal, not proof that behavior or accessibility is correct.
As an Amazon Associate I earn from qualifying purchases.
Visual tests and markup snapshot tests answer different questions. A markup snapshot compares rendered HTML; a visual test compares rendered pixels. Use visual checks alongside interaction, functional, and accessibility tests rather than as a replacement for them. Storybook’s visual testing guide
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Set up a repeatable Storybook review loop
- Create stories for meaningful states. Include variants, important design states, and cases that have previously regressed. A well-chosen story set becomes reusable visual test coverage.
- Configure visual testing. Storybook documents the official
@chromatic-com/storybookaddon workflow: install and configure the addon, link the project to Chromatic, and create an initial baseline build. The addon listing states that it requires Storybook 7.6 or later and access to a Chromatic project; confirm current requirements and setup before adopting it. Storybook setup guide · Addon listing - Run checks while developing. Review stories flagged for visual changes. Inspect the diff to identify what changed instead of accepting it automatically.
- Resolve each difference. If the appearance change is intended, accept it as the new baseline. If it is unintended, correct the implementation or story and run the comparison again. Approval records the team’s acceptance of the appearance; it does not establish that the new design is correct.
- Run checks in CI before merge. Storybook recommends combining local checks with CI. Pull or merge requests can show a UI Tests check for errors or changes requiring review; teams can choose to make the provider check a merge requirement.
Choose representative coverage
Match browser, viewport, and theme coverage to the experiences your UI supports. The addon listing describes multiple browsers, viewports, and themes, but the exact available matrix depends on current product documentation and project configuration. Avoid treating one captured configuration as coverage of every supported environment.
#1 Best Overall
Connect Figma designs and Storybook stories
Storybook documents two integration directions. Choose based on whether the design reference should appear beside the implementation or the implementation should be accessible from Figma.
| Direction | What it does | Setup and limits |
|---|---|---|
| Figma design in Storybook | Displays a Figma frame alongside a story using a design parameter containing the Figma URL. |
Use the design integration instructions for the story configuration. Storybook design integrations |
| Storybook story in Figma | Uses the Storybook Connect Figma plugin to link stories to Figma components, variants, and instances. Storybook says linked stories reflect later publishes on the linked branch. | The documented workflow requires a Storybook published to Chromatic: choose the branch, copy the story URL, and paste it into the plugin. The plugin does not support linking stories to Figma layers. Storybook design integrations |
| Third-party in-browser comparison | The Storybook Addon Figma Sync listing claims overlay, side-by-side comparison, and pixel-diff views. | These are the addon author’s claims, not independent validation. Check current maintenance, compatibility, and Figma access requirements before relying on it. Addon listing |
Choose the right comparison workflow
Baseline testing and design review overlap, but they are not interchangeable. Use the following questions to decide what the team needs:
- Purpose: Are you detecting changes against an accepted implementation baseline, or checking implementation against the original Figma design?
- Workflow location: Should review happen in Storybook and CI, should the design reference be embedded in Storybook, or is an in-browser overlay useful?
- Coverage: Which stories, component states, browsers, viewports, and themes matter for the supported experience?
- Review ownership: Who approves intentional changes, where is the baseline maintained, and should CI block merging until review is complete?
- Dependencies: Does the setup meet the Storybook version requirement, require Chromatic project access or a published Storybook, or depend on a third-party addon whose compatibility must be checked?
Capture a page independently with a screenshot API
A screenshot API can capture a URL for a one-off reference, a page outside Storybook, or an artifact in a separate workflow. It does not replace Storybook’s story-based baselines or Figma design integrations: it captures a page, while those workflows connect component states, baselines, and design references. ScreenshotNeo is a website screenshot API and MCP server; its API accepts a URL and returns an image or PDF.
Recommended Free Tools
Or skip the browser setup
Use a GET request to capture a page. Add your ScreenshotNeo API key and substitute the target URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie and consent banners are accepted like a visitor and 60+ known consent platforms, newsletter popups, and chat widgets are removed before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month without a card.
Quick Recap
Troubleshoot visual-test setup and review
- The addon setup does not match your project: Check the current addon prerequisites and your Storybook version; the listing states Storybook 7.6 or later and Chromatic project access.
- A change is flagged but its cause is unclear: Inspect the story’s visual diff, then check the rendered state and relevant story configuration before deciding whether to accept it.
- The baseline was updated for an unintended change: Correct the implementation or story and rerun the comparison to produce a baseline reflecting the intended appearance.
- CI reports changes that have not been reviewed: Review the flagged stories in the pull or merge request workflow; if your team requires approval before merging, confirm the provider check is configured as required.
- A Figma link does not show the expected Storybook story: For Storybook Connect, verify that the Storybook is published to Chromatic, the intended branch was selected, and the story URL was pasted into the plugin. Figma layers are not supported as link targets.
- A Figma Sync addon feature or setup is unavailable: Recheck the listing and current compatibility, maintenance, and Figma access requirements; the listing’s feature description is the addon author’s claim.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
