To reduce Applitools Eyes usage without losing useful coverage, remove only redundant visual checkpoints, keep distinct states that protect important risks, and tune comparison settings or regions narrowly for known variation. Fewer checkpoints may reduce checkpoint consumption, but the effect on your bill depends on your contract and account usage—not a universal savings formula.
What counts as an Applitools Eyes step?
An Eyes checkpoint is a visual validation at an application state: an Eyes SDK check captures a screenshot and compares it with a baseline. A click, keystroke, or other ordinary UI action is not itself a visual checkpoint unless the test also performs an Eyes check. See Applitools’ visual UI testing overview and system overview.
As an Amazon Associate I earn from qualifying purchases.
This distinction matters when reviewing test volume. Count calls to eyes.check() or the equivalent in your SDK, rather than counting every step in a browser script.
Recommended Free Tools
How do I reduce the number of Applitools Eyes steps?
1. Inventory checkpoints by state and risk
List every visual check and record the screen state it captures, the transition or risk it protects, and whether another checkpoint already covers the same visual outcome. Look especially for repeated captures of an unchanged screen and checks that add no distinct visual assertion.
#1 Best Overall
2. Consolidate only when meaningful coverage remains
Remove or combine checks only when the remaining screenshot still verifies the visual outcome you need. Preserve checkpoints for distinct states, important transitions, and high-risk areas. A broader screenshot may cover content that several narrower snapshots previously checked, but it is not a substitute if those checks represented different states.
Applitools’ Playwright guidance recommends using eyes.check() for appearance and functionality with a visual aspect, while retaining textual assertions when exact logic checks are necessary. Its statement that this can reduce test code by 80% concerns code size; it is not a promise of fewer checkpoints or lower subscription cost. See Integration with Playwright.
3. Keep functional assertions for exact behavior
Use ordinary assertions for values or behavior that must be checked precisely—for example, whether a particular value is present or an action returns the expected result. Use visual checks to validate appearance. Keeping those jobs distinct helps avoid adding screenshots where a direct logic assertion is the better test.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
4. Measure what changed
Compare the before-and-after checkpoint volume, time spent reviewing changed diffs, coverage of key states, and escaped visual defects. These measurements help determine whether consolidation removed waste or weakened coverage. No universal savings percentage can be inferred without your team’s usage and contract details.
How should I tune comparisons for dynamic pages?
If the main burden is noisy diffs and review effort, identify what is changing before loosening comparison behavior. Applitools documents several match levels; choose according to the validation you need, not simply to make failures disappear. See Defining Eyes Visual AI Settings.
| Setting | What it checks | When it may fit | Main risk |
|---|---|---|---|
| Strict | Appearance with content and styling differences considered. | Mostly static content on a particular browser and operating system; the documented recommended default for this situation. | Dynamic or environment-specific changes can produce diffs that need review. |
| Layout | Relative structure while ignoring content and styling. | Pages with dynamic content, localization, or cross-environment testing where a shared baseline is used across browsers, devices, viewport sizes, operating systems, or orientations. | Content and styling changes may not be caught as visual differences. |
| Ignore Colors | Ignores color-only changes. | When color variation is known to be irrelevant to the specific check. | Meaningful color regressions can be overlooked. |
| Exact | Pixel-to-pixel comparison. | Only where exact pixel identity is specifically required. | Applitools does not recommend it for ordinary verification. |
Use regions for bounded, known variation
For a predictable changing area, use the narrowest region behavior that fits: dynamic regions tolerate predictable patterns, floating regions allow bounded movement, and ignore regions suppress diffs within their bounds. Keep these regions limited to known volatile content; broad regions can hide defects in important content. The Applitools Dashboard documentation describes region handling.
Rank #3
Does reducing Eyes checkpoints lower my Applitools bill?
It can reduce checkpoint usage, but the amount and invoice impact depend on your plan, order form, and actual account usage. Applitools’ subscription agreement distinguishes Pages from Checkpoints: a Page is a unique Checkpoint regardless of how many times it is executed or which browser or device is used, while each visual validation execution counts as a Checkpoint. The agreement also says separate order forms can have different terms. Review the Subscription Service Agreement versioned 2023-11-15 and your own order form rather than assuming that fewer test steps translate directly into a particular bill reduction.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe Applitools Platform Pricing page, accessed in 2026, lists Starter at $667 per month paid annually, with either 100,000 component checkpoints or 1,000 page checkpoints. It lists Professional starting at 150 active pages or 1,500 components, and Enterprise starting at 350 active pages or 1,500 components. The latter tiers describe unlimited executions, while pricing is customizable. These public figures are not an account-specific quote; recheck the page and compare it with your contract and usage.
Make a cost decision from the account’s actual terms
- Ask your Applitools administrator for current usage and the applicable allowance.
- Compare active pages, components, checkpoint executions, and concurrency with the terms in your order form.
- Ask your account representative how the proposed test changes affect your specific subscription before treating reduced volume as a forecasted saving.
Or skip the browser setup
If the goal is a clean screenshot of a live page rather than an Applitools baseline comparison, ScreenshotNeo offers a one-request screenshot API and MCP server. It is not a replacement for Eyes’ visual regression workflow, but can capture screenshots or PDFs without you setting up browser automation. Its cookie-banner, popup, and chat-widget cleanup can be turned off; bot checks, blank pages, failed loads, and cache hits are not billed. AI agents can use its MCP tools to take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
See the ScreenshotNeo API documentation. For example, this cURL request saves a WebP screenshot; replace the URL and API key with your own:
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Troubleshooting checkpoint cleanup
Checkpoint count did not fall after deleting browser actions
Review the test for remaining Eyes checks. Ordinary clicks and typing are not checkpoints; each visual validation is. Count SDK check calls rather than browser actions.
Fewer checks caused a missed visual regression
Restore a checkpoint for any removed state that had its own meaningful risk or transition. Reassess whether the consolidated screenshot actually includes the needed visual outcome.
Dynamic pages still produce noisy diffs
Classify the difference first: changing content, color-only variation, bounded movement, or a genuine layout or content defect. Then choose a suitable match level or narrowly scoped region. Avoid weakening the entire comparison for one volatile element.
Usage changes but the invoice does not
Check whether your subscription is measured by Pages, Checkpoints, components, active pages, or other contracted terms, and confirm the allowance in your order form. Public pricing examples cannot establish negotiated terms or predict a specific invoice.
Frequently Asked Questions
Is a click or keystroke an Applitools Eyes step?
No. A visual checkpoint is the Eyes check that captures and compares a state; browser actions alone are not checkpoints.
Does Applitools promise 80% lower visual-testing costs?
No. The cited Playwright documentation’s 80% figure refers to reducing test code, not subscription cost or checkpoint volume.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
