Back to Blog

Run Visual Monitoring Every X Hours, Not Just Once a Day

Diffy scheduled monitoring can now run every 1 to 23 hours. Catch visual breakages from deploys, auto-updates and third-party scripts within hours instead of a day.

Yuriy Gerasymov
Yuriy Gerasymov
18 Nov 2026 · 5 min read

Daily visual monitoring has a blind spot, and it is about 23 hours long.

If Diffy checks your site at 6:00 AM and something breaks at 9:00 AM, nobody hears about it until tomorrow morning. For a lot of sites that is fine. For a store running a sale, a site with several deploys a day, or a WordPress install with auto-updates turned on, a day is a long time for a broken checkout button to sit in production.

So scheduled monitoring now has a third option next to Every day and Specific days: Every X hours. Pick a number from 1 to 23, and Diffy takes fresh screenshots and compares them on that interval, around the clock.

It is available on every plan, the free plan included.

What changes during a day

The reason to check more often is that production changes more often than most teams think, and much of it does not go through a deploy you would test anyway:

  • Automatic updates. WordPress runs its update checks twice a day, and plugins with auto-updates enabled install themselves on that schedule. We wrote about what tends to break during WordPress and Drupal updates.
  • Third-party scripts. Chat widgets, cookie banners, A/B testing tools and tag managers are loaded from someone else’s server and change when they decide to.
  • Content and configuration edits. An editor publishes a page with a 4000-pixel image, or someone changes a block setting in the CMS.
  • Hotfixes. The deploy that “only changes one line” and skips the usual review.
  • Infrastructure. A CDN cache purge, a font that stops loading, a CSS file served stale on one region.

None of these wait for your daily check. Running monitoring every few hours shrinks the time between “it broke” and “we know it broke” from up to a day to a few hours.

How it works

Monitoring works the same as before, just more often. On each run Diffy takes a fresh set of screenshots of every page in the project, at every breakpoint you have configured, and compares them with what you chose in the Environments setting:

  • Fresh Production vs Last Production (the default): each run is compared with the previous run, so you see what changed in the last X hours.
  • Fresh Production vs Baseline: each run is compared with a set of screenshots you approved, so a change stays visible until you accept it. See two ways to use a baseline set.
  • Fresh Production vs Fresh Staging (or development): useful when you want to know, several times a day, whether the two environments have drifted apart.

The results land where they always do: in the project’s comparison list and in whatever notifications you have set up for the project. Diffy’s comparison algorithm and masking rules are the same for scheduled and manual runs, so a page that is stable in your daily monitoring stays stable when it runs every two hours.

The first run happens within half an hour of saving the schedule. Diffy checks schedules every 30 minutes, and from then on each run starts X hours after the previous one.

How to set it up

For a new project: in the create-project wizard, choose to compare on a schedule. In the How often row, open the dropdown, pick Every X hours and enter the number. The time and time zone fields disappear, since they don’t apply to this schedule.

For an existing project:

  1. Open the project and go to Settings → Monitoring.
  2. Under Schedule, select Every X hours.
  3. Enter a whole number of hours from 1 to 23.
  4. Check the Environments row is comparing what you want, then save.

The project list will show it as “monitoring every 6 hours” (or whatever you picked), so you can see at a glance which projects run on which schedule.

If you manage several projects in a team, the same option is in the team’s default project settings, so new projects can start with it.

Picking the interval

There is no right number, but a few patterns work well:

  • Every 1–2 hours for the handful of pages that make money: checkout, pricing, sign-up, the main landing page. Put them in their own small project so frequent runs stay cheap.
  • Every 4–6 hours for a typical business site or store with auto-updates on. You catch an overnight update before the morning traffic and a lunchtime deploy before the end of the day.
  • Every day for large content sites where most pages change slowly and you mostly care about templates.

Every run takes screenshots, so frequency and page count trade off against your monthly allowance. A project with 20 pages at 3 breakpoints, compared with the last production run, takes 60 screenshots per run. Every 6 hours that is 240 a day, roughly 7,200 a month. The same 20 pages once a day is about 1,800. Check pricing if you are planning to run a large project hourly.

FAQ

How often can Diffy monitoring run?

Every 1 to 23 hours, in whole hours. For once a day or less, use the Every day or Specific days schedules, which also let you pick the exact time and time zone.

Which plans include monitoring every X hours?

All of them, including the free plan. Every run takes screenshots, so it uses your monthly screenshot allowance the same way any other comparison does.

When does the first run happen?

Within half an hour of saving the schedule. Diffy checks schedules every 30 minutes, so after that each run happens X hours after the previous one, on the half-hour.

Can I still choose what each run is compared against?

Yes. The Environments setting works the same as for daily monitoring: compare fresh production with the previous production run, with a baseline, or with another environment.

How many screenshots does it use?

Pages times breakpoints for each new set of screenshots, times the number of runs. 20 pages at 3 breakpoints compared with the last production run every 6 hours is 60 screenshots per run, 240 a day.

Try it

If you already have a project with daily monitoring, switching it to every X hours takes one setting. If you don’t, create a free account, add the pages you care about most, and set the schedule in the same wizard.

Related Articles

More guides on visual regression testing, QA automation, and keeping your site pixel-perfect as it changes.