Skip to main content
Comparison · Visual testing

Capture, mask, review — with nothing to install

TestKase Visual photographs your pages in real browsers, masks what you told it to ignore, and puts every change in front of a person to approve or report. Start from a list of addresses, a Live session or a folder of PNGs, with 1,000 free snapshots and no SDK.

1,000 free snapshots · lifetime allowance · no credit card required

Review3 changedPricing · Chrome · WindowsUnreviewedbaselinenew captureApproveApprove +update baselineBugbanner masked in both · price block changedHome · Safari · macOSApprovedSign-up · Edge · WindowsBug

The workflow

From first capture to approved baseline, and round again

Approve a page once and it becomes the baseline. Every capture after that is matched to it, masked, compared and either stays quiet or waits for a person — who decides whether the change becomes the new baseline or a bug.

first captureapprove it oncebaselinekeyed by 6 valuesnext capturemask in bothcomparepixels → ratioreviewUnreviewedbugticket filedno changequiet runsamechangedapprove + update baseline → the new picture becomes the baselineor approve once andkeep the old baseline

Ways in

Four ways to capture, none of them an SDK

Start from whatever you already have. Every route lands in the same baselines and the same review queue.

A list of public pages

Paste the addresses and press Run. Real browsers on our machines open and photograph each one.

A Live session

Sign in, drive the page to the state that matters and press Visual — on a desktop browser or a real phone.

A folder of PNGs

The @testkase/visual CLI uploads screenshots from whatever produced them and exits 1 when something needs review.

A schedule on the page

Daily, weekly or monthly at a time in your timezone, on desktop browsers, with the report emailed to you.

Free allowance

A free tier you can do the arithmetic on

One page, in one browser, at one size, is one snapshot. You get 1,000 of them for life with no card, then one flat monthly plan for the whole organisation — so you know what a run will use before you press it.

  • Not a trial that expires
  • 5,000 snapshots a month on the flat plan
  • Nothing per user, nothing per parallel session
what counts as one snapshot1 page×1 browser×1 size=1 snapshota run over 10 pages in one browser10 snapshotsfree · lifetime · no card1,000 snapshotsused on your first runsthen one flat plan5,000 a month · whole orgnothing per user · nothing per parallel session

TestKase Visual and Percy, side by side

What a team gets from TestKase Visual, with Percy's approach noted where it helps you compare.

Percy details read on BrowserStack's product and billing pages, 11 September 2026. They change; check rather than trusting our summary.
ItemSide by sideStatus
Starting without a suiteA TestKase run takes a list of public page addresses; a Live session capture takes a person and no code at all. Percy captures through its SDKs for Playwright, Selenium, Cypress and Appium and the BrowserStack SDK.No suite needed
Watching a page on a clockA TestKase page can carry its own daily, weekly or monthly schedule at a time in a named timezone, so a content edit or a third-party script update is caught with nobody starting a build.Built in
Content that moves on its ownA TestKase ignore region is a box you draw, masked out of both images before comparing — you can always see exactly what is excluded. Percy filters dynamic regions with Intelli-Ignore.Transparent
What a snapshot isOn TestKase a snapshot is one page, in one browser, at one size, and that is the unit the allowance counts. Percy meters screenshots — one rendering at one browser and one width — and groups them as snapshots in its interface.One unit
SeatsNeither charges per user: Percy's plans carry unlimited users, and TestKase Visual is one plan for the whole organisation, with nothing per parallel session either.Both
Where it sitsTestKase Visual shares a workspace with the TestKase device farm, the automation runs, the accessibility scanner and the test cases. Percy is part of BrowserStack.One workspace

Getting started

Your first review, before lunch

  1. 1

    Add your pages

    Paste the public addresses you care about, or capture a state from a Live session. No code, no SDK.

  2. 2

    Approve the first capture

    It becomes the baseline for that page, browser, platform and size. Draw ignore regions over anything that moves on its own.

  3. 3

    Review what changes

    Every later capture is compared with it. Quiet when nothing moved; Unreviewed in the queue when something did.

Read more on how baselines are keyed, ignore regions and scheduled runs.

FAQ

Frequently asked questions

One page, captured once, in one browser, at one size. A run over ten pages in one browser is ten snapshots, and a daily schedule over twenty pages is roughly six hundred a month. That is the whole counting rule.

Point a run at your pages and see what it finds

No SDK, no suite and no credit card — just 1,000 free snapshots and a review queue.