Use case
Screenshot workflow for QA and bug reports
QA screenshots require enough context to reproduce a problem without leaking unnecessary data.
Capture
Take a full scroll capture of the broken page, or a region around the defect, so the developer sees the layout, the error, and the state in one image.
Annotate
Draw boxes and arrows to the exact element that failed and add text callouts with the expected versus actual behaviour right on the screenshot.
Attach
Export a PNG or a paginated PDF, then drop it into the bug report yourself since Captorify does not write into trackers for you.
What a useful bug report has to show
QA captures have to carry enough context to reproduce the issue while keeping test accounts and tokens out of the picture. Captorify covers the full-page capture, the markup, and the cleanup in one browser workflow.
Redaction and source context
Staging screenshots often show seeded test accounts, session tokens, or API keys in a debug panel. Manual and suggested redaction let you black those out permanently before the report leaves your browser, and suggested redaction flags common token and key patterns for review (Pro). For source context, a PDF export can carry an optional URL and timestamp overlay so the developer knows exactly which page the bug came from (Pro).
- Annotations and crop, redaction and the PDF URL overlay.
- Suggested redaction matches token and key shapes, including Stripe-style keys and high-entropy strings, and asks you to confirm.
- A clean PNG for inline context or a paginated PDF for a full repro both export on the free tier.
A repeatable bug report shape
A consistent report shape makes a screenshot far easier to act on. Anchor each report on the annotated capture and keep the same fields around it so triage does not have to chase missing detail.
- Steps to reproduce, with the annotated full-page capture attached.
- Expected versus actual behaviour, called out directly on the image.
- PDF URL and timestamp overlay when you enable it (Pro).
Capture limits worth knowing
Plan around the limits so a developer does not get a silently cut or blank image.
- Lazy-loaded images may appear blank if they have not loaded by the time their tile is captured.
- Very tall pages are clamped with a truncation warning that shows captured versus total height.
- For a page past the cap, capture it in sections and combine them rather than relying on one giant image.