Monitor Screenshots

When a monitor goes offline, Pulsetic automatically captures a screenshot of the page at that exact moment. Instead of guessing what a 503 error or a timeout looked like to your visitors, you open the incident and see the real page: the error screen, the maintenance notice, the half-loaded layout, or your hosting provider's parking page.

Monitor Screenshots are available on the Team and Organization plans.

How to Enable Monitor Screenshots

You can turn screenshots on for a single monitor, or for every monitor in your account at once.

Step 1: Enable Screenshots for One Monitor

1. Open the monitor you want to capture.
2. Go to the Advanced Settings tab.
3. In the Checks section, tick Enable monitor screenshots.
4. Click Update.

Step 2: Enable Screenshots for All Monitors

1. Go to Account → General Monitor Settings.
2. In the Checks section, tick Enable monitor screenshots.
3. Click Update.

Settings applied here affect all of your existing monitors and every monitor you create afterwards.

Screenshots apply to HTTP monitors only. Port, ping and heartbeat checks have no page to capture.

Step 3: View a Screenshot

1. Go to the Incidents page.
2. Any incident with a capture shows a small image icon next to its root cause.
3. Click the icon to open the screenshot, along with the monitor name and the time it was captured.

Captures are full page, so they are often taller than your screen. Scroll inside the viewer to read the whole page.

Step 4: Download a Screenshot

Click Download in the viewer. The file is saved as yoursite.com-screenshot-2026-08-07-1346.png , so a folder of downloads stays sorted and self-describing. This is useful when you need to attach evidence to a ticket with your hosting provider, or share it with a developer who was not watching the dashboard at the time.

Understanding Screenshot Retention

Screenshots are stored for 90 days and then deleted automatically. If you need to keep one for longer, download it.

Understanding Why an Incident Has No Screenshot

• Screenshots were not enabled on that monitor when the incident happened. Enabling them does not backfill past incidents.
• The incident is a recovery ("Resolved") rather than an outage. Captures are taken at the moment a monitor goes down.
• The check failed before a page could be rendered at all, for example a DNS failure or a refused connection.
• The page could not be rendered within the capture timeout.

Screenshots are taken by our monitoring nodes as an anonymous visitor. Pages behind a login, and content that only appears after a visitor interacts with the page, will not appear in the capture.