Create a bug report with annotated full-page screenshots
Capture the page where a bug appears, number each problem, and send developers one clear file they can act on.
You’ll need
- The page where the bug appears
- Capurize installed and pinned
Steps
- Reproduce the bugGet the page into the broken state first: open the menu, submit the form, or switch to the account that shows the problem.
- Capture the full pagePress Alt+Shift+P. A full-page capture shows the bug in context, including anything above or below it that a developer might need.
- Number each issueIn the Studio press N and click next to each problem. Numbers increase automatically, so you can refer to “#2” in your ticket.
- Point and explainPress A to draw an arrow at the exact element, then T to add a one-line note such as “Total doesn’t include tax”.
- Hide test dataPress B and drag over emails, names or order numbers. Choose Solid for anything that must not be readable.
- Export or copyClick the download button for a PNG, or press Ctrl+C with nothing selected to copy the page straight into your issue tracker.
Result: One annotated image (or a multi-page PDF for long pages) that shows exactly what is wrong and where, with sensitive data removed.
Tips
- Set the file-name pattern in Options to {domain}_{date}_{time} so captures sort by site and time.
- If the bug only appears at a certain width, resize the browser window before capturing.
- Keep one capture per page and number the issues, rather than sending many cropped screenshots.
Who uses this workflow
Full-page screenshots for QA testers
Capture complete pages, number each defect, redact test data and send developers one clear file.
Full-page screenshots for web developers
Document layouts, share reproducible bug evidence and keep before-and-after records of changes.
Screenshots for product managers
Capture product flows, annotate feedback and turn screens into specs, reviews and release notes.
Related guides
Full-page screenshots for website QA and bug reports
A practical workflow for capturing, numbering and reporting website issues so developers can fix them quickly.
How to annotate screenshots for clear design feedback
Make design and content feedback unambiguous with arrows, callouts, highlights and numbered points on the live page.
How to redact sensitive information in screenshots safely
Why a black box isn’t always enough, the difference between blur, pixelate and solid redaction, and a checklist before you share.
Do this with Capurize
Full-page capture, annotation, redaction and PDF export, free during launch.