Chromatic Pricing for a Small Development Team
Chromatic lists plans from free to custom-priced Enterprise. Compare snapshot limits, browser coverage, and overage costs to estimate what a small team will pay.
Direct answer: Chromatic’s listed monthly plans are Free at $0 for 5,000 billed snapshots, Starter at $179 for 35,000, and Pro at $399 for 85,000. Enterprise pricing is custom. Chromatic says it does not charge per seat, so a small team’s main cost drivers are snapshot usage and required features, especially browser coverage. Starter and Pro list additional billed snapshots at $0.008 each. Check Chromatic’s pricing page before purchasing because prices and allowances can change.
Chromatic plan prices at a glance
| Plan | Listed monthly price | Included billed snapshots | Relevant features listed |
|---|---|---|---|
| Free | $0 | 5,000 | Chrome testing, unlimited projects and users/collaborators, Git and CI integrations, UI version tracking |
| Starter | $179 | 35,000 | Free features plus Safari, Firefox, and Edge testing; $0.008 per additional billed snapshot |
| Pro | $399 | 85,000 | Starter features plus a custom domain; $0.008 per additional billed snapshot |
| Enterprise | Custom | Custom or unlimited snapshots listed | Unlimited accessibility usage, SSO and custom Git integrations, priority support and SLA, data retention |
These are the amounts shown on Chromatic’s official pricing page when checked on October 3, 2026. They are list prices, not a personalized quote. The reviewed material does not establish tax-inclusive totals or geographic price variations, so confirm the checkout amount for your account.
Does Chromatic charge per user?
No per-seat charge is listed. Chromatic says teams can invite collaborators without a per-seat fee; access to projects is still controlled by project permissions. For a small team, adding another developer does not by itself multiply the subscription price. Snapshot consumption and plan features are the more relevant budget questions. See Chromatic’s team permissions FAQ.
How to estimate a small team’s monthly cost
- Forecast billed snapshots. Start with the number of visual and accessibility snapshots you expect across builds, projects, browsers, devices, and modes. Usage aggregates across projects in the account.
- Account for snapshot outcomes. A captured visual or accessibility snapshot counts as one billed snapshot. A copied TurboSnap snapshot counts as 0.2. A qualifying bypassed snapshot counts as zero. Interaction tests do not incur billed snapshots.
- Check browser requirements. Free lists Chrome testing. Safari, Firefox, and Edge are listed beginning with Starter. If cross-browser visual checks are part of your release criteria, include that requirement in the plan choice.
- Compare forecast with included allowance. Free includes 5,000; Starter 35,000; Pro 85,000. Estimate usage from actual test and build patterns rather than team size alone.
- Model overages and limits. Starter and Pro list $0.008 per extra billed snapshot. Free pauses review and testing when its allowance is exhausted; paid plans continue and bill excess usage.
- Check higher-tier requirements. Compare Pro’s custom domain and higher allowance with Starter. If you need Enterprise-listed capabilities such as SSO, custom Git integrations, an SLA, or data retention, request custom pricing.
Chromatic documents snapshot accounting, usage reporting, and billing alerts in its billing guide. Use the account’s usage reports to refine estimates as real projects and builds accumulate.
What happens when the snapshot limit is reached?
On Free, review and testing pause after the 5,000-snapshot monthly allowance is used. They resume after the allowance resets or after upgrading. Chromatic says Free has no trial period and does not expire. On Starter and Pro, testing continues and additional billed snapshots are charged at the listed $0.008 rate. Keep an eye on usage reports and alerts if a build surge could create an unexpected overage.
Snapshot accounting details that affect the estimate
- Captured: one billed snapshot.
- Copied by TurboSnap: 0.2 billed snapshot.
- Bypassed: zero billed snapshots when the build qualifies.
- Interaction tests: no billed snapshots.
- Visual and accessibility snapshots: billed; multiple browsers, devices, modes, or test types can increase the total.
TurboSnap uses the dependency graph to narrow which stories need snapshots. An unchanged-looking commit does not guarantee a bypass: the build must satisfy Chromatic’s documented dependency and ancestor-build conditions. The August 2026 changelog says bypassed builds require TurboSnap and Chromatic CLI 17.7.0 or later. Review the August 2026 changelog and current billing documentation for qualification details.
Which plan fits a small development team?
| Choose this plan when… | What to verify |
|---|---|
| Free: expected usage fits within 5,000 and Chrome coverage is enough. | Decide whether pausing review and testing at the limit is acceptable. |
| Starter: the team needs Safari, Firefox, or Edge, or needs more than Free’s allowance. | Compare 35,000 included snapshots with forecast use and possible $0.008 overages. |
| Pro: the team needs the listed custom domain or expects to use the larger allowance. | Assess whether its $220 monthly increase over Starter is justified by those specific requirements. |
| Enterprise: the team requires listed enterprise capabilities such as SSO, custom Git integrations, an SLA, or data retention. | Ask Chromatic for a quote and confirm snapshot and accessibility terms. |
Do not choose Pro solely because a pricing page labels it “Best value.” Compare the capabilities your team will use and its realistic monthly snapshot total.
Billing cadence and plan-name caveats
Chromatic’s billing documentation says self-serve plans bill monthly on the subscription date and do not currently support annual payment. Plan changes are prorated by day. The documentation also says the former Standard plan was renamed Pro in September 2025; Legacy Pro is no longer available to new customers, though existing subscribers may retain it while they remain subscribed. Older articles and cached pages may therefore show plan names or terms that differ from the current public offer. See the official billing documentation.
Ways to control snapshot spend
- Use usage reports to identify which projects and builds account for snapshots.
- Review browser, device, mode, and accessibility coverage so each added dimension is intentional.
- Use TurboSnap and keep its dependency information accurate; eligible copied or bypassed snapshots can reduce billed usage.
- Set billing alerts and consider likely build spikes, not only an average month.
- Share the same account allowance across projects in your estimate, since billing aggregates account usage.
ScreenshotNeo for screenshot API needs
Chromatic is for component visual testing and review. If your team also needs screenshots of live web pages through an API or AI-agent workflow, try ScreenshotNeo first: it removes cookie banners, popups, and chat widgets before capture, bills only clean shots, and has the lowest paid plan described here. It is a separate product and does not replace Chromatic’s component testing workflow.
Or skip the browser setup
For a one-off website screenshot, call the API with a URL. See the ScreenshotNeo API documentation for the available options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);- Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Response headers say the page verdict and whether it was billed.
- An MCP server lets Claude, Cursor, and other MCP clients use screenshot tools.
- 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Every feature is on every plan.
Sign up free for 1,000 screenshots a month, with no card required.
Common pricing and usage questions
Can the number of collaborators change the plan price?
Chromatic says it does not charge per seat. Project permissions still determine who can access each project.
Are all snapshots billed as one full snapshot?
No. Captures count as one, copied TurboSnap snapshots count as 0.2, and qualifying bypassed snapshots count as zero. Interaction tests do not incur billed snapshots.
Does Free expire after a trial?
No trial period is listed for Free; Chromatic says the plan does not expire. Its monthly review and testing allowance still applies.
Can a team get an exact bill from the public price table?
No. Actual cost depends on account usage and applicable checkout details. The public table is a useful estimate, but confirm the current quote or checkout total with Chromatic.
