Use Storybook stories as repeatable UI states, compare their rendered screenshots with accepted baselines, and review each visual difference before approving it. For design review, you can also display Figma designs in Storybook or link published Storybook stories to Figma components. Run checks during development and in CI before merging; visual comparison complements, rather than replaces, behavior and accessibility tests.
What visual testing checks
Storybook visual tests capture the rendered pixels of stories and compare them with known baselines. As Storybook puts it, “Visual tests compare the rendered pixels of every story against known baselines.” The story collection becomes a repeatable set of cases for reviewing components and their important states.
A visual difference can reveal a change in layout, color, size, or another visible detail. It is a signal for review, not proof that an interaction works or that a component is accessible. Markup snapshot tests answer a different question: they compare rendered HTML rather than rendered pixels. Use the method that matches the risk you need to check, and retain separate functional and accessibility checks where those matter. Storybook visual testing documentation
Set up a repeatable Storybook review loop
1. Create stories for meaningful states
Add stories for the component variants and UI states that matter to your product. Include states that are important to the design or have previously regressed; a screenshot comparison can only cover states represented by the stories you test.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
2. Configure visual testing
Storybook documents visual testing with the official @chromatic-com/storybook addon. Install and configure it, link the project to Chromatic, and create an initial baseline build. The addon listing states a prerequisite of Storybook 7.6 or later and access to a Chromatic project. Check the current setup instructions and compatibility for your project before installing, since requirements can change. Official addon listing
3. Run checks while developing
Run visual tests as you work. When a story is flagged, inspect its visual diff and decide whether the changed appearance is intentional. If it is, accept the new baseline; if not, correct the implementation or story and run the comparison again. Accepting a baseline records approval of the new appearance—it does not independently establish that the design is correct.
4. Add the review to CI
Pair local checks with CI checks before merge. Storybook documents a UI Tests check on pull or merge requests that can surface errors or visual changes for review. A team can choose to make the provider check required before merging. Decide who approves intentional changes and whether unresolved reviews should block merges. Storybook visual testing documentation
5. Choose coverage deliberately
Match browser, viewport, and theme coverage to the experience your project supports. The addon listing describes multiple browsers, viewports, and themes, but the available matrix depends on current product documentation and project configuration. Ensure stories cover the combinations that are material to your UI rather than assuming a single render represents every supported experience.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Connect Figma designs and Storybook stories
Show a Figma design alongside a Storybook story
Storybook’s design integrations documentation describes adding a design parameter to a story and supplying a Figma URL. This lets a reviewer view the design reference alongside the implementation. Use this direction when the immediate need is to inspect a design while browsing the corresponding story.
Link a published Storybook story from Figma
Storybook Connect works in the other direction: its Figma plugin links stories to Figma components, variants, and instances. The documented workflow requires a Storybook published to Chromatic: choose the branch to link, copy the story URL, and paste it into the plugin. Storybook says linked stories reflect later publishes on that branch. The plugin does not support linking stories to Figma layers. Confirm the current plugin instructions and publishing prerequisites before adopting this workflow. Storybook design integrations
Consider a third-party overlay addon cautiously
The Storybook addon directory lists Storybook Addon Figma Sync, whose listing claims support for overlays, side-by-side comparison, and pixel-diff views. Those are the addon author’s claims, not independent validation. Check its maintenance, Storybook compatibility, and Figma access requirements before relying on it. Addon listing
Choose the right comparison workflow
| Approach | Best suited to | Workflow | Key consideration |
|---|---|---|---|
| Storybook visual tests | Detecting visual regressions against an accepted implementation baseline | Review story diffs in the testing workflow and CI | Requires stories for the states and render conditions you want covered; changes need human review |
| Figma design embedded in a story | Viewing a design reference alongside its implementation | Add a design parameter with a Figma URL |
Provides a reference in Storybook; it is distinct from baseline regression testing |
| Storybook Connect in Figma | Opening published stories from Figma components, variants, or instances | Publish to Chromatic, select a branch, then paste the story URL into the plugin | Does not support linking Figma layers |
| Storybook Addon Figma Sync | Trying an in-browser overlay or side-by-side design comparison | Third-party addon; see its listing for setup | Overlay and pixel-diff support are claims in the addon listing; verify compatibility and maintenance |
These approaches address different needs. Baseline tests ask whether a rendered story changed; a Figma integration helps reviewers consult or compare against a design. When evaluating a setup, consider the purpose, workflow location, story and browser coverage, review ownership, CI policy, version requirements, and whether Chromatic publishing or a third-party dependency is involved. Visual testing · Design integrations
Recommended Free Tools
Troubleshoot common review problems
A story shows a difference, but the design was not changed
Inspect the diff rather than accepting it automatically. Check the story’s state and the browser, viewport, and theme being rendered; determine whether the implementation changed or the story no longer represents the intended state. Correct an unintended change, then rerun the comparison.
The review misses a state or rendering condition
Check whether that state has a story and whether the relevant browser, viewport, or theme is part of the configured coverage. Add the missing story or coverage condition, then verify the current addon configuration supports it.
The Figma plugin cannot link a layer
Storybook’s documented Connect plugin links stories to components, variants, and instances, not Figma layers. Link the supported component or instance instead, or use the Figma-in-Storybook direction if the goal is to view a design reference beside a story.
The integration setup does not match the project
Verify the project’s Storybook version, Chromatic access, and whether the Storybook has been published where the workflow requires it. The addon listing gives Storybook 7.6 or later as a prerequisite for @chromatic-com/storybook; check the listing and current official setup documentation for any later changes.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesOr skip the browser setup
For a screenshot of a live page, ScreenshotNeo offers a one-request API. This is a separate capture workflow from Storybook’s story-based visual regression tests and Figma integrations; it does not replace testing component states against baselines.
Quick Recap
cURL:
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. ScreenshotNeo accepts cookie or consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month, no card required.
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.
