Visual testing for the page your customers load
TestKase Visual captures the assembled page in real Chrome, Edge, Firefox and Safari and compares it with the image your team approved. Point it at any public address, or hand the CLI a folder of PNGs — no repository changes, no SDK, and 1,000 free snapshots to start.
1,000 free snapshots · lifetime allowance · no credit card required
If it has an address, it can have a baseline
Paste a list of public pages and press Run. Real browsers on our machines open each one, capture it and compare it with the approved image. Put the list on a daily, weekly or monthly schedule and it keeps watching with nobody driving.
- A CMS site, a docs site, a store, a site an agency built
- Nothing installed and no repository involved
- Catches a content edit or a third-party script change with no build
What the assembled page shows
Some changes only exist once everything is on the page together. A capture of the page shows them.
Clipped by its container
A card cut off by a parent's overflow, or a menu hidden behind the header that sits above it.
Stylesheet order
A global rule that loads later on the real page and quietly restyles a button or a heading.
A font that fell back
The web font fails to load and the fallback reflows the headline across a second line.
Something injected
A tag manager adds a banner, or a third-party widget resizes and pushes everything below it down.
One browser, not the others
Safari on macOS and Chrome on Windows keep separate baselines, so a break in one is never hidden by the rest.
Every size its own baseline
A capture at a new size starts its own approved image rather than reading as a regression.
Hand it a folder of PNGs
Already taking screenshots in your pipeline? The @testkase/visual uploader sends a folder of them for comparison, whatever produced them, and the exit code tells your CI whether anything needs a person.
- A public npm package with zero runtime dependencies
- Exit 0 when nothing needs review, 1 when something does
- Images go straight to storage, with a dry run to check first
TestKase Visual and Chromatic, side by side
What TestKase Visual gives a team that wants its pages watched, with Chromatic's approach noted where it helps you compare.
| Item | Side by side | Status |
|---|---|---|
| What is photographed | TestKase Visual captures the assembled page in a real browser, keyed by page address, browser, operating system and size. Chromatic is built by the Storybook maintainers, turns stories into tests, and also works with Vitest, Playwright and Cypress. | The page |
| Sites outside your codebase | A TestKase run takes any public address — a CMS site, a documentation site, a site somebody else built — with nothing installed and no repository involved. | Any site |
| Screenshots from any tool | The TestKase CLI uploads a folder of PNGs from whatever produced them and exits 0 or 1, so it fits any pipeline without a framework plugin. | Any PNG |
| Changes nobody committed | A TestKase page can carry its own daily, weekly or monthly schedule, so a content edit or a tag-manager change is caught without a commit or a build. | Built in |
| States behind a sign-in | In a TestKase Live session a person signs in, drives the flow to the screen that matters and presses Visual — on a desktop browser or a real phone, with no fixture or mock. | Live capture |
| Seats | Neither charges per person: Chromatic advertises unlimited collaborators on every tier, and TestKase Visual is one flat plan for the whole organisation, with nothing per parallel session either. | Both |
Where your pages live, and how each is captured
Every kind of site has a way in. Public pages run on their own; anything behind a sign-in is a Live capture or a CLI upload.
- Marketing site on a CMS — public pages, on a scheduleRun
- Documentation site — every install and API pageRun
- Storefront — home, category and product pagesRun
- Site an agency built — no access to the code neededRun
- Signed-in app screens — sign in, reach the state, press VisualLive
- Mobile web and app screens — from a Live session on a real phoneLive
- Screens your tests already take — any PNGs, any frameworkCLI
- A checkout or wizard step — drive the flow there in a sessionLive
More on scheduled runs, Live sessions and the command-line uploader.
Frequently asked questions
The page — assembled, styled and loaded in a real browser, the way a customer sees it. Each capture is compared with the approved image for that page address, browser, operating system and size, so Chrome on Windows and Safari on macOS each keep their own baseline.
Any page with a public address: a marketing site on a CMS, a documentation site, a store, a site an agency built for you. Nothing is installed and no repository is involved. For a page behind a sign-in, capture it from a Live session or upload screenshots from your own tests with the CLI.
No. TestKase Visual works at the level of pages, not components, so there is nothing to set up in your codebase. A baseline hangs off a page address, a browser, a platform and an image size.
Yes. The @testkase/visual command-line uploader takes a folder of PNGs from whatever produced them. Each file is compared with its baseline, and the command exits 0 when nothing needs review and 1 when something does — that exit code is the whole CI integration. Keep file names stable, because the file name is the screen name.
Live sessions capture in Chrome, Edge, Firefox and Safari on real Windows and macOS machines, and on real phones and tablets. Scheduled runs use desktop browsers.
With ignore regions: boxes you draw over a rotating banner, a date or a live counter, masked out of both images before they are compared. Everything outside the box is checked at full strictness.
1,000 snapshots free as a lifetime allowance, with no card. Then one flat monthly plan with 5,000 snapshots a month for the whole organisation. Nothing is charged per user or per parallel session. Every price is on the pricing page.
Related
- TestKase vs Deque axeThe same engine underneath, a different report on top
- TestKase vs SiteimproveA developer tool rather than a governance platform
- TestKase vs Level AccessAccessibility scanning without a services engagement
- All of Why TestKaseHow we compare with the tools you are probably already paying for
- PricingPer-seat test management and per-thread device testing, priced on the page
Watch the pages your customers load
Paste a few addresses, approve the first capture, and see what the next one finds — 1,000 snapshots free, no credit card.