To test a site’s appearance in Safari and Chrome with Applitools Eyes, keep your existing browser automation tests, add Eyes visual checkpoints at important UI states, and configure both browsers as test environments. Eyes compares each captured screen with a baseline; reviewers decide whether differences are bugs or intentional changes before updating that baseline. In the usual setup, Safari and Chrome have separate baselines.
How Eyes fits into Safari and Chrome testing
Eyes adds visual regression checks to an application test flow; it does not replace the test suite that navigates the site and exercises its behavior. The suite drives the application to a state worth checking, the Eyes SDK captures a screenshot at a checkpoint and sends it to the Eyes server, and the server compares it with a stored baseline. Testers inspect differences in Eyes Test Manager, report bugs or annotate special regions where appropriate, and save approved baseline changes for future runs. Applitools’ system overview describes this architecture.
For Safari and Chrome, the key setup choice is whether to validate each browser against its own accepted appearance or deliberately compare them against a shared reference. Browser is part of the default baseline identity, so separate browser runs ordinarily use separate baselines.
Choose per-browser baselines or cross-environment comparison
Use separate baselines for browser-specific expectations
This is the usual choice when you want to catch a regression in Safari without treating a legitimate browser-specific rendering difference as a failure in Chrome, or vice versa. By default, a baseline is associated with the application name, test name, operating system, viewport size, and browser. Keep the relevant environment settings consistent between runs so a test is compared with the intended baseline. See the Applitools baseline explanation.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Use a shared baseline only when that is the test you want
Applitools documents cross-environment testing by assigning a Baseline Environment Name. A help article published in 2021 recommends Layout match level for this case because different environments may have visible differences. Treat that as older guidance rather than current SDK syntax: verify the configuration supported by your chosen SDK before using it. A shared reference makes sense only if the team intends to compare across environments and understands how its match level handles visual variation. Read the cross-environment help article.
Configure Safari and Chrome in your existing suite
Start with the Eyes SDK integration for the language and automation framework already used by your tests. The official Selenium Java quickstart shows desktop Chrome and Safari targets in Eyes Configuration, with specified viewport dimensions. It also illustrates that browser and device targets are configuration choices, not a separate visual test process. Use its exact setup for Selenium Java; do not copy Java configuration into Playwright or another SDK. Open the Selenium Java quickstart.
Rank #2
- Set up Eyes for your framework. Follow the current SDK quickstart for the language and runner you use, then connect Eyes to the suite that already opens and drives your application.
- Choose the browser environments. Configure Chrome and Safari targets using the supported syntax for that SDK. Keep the viewport and operating-system choices explicit so the resulting baselines represent the environments you mean to test.
- Place checkpoints at meaningful states. After the test has reached a stable page or interaction state, add an Eyes visual checkpoint. Choose states that matter to users—such as a page after it has loaded or a menu after it has opened—rather than capturing arbitrary moments during page activity.
- Run the suite and inspect results. On the first run for an environment, the captures establish baselines. Later runs are compared with those images, and Eyes reports differences for review.
- Review before updating baselines. Accept changes only when they are expected; investigate unexpected differences as possible regressions. Save approved changes so later runs compare against the intended appearance.
For a local Selenium Java setup, Applitools’ quickstart says the ChromeDriver major version should match the Chrome major version. Keep that advice scoped to the documented local setup; the available guidance does not establish one universal Safari driver configuration across frameworks.
Framework-specific notes and rendering choices
Playwright
Applitools’ Playwright integration uses an Applitools-enhanced Playwright test fixture and describes match-level configuration. Fixture and checkpoint APIs are SDK-specific, so use the current integration instructions rather than assuming the Selenium Java setup applies. See the Playwright integration documentation.
Local execution or Ultrafast Grid
Applitools describes Ultrafast Grid as a cloud browser and device rendering option that works with existing Playwright, Cypress, Selenium, and Appium suites. This is an option to consider when deciding how to cover browser and device environments; the available information does not establish independent comparative performance results. Applitools’ claims such as “up to 99%” lower flakiness are vendor claims, not neutral measurements. See Applitools’ cross-browser product information.
AI-assisted setup through MCP
Applitools’ MCP documentation currently limits setup and checkpoint-creation tools to the Playwright Fixtures SDK. Its tools for inspecting, resolving, and reviewing results can work with Eyes results created by any SDK. This is a limitation of those MCP tools, not a general restriction on which frameworks can use Eyes. Check the Applitools MCP documentation.
Rank #4
- Used Book in Good Condition
Troubleshoot common setup and review problems
- A run creates a new baseline instead of comparing as expected: Check the application name, test name, operating system, viewport size, and browser. Those values are part of the default baseline identity. If you intend to compare environments, confirm the current SDK guidance for Baseline Environment Name rather than assuming different browsers share a baseline.
- Chrome’s local Selenium setup has a driver error: Compare the Chrome and ChromeDriver major versions and align them, as specified in Applitools’ Selenium Java quickstart.
- Playwright setup instructions do not match the test code: Confirm that you are following the Eyes integration for Playwright and using its enhanced fixture conventions. Do not substitute Selenium Java examples for Playwright APIs.
- A visual difference appears between Safari and Chrome: First determine whether the run is using separate browser baselines or a deliberate cross-environment baseline. Review browser-specific differences before accepting a change across the matrix.
- A cross-environment comparison flags expected rendering variation: Reassess whether a shared baseline is appropriate. The 2021 Applitools help article recommends Layout match level for cross-environment testing, but check current SDK documentation before setting it.
Or skip the browser setup
Applitools Eyes is for visual regression checks inside an automated test workflow. If you instead need a screenshot or PDF from a single HTTP request, ScreenshotNeo is a website screenshot API and MCP server for developers.
One-call cURL example (see the ScreenshotNeo API documentation):
Recommended Free Tools
Quick Recap
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
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.
