
Visual testing for Storybook, Playwright, & Cypress. Improving the UX of the Internet. Core maintainers of @StorybookJS.
CI/CD
Joined August 2010
- Tweets1.7K
- Following126
- Followers3.9K
- Likes1.5K
Pinned Tweet
🚀 Chromatic's Accessibility Testing & Dashboard are now live!
Powered by Storybook & axe, we're making accessibility compliance seamless across your entire dev lifecycle—without slowing you down.
Chromatic retweeted
How are agents really doing on your frontend? 🤖
Are they saving you work or shipping a button that’s 2px off?
Tell us in the State of AI in Frontend Delivery 2026 survey. It takes 5 minutes and 5 people get a $75 Amazon gift card as a thank you. 🙏
Survey in comments 👇
Read the full announcement: chromatic.com/blog/quarantin… (5/5)
In Library > Quarantined, you can see each test’s issue rate. Fix the flake, remove quarantine, and put the test back to work. While quarantined, it won’t catch regressions. (4/5)
The test doesn’t disappear. Quarantined diffs show up in the build’s Unstable group, alongside tests caught by the automatic flake filter. Expand the group to inspect them. (3/5)
Chromatic keeps capturing snapshots for quarantined tests, but ignores their diffs across builds, branches, and users. So the same flaky diff won’t keep showing up for review. (2/5)
📣 New in Chromatic: Quarantine for flaky tests
You can now quarantine the flaky diffs that slip past Chromatic’s automatic filter. Quarantine the test from its build or test page to get your PR moving. 🧵⤵️ (1/5)
Our new Vitest plugin turns the tests you already have into visual tests.
📖 No Storybook required
✍️ No changes to your test code
Join Ari Perkkiö, the Vitest core maintainer who built it, and Kyle Gach live tomorrow. 🧪
🎟️ Save your spot 👇
Run your tests as usual. Chromatic then:
✔️ Compares snapshots across stable cloud browsers
✔️ Runs every browser and viewport in parallel
✔️ Surfaces visual changes in your PR for team review
✔️ Stores the full rendered UI behind every diff
(3/4)
Vitest core maintainer Ari Perkkiö built the plugin around Browser Mode tests.
As tests run, Chromatic captures a web archive of each result: the HTML, CSS, JS & assets behind the UI. When something is off, open that state in a browser instead of debugging a screenshot. (2/4)
Chromatic for @vitest_dev Browser Mode is live. 🧪📸
Browser Mode runs your component tests in a real browser. Now Chromatic checks how those components look by capturing the rendered UI.
No new screenshot assertions. No second suite to maintain. 🧵 (1/4)
iOS is now available for React Native visual testing on Chromatic 📱
Chromatic now builds your Storybook app for iOS and runs your visual tests on the iOS simulator.
👉 Request beta access to get started: hubs.li/Q04wr_Wn0
This month we’re rolling out two changes to help you test more with fewer snapshots:
🔀 Builds that don’t touch UI are now free
📊 New Trends dashboard to help you investigate snapshot usage spikes
Read the full changelog 👇
🎟️ Register to join: us02web.zoom.us/webinar/regi…
Our upcoming public API lets agents test their own frontend work, diagnose what failed, and fix it in the same loop.
Join Jarel Fryer and Varun Vachhar for a live preview and our roadmap for agents.
Register in comments 👇
Flake Filter is live on every plan, on by default, with no setup required.
Read the full announcement » chromatic.com/blog/automatic…













