To monitor website changes with screenshots, keep a fixed list of the pages you care about, capture all of them at the same size on a regular rhythm, such as every Monday morning, and save each run into its own folder named with the date. Comparing this week's folder with last week's shows what changed: new prices, redesigned pages, removed products or new messaging. It is a simple, visual record that anyone on your team can review, and it keeps a dated history you can go back to.
This guide walks through building the page list, choosing capture settings, setting up the routine, and comparing runs efficiently. It also covers what screenshots will and will not tell you.
Why use screenshots to track changes
Text-based change monitors alert you when the code or text of a page changes. That is useful, but it is noisy, and a list of changed lines is hard to interpret. Screenshots show the page the way a visitor sees it:
- Competitor tracking: pricing pages, offers, product ranges and home page messaging.
- Client sites: spotting edits made by someone else, broken layouts or expired banners.
- Your own site: a dated record of what was live and when, useful when someone asks "what did the page say last month?"
- Compliance: evidence of the terms, prices or disclaimers that were displayed on a given date.
- Research: how a market's websites evolve over months or years.
Step 1: Build a focused page list
Monitoring works best with a small, deliberate list rather than every page on every site. Choose pages where change matters to you:
- Home pages, for headline messaging and offers.
- Pricing and plan pages.
- Key product or category pages.
- Terms, shipping and returns pages, if policies matter to you.
- "About" or team pages, if you track staffing or positioning.
Put one URL per line in a text file, or keep the list in a spreadsheet column and save it as CSV. Our guide to screenshotting every URL in an Excel list covers cleaning up a spreadsheet of addresses. Keep the list in a fixed order and add new pages to the end, so captures stay comparable from run to run.
Step 2: Choose consistent capture settings
Comparisons only work when every run uses identical settings. Decide once and write them down.
| Setting | Recommendation | Reason |
|---|---|---|
| Capture type | Full page | Changes far down the page are included |
| Width | 1920 px, plus 390 px if mobile matters | Covers desktop and phone layouts |
| Load delay | 3 to 5 seconds | Lets images, fonts and banners load |
| Format | PNG, or JPG for very large lists | PNG is sharp; JPG saves space over many runs |
| File name | Domain plus counter | The same page gets the same name in every run |
| Folder | One sub-folder per run, named with the date | Runs sit side by side and never overwrite |
Dated folders are the key to the whole system. A structure like D:\Monitoring\2026-10-05\, D:\Monitoring\2026-10-12\ means each run is complete on its own, and finding the same page across weeks is a matter of opening the same file name in different folders. Our guide to organizing screenshots into folders automatically has more on folder patterns.
Step 3: Set a routine
How often to capture depends on how fast the pages change and how quickly you need to know.
- Weekly suits most competitor and client monitoring.
- Daily suits pricing pages in fast-moving markets, news pages or launch periods.
- Monthly suits long-term records, policies and research archives.
Pick a fixed time, such as Monday at 9 a.m., and put a recurring reminder in your calendar. Running at the same time each week also avoids differences caused by time-of-day content, such as lunch offers or "open now" labels.
Step 4: Capture the pages
Bulk Captures is built for this kind of repeated batch on Windows. Load the same URL list each time, keep the same full-page or viewport choice, widths and delay, and set the folder pattern to include the date so every run goes into a new sub-folder automatically. Click Capture and it visits each page, waits for it to load, retries any that fail and saves every screenshot.
Two limits to be aware of: Bulk Captures does not schedule runs, so you start each run yourself when your reminder comes up, and it does not compare images, so spotting the changes is your job (the next section makes that quick). Because it remembers its settings, a weekly run is a few clicks.
Leave the PC awake while a large batch runs. If Windows goes to sleep partway through, the remaining pages will not be captured until it wakes.
Step 5: Compare runs quickly
With identical file names in dated folders, reviewing changes is straightforward:
- Open two runs side by side. Snap last week's folder to the left of the screen and this week's to the right, and switch both to Large or Extra large icons.
- Scan the thumbnails. Big changes such as new hero images, new layouts or missing sections are visible straight away.
- Check dimensions. Switch to Details view and add the Dimensions column. A page that grew or shrank in height almost always changed in content.
- Flip between pairs. For pages that look similar, open both versions in a browser or the Photos app and switch quickly between them. Moved or changed elements jump out.
- Note what you found in a simple log: date, page, change, and any action needed.
If you need pixel-level comparison, a separate image diff tool can highlight differences between two files. For a structured before-and-after process around releases, see our guide to visual regression testing with screenshots.
What screenshots will not show
Screenshots are a record of what was visible, so be aware of the gaps:
- Hidden changes: metadata, page titles, structured data and tracking code do not appear in a screenshot.
- Personalized content: prices or offers that vary by location, login or cookies may differ from what other visitors see.
- Pages not on your list: new pages added to a site will not be captured until you add them. Re-importing a site's sitemap from time to time helps; see screenshotting every page of a website.
- Changes between runs: a sale that starts and ends within a week will be missed by weekly captures.
Keeping the archive manageable
Weekly full-page captures of 50 pages add up. Save JPG at a high quality setting if storage matters, keep the PNG format for the pages where text detail is important, and archive older runs to an external or network drive each year. Because every run is self-contained in its dated folder, moving or zipping old runs never breaks anything.
Frequently asked questions
How often should I screenshot pages to track changes?
Weekly suits most competitor and client sites. Pages that change daily, such as pricing or news pages, may need more frequent runs.
How do I keep each run separate?
Send each batch to its own sub-folder named with the date, so every run is kept side by side and nothing is overwritten.
Will screenshots show every change?
Only visible changes. Changes to hidden text, metadata or pages you did not include in your list will not appear.
