BackstopJS and Lost Pixel are free, and so is vizzly tdd. The difference is how you review. Vizzly opens a dashboard that updates as your tests run, so you can accept or reject changes right there.
# Install and open the dashboard $ npm i -g @vizzly-testing/cli $ vizzly tdd start --open
| Vizzly TDD | BackstopJS, Lost Pixel | |
|---|---|---|
| Setup | Install the CLI and run your tests | Configure capture scenarios, often in JSON |
| Reviewing results | Local dashboard that updates as tests run | Static HTML report |
| Diff views | Overlay, toggle, onion skin, and side by side | Depends on the tool |
| Updating baselines | Accept or reject in the dashboard | Run an approve command or move files |
| Account needed | No | No |
| Price | Free locally | Free |
| Team review | Optional cloud plans with PR checks | Bring your own |
Yes. It runs on your machine with no account and no credit card. Connect a free cloud account when you want shared baselines and PR checks.
Anything that can save a screenshot. Call vizzlyScreenshot() from Playwright, Cypress, Puppeteer, Selenium, WebdriverIO, and others.
If you like defining scenarios in JSON and reviewing HTML reports, and your current process works, stick with it. Vizzly is for when you want a live dashboard and an easy path to team review.
More comparisons: Vitest vs VizzlyPercy vs VizzlyChromatic vs VizzlyAll tools
Run your screenshot tests, open the dashboard, and see if the workflow fits.