Skip to content
Full Page Screenshot

Full page screenshots for QA testing

Short answer

QA evidence is only useful if it shows enough context to reproduce the defect. A full page capture records the whole state — the broken element, the surrounding layout, and any error banners further up that a crop would have missed.

Updated 13 August 2026Written by the Full Page Screenshot team

What makes evidence usable

The whole page, not the defect
The cause is frequently outside the crop. A validation error at the top of a form explains a disabled button at the bottom, and only a full page capture has both.
One capture per state
Before the action, after the action. Two full page images make a state transition unambiguous in a way a description does not.
Annotations that point, not decorate
One arrow at the thing that is wrong. Ten highlights make a reader hunt.
Redaction before filing
Test environments carry real-looking personal data and trackers are often more visible than assumed. Blur before saving.

Settings for test evidence

Format
PNG, or JPG where the tracker caps attachment size
Environment
Staging and localhost both work
Nested panels
Click inside the panel before capturing
Retention
Captures are cleared after 2 hours — save what you need

Frequently asked questions

Can I capture a staging environment behind auth?

Yes. The capture runs in your signed-in browser session.

How do I capture a modal or error state?

Trigger it, then capture. Anything visible on screen is included, and fixed overlays are preserved.

Does the capture affect the page under test?

It scrolls the page and temporarily neutralises fixed positioning, then restores everything. It does not fire synthetic events or alter application state.

Capture your first full page screenshot

Free, no account, and nothing leaves your computer.

Keep reading