Screenshots and HTML snapshots

Before opening artifacts

Use this page when a scan or issue shows screenshot or HTML snapshot availability. Screenshots and HTML snapshots are evidence artifacts for the accepted scan run; they are not a separate scan scope, a guarantee that every hidden state was observed or a reason to include private pages. Review artifacts only after the scan is completed or after the product clearly says which page is still running. That keeps visual evidence, DOM evidence, console evidence and network evidence tied to the same scan run.

Open screenshot and HTML snapshot evidence

Follow the path `Scans → Scan detail → Worker readiness → Artifacts → View issues → Console and network evidence`.

1. Open /scans/{scanRun} from a completed scan. Result: the scan detail page shows the artifact availability for that exact run.
2. Check Worker readiness → Artifacts. Result: Screenshot, HTML snapshot and issue evidence availability are visible before interpreting the page.
3. Open View issues or the scanned page evidence entry. Result: the screenshot path shows the rendered page image, while the HTML snapshot path shows the rendered DOM artifact.
4. Compare artifact timestamps and status with the current scan status. Result: evidence is tied to the completed scan run, not a retry, stale preview or unrelated customer site.
5. If Screenshot unavailable or HTML snapshot unavailable appears, read the blocked reason before retrying. Result: timeouts, private paths, redaction and capture failures stay explainable.
6. Continue to Console and network evidence when artifacts exist. Result: visual and DOM evidence can be interpreted together with script and request errors.

What each artifact proves

Each artifact answers a different evidence question.

• Screenshot available means WebRiskOps stored the rendered page image that the browser worker could see.
• HTML snapshot available means WebRiskOps stored the rendered DOM artifact for later evidence review.
• Issue evidence available means at least one normalized finding can reference the captured page state.
• A screenshot does not prove hidden account states, checkout completion, private user data or pages outside accepted scope.
• Sensitive data in an HTML snapshot should be read with [Privacy redaction](/docs/projects/privacy-redaction) before sharing.

Missing artifact states

Missing artifacts should produce a customer-readable reason instead of a guess.

• Screenshot unavailable means the worker did not store a usable visual capture for that page.
• HTML snapshot unavailable means the DOM artifact was not stored or could not be retained.
• Artifact capture failed means retry only after the target is reachable and scope remains accepted.
• Evidence incomplete means use the available deterministic fields without inventing a missing screenshot or DOM state.
• Private path or redaction means do not bypass the boundary to capture a more complete artifact.

Continue to console and network evidence

After screenshot and HTML availability are clear, continue to [Console and network evidence](/docs/projects/console-and-network-evidence). That page explains how script errors, failed requests and blocked resources affect the same rendered evidence.