UI Verify for open source: 50,000 free snapshots a month

Open-source maintainers ship UI on every pull request and rarely have a budget for a paid visual testing tool. So the free tier for a public project is much bigger than the standard one, and you turn it on yourself: there is no application to fill in, no sales call, and no waiting for approval.

An open-source workspace runs on the same engine as every paid plan, with a far larger free allowance:

• 50,000 snapshots a month, 5 times the standard free tier.
• 500 AI reviews a month, so the judge tells an intended change from a real regression on your pull requests.
• Snapshot only what changed, so a typical build bills a fraction of your full UI and the allowance stretches further.
• GitHub pull request checks and comments, the MCP for your coding agent, and unlimited projects and members.

It behaves like the free tier otherwise: it is a bigger free bucket, not a paid plan. There is no card and no invoice. If you cross the snapshot allowance the build pauses rather than billing you, and if you cross the AI allowance the build still renders, just without new verdicts.

Use the Get started button on the open-source callout on the pricing page or from this article. It takes you straight through sign-up onto the open-source tier - there is no form to fill in and no box to tick, and your first workspace confirms the plan is applied. That is the whole eligibility step.

Name your first project and get a build in the same way as any other project. Follow How to set up visual regression testing for your framework, then push. Your baselines and pull request checks work exactly as they do on every plan.

No. The open-source tier is self-declared and there is no verification step, so you are never blocked waiting on a human to approve you. We would rather a few teams pick it who should not than make a real maintainer jump through a hoop. The spirit is simple: keep your repository public.

Most open-source pull requests come from forks, and GitHub withholds your secrets from a fork's workflow run, so the visual check needs a maintainer-approval flow to run with your key. That is a separate setup step worth getting right. See Visual testing on open source repos and fork pull requests for the flow and the CI gotchas.