How to Monitor Website Changes and Attach Before-and-After Screenshots to Email Alerts

To monitor website changes and receive before-and-after screenshots by email, use a scheduled visual monitoring service that explicitly includes both screenshots in its alert email. Add the public page, choose whether to watch the whole page or a specific region, set a check interval, and enable email notifications. Visualping’s help documentation describes alert emails with previous and current screenshots side by side, with additions highlighted in green and deletions in red. [Visualping: Navigating Alerts]

Screenshot attachment behavior matters: a service may email a text summary or a link to a change history without attaching the two screenshots. Of the services covered here, Visualping’s documentation explicitly describes before-and-after screenshots in alert email. The reviewed Distill and Wachete pages describe monitoring and notifications, but do not establish that their alert emails attach both screenshots.

1. Choose what to monitor

Start with the exact page and the change you care about. A whole-page monitor can catch broad visual changes, but headers, rotating banners, timestamps, ads, and other volatile areas may create noisy alerts. If the target is a price, policy paragraph, product availability notice, or event date, monitor that region when the service supports selecting an element.

• Whole page: use it when changes anywhere may matter, such as a home page redesign or a public status page.
• Specific region: use it when one section is the signal, such as a price, a release-notes area, or a posted deadline.
• Alert criteria: describe the type of change that should trigger an email where the service offers criteria. This can reduce alerts caused by irrelevant page movement.

Visualping supports whole-page or selected-element monitoring and lets users describe changes that matter. Its cloud monitors continue checking while your computer is off. [Visualping: What is Visualping?]

2. Configure monitoring and email alerts

1. Add the page URL. Use the canonical public URL and check that it opens without a login in a normal browser session. For a password-protected page, confirm that the selected service supports the needed authentication before relying on it.
2. Select the scope. Choose the whole page or the smallest useful region. Narrow scope is usually easier to interpret when unrelated parts of the page change often.
3. Set the check frequency. Match it to how quickly you need to learn about a change and how often the page is likely to update. There is no universal ideal interval: frequent checks can detect a change sooner, while less frequent checks reduce unnecessary checks and alerts.
4. Set alert criteria if available. Specify the content or type of change that matters. Review the first alert to see whether the criteria are too broad or too restrictive.
5. Enable email notifications. Confirm the monitor-level setting and any workspace-level mute or notification settings. Visualping says email notifications are enabled by default, but recommends checking the monitor setting when expected alerts are missing. [Visualping: Navigating Alerts]
6. Let the first check establish a baseline. A before-and-after comparison needs an earlier captured version. Confirm that an initial check has completed before expecting an alert for a later change.
7. Review the alert email. Visualping documents side-by-side current and previous screenshots, with new content in green and deleted content in red. Either screenshot opens a larger difference view. [Visualping: Navigating Alerts]

3. Use a service that documents screenshot emails

Service	Documented monitoring and alert capabilities	Evidence for screenshots attached to alert email
Visualping	Scheduled whole-page or selected-element monitoring; visual, text, and code changes; email notifications; cloud checks continue when your computer is off.	Its help documentation describes previous and current screenshots side by side in alert emails, with additions green and deletions red. [Source] [Source]
Distill.io	Selected page parts, background checks, custom frequency and notification conditions, cloud monitoring, and several notification channels.	The reviewed official homepage does not establish that email alerts attach before-and-after screenshots. Check its current documentation if that delivery format is required. [Distill.io]
Wachete	Whole-page or selected-area monitoring, dynamic and password-protected pages, ignoring volatile regions, change history, and email or digest alerts.	The reviewed official feature page describes additions and removals in change views, but does not establish screenshot attachments in email. [Wachete features]

Choose based on the evidence for the delivery format you need, the page type, and the available monitoring controls. Feature descriptions are vendor documentation, not a guarantee that every site will render identically on every check.

4. Keep the alerts useful

