If Reg-suit reports every screenshot as changed, first verify that it fetched the intended baseline and paired each expected image with the right actual image. Then check whether the baseline and current captures were made under the same conditions. Adjust comparison tolerances only after those inputs are correct: a looser threshold can hide real visual changes rather than fix a bad baseline.
What Reg-suit is comparing
Reg-suit compares images in actualDir with expected images fetched by sync-expected, then creates an HTML report. In the standard run workflow, synchronization, comparison, and publishing are combined. A key-generator plugin determines which expected snapshot key to use, while a publisher plugin retrieves the expected images. If the key, fetched baseline, image names, or directory pairing is wrong, the comparison can make an unchanged page appear changed—or treat the actual image as a new item. Reg-suit documentation
As an Amazon Associate I earn from qualifying purchases.
Capture is upstream of that comparison. The official Puppeteer demo shows Reg-suit recognizing screenshots as “New items”; the screenshots supplied to the comparison matter as much as its settings. Reg-suit Puppeteer demo
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTriage the report in this order
-
Check the report categories and image pairs
Look at whether the report classifies images as new, missing, or changed, and inspect the names and pairs it presents. If images are reported as new, confirm that their expected counterparts exist and that the filenames and paths match the intended baseline. Use the labels shown by your own run; they can help distinguish a pairing problem from a pixel difference.
#1 Best Overall
-
Confirm synchronization and the expected key
Verify that
sync-expectedcompleted successfully. Find which expected snapshot key the configured key-generator selected, and make sure the publisher fetched the baseline for the branch or commit you intend to compare against. If the wrong key is selected, changing image thresholds will not restore the correct comparison. -
Match the capture conditions
Compare the baseline-generation setup with the current CI or local capture setup. Check browser and capture-tool versions, viewport dimensions, device scale factor, installed fonts, loaded assets, locale, timezone, and animation or timing state. Differences between CI and baseline environments can cause visual diffs. The specific variables to verify depend on the capture tool configured in your project. Storybook visual testing documentation
-
Inspect several representative diffs
Open a handful of images rather than assuming every reported difference has the same cause. Look for repeated symptoms: shifted layouts, altered text rendering, missing assets, or broad color changes. A pattern across many pages points you toward shared inputs such as the baseline key, fonts, browser, or common assets, but does not by itself identify which one is wrong. Reg-suit documents optional
x-img-diff-jsreporting to help expose inserted or moved regions. Reg-suit documentationThe Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Change tolerances only after validating inputs
Reg-suit documents several settings that affect comparison:
thresholdRatesets a ratio of differing pixels.thresholdPixelprovides an absolute differing-pixel alternative.matchingThresholdchanges sensitivity to YUV color distance.enableAntialiasignores pixels detected as antialiased.
The Reg-suit configuration example uses
thresholdRate: 0.05; that is an example value, not a universal recommendation. The relatedreg-cliproject also documents threshold rate. Reg-suit documentation reg-cli documentation Increasing tolerance can reduce noise, but it can also conceal small real regressions. Inspect diffs before accepting a setting. -
Refresh baselines only after reviewing the changes
If the visual differences are intentional, review and publish the new expected screenshots through your team’s normal baseline workflow. Do not refresh every baseline merely to make CI pass: an accidental rendering change or failed asset load could otherwise become the accepted expectation.
How to tell a shared setup issue from a page-specific change
| What you observe | What to check next |
|---|---|
| Many pages show similar layout, text, or color changes | Verify the expected key and fetched baseline, then check shared capture conditions, fonts, and assets. |
| Only particular pages differ | Inspect those page pairs for content, loading, or asset changes before changing global thresholds. |
| Images appear as new or lack an expected counterpart | Check filenames, paths, key selection, and whether synchronization retrieved the intended expected images. |
| Differences are small and concentrated around edges | Review antialiasing and color-distance settings, but confirm the capture environments match first. |
These are diagnostic clues, not proof of a cause. The report and configuration determine which explanation applies.
Capture screenshots consistently when regenerating a baseline
When an intentional change requires a new baseline, keep the capture setup stable between baseline creation and later comparisons. Record the capture-tool and browser versions, viewport and device scale, fonts, locale, timezone, asset-loading behavior, and animation or wait settings used by your project. Reg-suit compares the images it receives; it cannot make inconsistent capture inputs equivalent.
Best Value
Or skip the browser setup
If your goal is to produce fresh page screenshots for a visual check, ScreenshotNeo can capture a URL in one GET request. Its API can return PNG, JPEG, WebP, or PDF; the request below saves the default image response as WebP. Add format=png or another supported format if you need a different output. See the ScreenshotNeo API documentation.
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/consent banners, newsletter popups, and chat widgets before capture, with those steps individually switchable. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status. Its MCP server includes tools for AI agents to take screenshots, inspect page information, and capture PDFs. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan.
ScreenshotNeo is an alternative capture service, not a Reg-suit baseline or comparison fix: you still need to keep baseline and current capture settings aligned and review diffs before updating expected images.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently Asked Questions
Does reporting every screenshot as changed prove the application changed?
No. It means the comparison found differences or could not pair the images as expected; verify the fetched baseline, image mapping, and capture inputs before concluding the application changed.
Should I increase the threshold until the report passes?
Not before checking the baseline and capture setup. A higher tolerance can hide genuine visual regressions, so review representative diffs before changing comparison settings.
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.
