Compatibility and limits
Plan coverage and understand the boundaries of a run.
Web compatibility#
| Area | Support |
|---|---|
| Storybook capture | 8.6, 9, and 10; not Storybook 7. |
| Browsers | Chromium, Firefox, WebKit. |
| Web uploader | Node.js 24. Your build may use a different supported Node version. |
| Smart Snapshots | Supported Vite-based Storybook build with stats metadata. |
| Storybook addon | Storybook 8.2+ and 9; local-host sign-in. |
| Accessibility | Chromium, WCAG 2.2 A/AA automated checks. |
Read run warnings for unsupported story parameters. Successful upload does not imply every provider-specific Storybook feature was applied.
Run limits#
A web run supports up to 5,000 visual snapshots across browsers and screen sizes and has a 45-minute deadline. Accessibility adds billed checks separately. Split or reduce the story/mode/browser coverage if a build exceeds the visual limit; changing its upload token does not raise the limit.
Each project can have two active upload tokens and up to five notification endpoints. Uploaded web builds are retained for 30 days; generated access links last one hour.
Queueing#
Runs share capacity, so a successful upload may wait before capture. Paid runs have priority over trial runs under the published service description. Queue time is not billed as capture usage.
Native preview#
Android needs a bundled capture APK with x86_64. iOS needs an arm64 simulator build. Native availability, devices, and billing are separate from the web defaults; use project Setup and the applicable preview guide.
Unsupported assumptions#
A screenshot test is not an end-to-end production test. WebKit is not a physical iOS device. React Native Web is not native rendering. Automated accessibility findings are not a full accessibility audit. Use these checks alongside the other testing your application needs.