Screenshots, PDFs, and output capture

Use this page when you need the right artifact for review, QA, export, or debugging.

Core idea Different browser artifacts answer different questions, so one generic capture habit is rarely enough.

Artifact chooser

Choose output based on what you need to prove

Visual proof

Best when the question is how the page looked.

Visual + refs

Best when the visible state and the current refs both matter.

Interactive structure

Best when the real question is what the page exposed for action.

Exported output

Best when the document output itself is the deliverable.

Capture discipline

use full-page capture only when long-layout review matters
pair screenshots with snapshots when review needs structural context
verify the artifact after capture rather than assuming it preserved what mattered

Profile caveat

If a capture workflow seems missing or narrower than expected, check whether the current profile type is limiting the output surface.

Next route

QA lane

Turn captures into repeatable layout evidence.

Action model

Understand the interaction model behind labeled captures and snapshots.

Troubleshooting

Use capture artifacts to support the right diagnosis lane.