Skip to content

Screenshot monitoring

See when your website changes visually.

A page can still return HTTP 200 while its layout, images or visible message have changed. Scheduled screenshots give you a visual record to investigate.

Keep a record of the page your visitors see

Useful for public landing pages, product pages and release checks.

A stylesheet update can move a headline, a missing image can leave a blank space, and a product page can switch from available to sold out. A response-only check may not explain the visible result. RegressionRadar opens the URL in Chromium and captures the full page so you can inspect changes across measurements.

Use this for periodic checks after a deployment, a visual history of your homepage, or changes to a public product listing. A captured difference is a reason to review the page; it does not establish whether the change is a defect.

Build for what’s next.

A modern platform for ambitious teams to build, ship, and grow.

Illustrative baseline: the original headline.

Build for what’s next. Together.

A modern platform for ambitious teams to build, ship, and grow.

Illustrative change: a word added to the headline.

From URL to screenshot comparison

Use the screenshot method on a web monitor.

  1. 01

    Choose a public page

    Create an account, add a monitor with a descriptive name and URL, and choose the screenshot probe. Use the page you want to observe, such as a campaign landing page.

  2. 02

    Set a realistic schedule

    Choose an interval and timeout, then enable the monitor. Chromium renders the page before a full-page PNG is captured. Checks are scheduled observations; they can miss a change that appears and disappears between runs.

  3. 03

    Establish the baseline

    The first-ever streak creates the starting record without sending a change notification. Matching HTTP status and screenshot hash continue that streak; a change to either starts another.

  4. 04

    Investigate and add alerts

    Open measurement history and compare available captures. Configure email or Teams rules for the streak changes you want to hear about. Review the image and the target page before deciding what to fix.

Follow the screenshot guide with application screenshots.

Three practical screenshot monitoring examples

Keep each monitor focused on a page with a clear purpose.

Landing page after a release

Monitor the public campaign URL. Compare captures when the headline, hero image or call to action moves. You get a record of the changed appearance, rather than an automated verdict about conversion impact.

Product availability

Watch a product page where the availability message is rendered by JavaScript. A screenshot can show the visible message that a raw HTML check may not contain. Rotating recommendations elsewhere on the page can also trigger a change.

Broken styling or missing assets

Capture an important page periodically to spot a changed layout or missing image during review. The comparison helps investigate what rendered at that time; it does not test every link or user action.

What screenshot monitoring can and cannot tell you

Stable pages make the history easier to interpret.

  • Screenshot hashes are byte-exact. There is no perceptual tolerance or configurable difference threshold. Animations, clocks, ads and rotating banners can create a new streak on every check.
  • The capture covers the full page. HTML CSS selectors do not crop or filter screenshot checks. Use HTML selection when a stable server-rendered section is the real target.
  • The application uses a configured Chromium viewport. A capture is one browser view, not coverage of all devices or responsive breakpoints.
  • There is no scripted sign-in, form submission or checkout journey in the monitor workflow. Choose a URL reachable without those steps.
  • Slow pages can time out. Oversized images can still be hashed without being stored; historical comparison requires available captures.

Plan the cost of your checks

Choose a schedule, then leave room for notifications and your other monitors.

Each screenshot check uses 5 credits, including failed checks. Each successfully sent email or Teams notification uses 1 credit. Failed or skipped notifications use none.

For one URL over a 30-day month, daily checks use 150 credits; hourly checks use 3600 credits, before alerts. Actual totals depend on the number of days and completed checks. Adding monitors multiplies the check budget.

The Free plan includes 50 credits per month: up to 10 checks if you spend the entire allowance on this method and send no notifications.

  • Bronze: 1,000 credits per month at US $9.99 per month, excluding VAT.
  • Silver: 10,000 credits per month at US $19.99 per month, excluding VAT.
  • Gold: 100,000 credits per month at US $29.99 per month, excluding VAT.

Credits are shared across all monitors and sent notifications and reset each calendar month (UTC). An action needs enough credits for its full cost; when the allowance is exhausted, checks and alerts pause until the next month or a plan upgrade. A paid plan has an end date; Free limits apply after expiry.

Compare plans, trial and extension terms and review usage forecasts in your account before increasing check frequency.

Explore monitoring by use case

Start with the change you need to detect, then choose the right probe.

Screenshot monitoring

Track landing pages, product availability and visible layout changes with full-page Chromium captures.

HTTP and HTML change monitoring

Watch pricing, release notes or important page sections with response comparisons and CSS selectors.

API response monitoring

Follow public JSON responses and status changes without rendering a browser page.

Start for free

Make the next change easier to spot.

Choose a page and start monitoring with the free plan. No obligations whatsoever. Free forever.