• Reduce visual noise: monitor a smaller region if navigation, rotating promotions, or other page areas change frequently.
• Check the rendering context: responsive layout, delayed content, location, and authentication can affect what the monitor sees. A region that is below the fold or loaded after a delay may need service-specific settings.
• Review a sample alert: confirm that the screenshot contains the relevant content and that highlighted changes are meaningful.
• Revisit the baseline after redesigns: a major page restructure can make a formerly useful selection inaccurate. Update the monitored region and criteria.
• Use cloud monitoring for unattended checks: Visualping says its cloud monitors continue when the computer is off; its local extension monitoring requires Chrome to remain open. [Visualping: What is Visualping?]

5. Troubleshoot missing or unhelpful emails

Symptom	Likely cause	What to check
No email after a page change	No check has run since the change, notifications are disabled, or the change did not meet the alert criteria.	Check the last run time, monitor notification setting, criteria, and workspace-level mute settings. Confirm the expected change is visible to the monitor.
Email is missing from the inbox	Spam filtering or a delivery rule may have moved it.	Search spam or junk, inspect mail rules, and confirm the address and service notification settings.
Email arrives but has no before-and-after images	The service or alert type may provide a link or summary instead of image attachments.	Check current documentation for the specific alert format. Visualping’s cited help describes screenshots in alert emails; the reviewed Distill and Wachete sources do not confirm the same behavior.
Too many alerts for irrelevant changes	The selected area is too broad, or volatile content changes often.	Select a smaller region where available and refine the alert criteria. Consider whether rotating banners, ads, timestamps, or dynamic content should be excluded.
Screenshot is blank or missing the target content	The page may require authentication, delayed rendering, or a particular browser or location context.	Open the page in a normal browser, verify the target is publicly accessible, and review the service’s supported page and rendering settings. The reviewed sources do not guarantee every dynamic page will render correctly.
Local checks stop when the computer is off	The monitor depends on a local browser or extension.	Use a cloud monitor if checks must continue while your computer is off. Visualping documents this distinction for cloud and local extension monitoring.

Or skip the browser setup

If you are building your own scheduled capture workflow, ScreenshotNeo is a website screenshot API and MCP server for developers. A screenshot API captures a page on demand; scheduling checks, comparing captures, and sending alert emails are application logic you must arrange around it. The API returns a PNG, JPEG, WebP, or PDF and supports capture options such as full-page capture, element selection, custom waits, and caching. 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.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

To turn captures into before-and-after email alerts, save a baseline image, take later captures on your chosen schedule, compare them, and send an email when your change rule is met. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.

Performance, reliability, and cost

A scheduled monitor’s detection delay depends on its check interval: a page change that occurs just after a check may not be noticed until the next one. Faster intervals can shorten that wait, but may use more of a plan’s checks. Select an interval based on the consequence of missing a change and the page’s update cadence rather than assuming that the fastest setting is always necessary.

Cloud monitoring can keep checks running when your computer is off; local extension monitoring may depend on the browser remaining open. Dynamic content, access controls, and notification settings can affect what is captured and delivered. Treat the service’s change history and a sample alert as part of setup, and periodically confirm that the monitored region still matches the page.

For ScreenshotNeo API usage, each successful clean capture is billed according to the selected plan; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers indicating page verdict and billing. Plans are Free for 1,000 shots per month with no card, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. Every feature is on every plan. These are capture-plan prices, not a complete estimate for any separate scheduler, image-difference process, email provider, or storage you add.

FAQ

Will every website monitor attach two screenshots to its email?

No. Verify the alert format in current documentation. The Visualping help source cited above explicitly describes current and previous screenshots in alert email; the reviewed Distill and Wachete sources do not confirm that behavior.

Can a monitor check while my laptop is shut down?

Cloud monitors can run on the service’s servers. Visualping documents that its cloud monitors continue when your computer is off; local extension monitoring requires Chrome to remain open.

How often should I check a page?

Choose an interval based on how quickly you need to know and how often the content changes. The available research does not establish one interval that suits every page.

Can I build email alerts with a screenshot API?

Yes. Capture a baseline and later images on a schedule, compare them, and send an email when your rule detects a meaningful change. The API handles capture; scheduling, comparison, and email delivery are parts of the surrounding application.