Consent overlay covers content
That can be valid audit evidence; this demo deliberately does not remove the banner.
Visual audit evidence
Website audit screenshots for desktop and mobile evidence
One URL produces the two viewport artifacts an audit needs, without pretending a screenshot replaces accessibility, SEO or performance checks.
Capture settings
Enter the source, choose your options, then run the capture.
Result
Your capture will appear here and stay in view.
waiting
No result yet
Complete the settings and run the tool. Images, PDFs, text, and video all preview in this panel.
Send this exact request
cURL, TypeScript and Python are generated from the same configuration as the demo.
curl --fail-with-body "https://api.pagecapture.dev/v1/take" \
-H "X-Access-Key: $PAGECAPTURE_KEY" \
-H "Content-Type: application/json" \
--data '{"url":"https://example.com","format":"png","viewport_device":"desktop_1280"}' \
-o capture.pngTwo real viewports
Desktop and mobile run as separate captures, so both artifacts can be inspected and retained.
Honest first visit
The demo keeps consent overlays because they are part of what a new visitor sees.
Versioned devices
Preset changes create a new catalog version instead of silently changing old audit rules.
Evidence, not a score
The API returns artifacts and metadata; it does not invent an accessibility or SEO grade.
Use this when
- An audit needs reproducible desktop and mobile evidence.
- The original cookie banner and first viewport are part of what is being assessed.
Do not use this when
- You need Lighthouse metrics or DOM accessibility rules.
- A single decorative thumbnail is the final deliverable.
Workflow
From input to verified artifact
- 01
Submit one URL
The demo creates two independent requests for the same page.
- 02
Render two viewports
Desktop and mobile presets capture what each visitor receives.
- 03
Attach evidence
Download both artifacts and associate them with the audit record.
DIY in hours and operational risk
Keep the browser when that is the simpler system.
A two-viewport script is simple; scheduling, evidence retention and failure attribution are the operational parts.
DIY is a good fit when
- • Audits are manual and an operator reviews every browser run.
- • The evidence never leaves an internal controlled environment.
No default is supplied: we do not invent engineering-hour savings.
Responsibility and risk transferred
Repeatability
Unversioned devices make comparisons change without an audit rule changing.
Partial failure
One missing viewport can silently leave an incomplete evidence set.
Workload pricing
500 two-device audits
This is an editable scenario, not a savings claim. Only successful captures that miss cache are billable.
- Billable successes
- 980
- Smallest included plan
- Basic
- Published monthly price
- $10.00
Each audit uses 2 captures in this scenario.
Tested and reviewed
Written by PageCapture Engineering. Reviewed by PageCapture API maintainers. Last tested 2026-08-11.
cURL, TypeScript and Python executed against controlled fixtures; request contract and artifact format verified.