Applitools Eyes normally keeps separate visual baselines for different browser and environment combinations. Keep that default when you want to catch browser-specific visual regressions. If you want one cross-browser structural check, deliberately configure a shared Baseline Environment Name and use Layout matching. Review differences in Eyes Test Manager before accepting any change to an expected image.
How Applitools Eyes identifies a baseline
Eyes associates a baseline with an application name, test name, operating system, viewport size, and browser. A run in a previously unseen combination can establish a new baseline. Consequently, running the same test in Chrome and then Firefox does not automatically compare both browsers against one shared image: the browser is part of the environment identity, so Firefox can have its own baseline. Applitools explains baseline identity and behavior.
That distinction matters when setting up a test matrix. Separate references answer, “Has this browser changed compared with its own accepted appearance?” A shared cross-environment reference answers a different question: “Does this run preserve the layout represented by the chosen reference environment?”
Choose the comparison model that matches the test goal
| Approach | Reference model | Use it for | Trade-off |
|---|---|---|---|
| Environment-specific baselines | One baseline for each test and environment combination, including browser, OS, and viewport. | Browser-specific visual regression, especially with Strict matching and stable content. | More references to review and maintain across environments. |
| Shared cross-environment baseline | A Baseline Environment Name associates runs with one reference environment. | Structural comparisons across browsers, operating systems, or viewport sizes, using Layout matching. | Layout matching disregards some visual details, including text, graphics, color, and other styling; it is not a replacement for strict same-environment checks. |
| Baseline variations | Multiple accepted reference images for a particular test step. | Legitimate alternate renderings, such as an A/B-tested page. | Variations need deliberate management; Applitools documents a maximum of 20 per step. |
Applitools recommends Layout matching for cross-environment tests because different environments can have noticeable visual differences. Layout matching checks relationships and positions among elements while ignoring text, graphics, color, and other style changes. Strict matching is intended for close visual regression checks within a particular browser and OS, typically where content is mostly static. See Applitools’ guidance on cross-environment testing and match levels.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Set up browser-specific baselines
- Run the test in each target browser and environment. The initial run for a new test/environment combination establishes its baseline; later runs compare against that reference.
- Keep environment identity intact. Do not set a shared Baseline Environment Name if the purpose is to judge each browser against its own accepted rendering.
- Use Strict matching when close visual fidelity is the goal. This is most useful when the same browser/OS and stable page content are expected from run to run.
- Inspect results in Eyes Test Manager. Review each flagged difference in context. Accept a change only when it is intended; reject it when it is an unexpected regression. Accepting updates the expected baseline, while rejecting preserves the previous reference.
Applitools describes this inspect-and-update workflow in its Eyes workflow overview and Test Manager baseline documentation.
Configure a shared cross-browser structural baseline
- Choose the reference environment. Decide which browser and environment should supply the shared reference. The Baseline Environment Name is associated with one environment, which serves as the reference for other runs using that name.
- Set the Baseline Environment Name before opening the Eyes test. Configure it using the API for the framework and SDK version in your project. The cross-environment help article contains framework-specific examples but was updated in 2021; do not copy an old method signature without checking the current SDK documentation for your version.
- Use Layout matching for the shared comparison. This makes the check about structure and element relationships rather than requiring different browsers to render identical text, graphics, colors, and styles.
- Run the other browser configurations and review their results. Investigate layout differences and update the reference only when the change is intended.
The Baseline Environment Name is an explicit comparison choice, not a setting that makes all browser output fully visually equivalent. Keep separate Strict checks as well if browser-specific styling or rendering regressions matter to your team.
Rank #2
Use baseline variations for legitimate step-level alternatives
If one test step has several valid appearances—for example, a page can show different content under an A/B test—baseline variations let that step have more than one accepted reference. A checkpoint passes when it matches any saved variation. Applitools documents a limit of 20 variations per step; see its baseline variations documentation. This is a focused way to represent known alternatives, not a reason to loosen matching across unrelated pages.
Review and update baselines safely
- Accept a difference when the application change is expected and should become the new reference.
- Reject a difference when it is unintended; the prior expected image remains in place.
- Do not bulk-accept browser diffs without inspection. A difference can be a real defect even when the test is part of a multi-browser run.
- Keep the test objective visible during review. For Strict, environment-specific tests, assess the browser’s visual output closely. For Layout cross-environment tests, assess the structural relationships the match level is designed to compare.
Common baseline problems and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| A new browser run appears to establish a baseline instead of comparing with Chrome. | Browser is part of the default environment-specific baseline identity. | Decide whether separate browser references are intended. For shared structural comparison, configure a Baseline Environment Name before opening the test. |
| Cross-browser runs show many visual differences. | Strict or another close visual match level is being used across environments with different rendering. | For a structural cross-environment objective, use Layout matching; retain separate Strict checks where detailed appearance matters. |
| A baseline update would hide a suspected defect. | The change has not been classified as intentional. | Reject it in Eyes Test Manager to preserve the old expected image, then investigate the application or test before making a baseline update. |
| A legitimate alternate appearance fails despite being expected. | The step has only one accepted reference. | Consider adding a baseline variation for that step and manage the alternatives deliberately, within the documented 20-variation limit. |
| An SDK configuration example does not work. | The example may not match the installed framework or SDK version. | Use the current documentation for that SDK and configure the Baseline Environment Name before opening the Eyes test. |
Or skip the browser setup
If what you need is a clean screenshot of a page rather than a managed visual-regression baseline, ScreenshotNeo is a screenshot API and MCP server for developers. One GET request can return a PNG, JPEG, WebP, or PDF. Cookie banners are accepted and removed, along with known consent platforms, newsletter popups, and chat widgets, before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server exposes screenshot, page-info, and PDF tools to AI agents.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11cURL example (replace the target URL and use your API key):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month with no card.
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.
