Bug Report with Screenshot and Console Logs: What to Include

A screenshot tells a developer what the page looked like. It almost never tells them why it broke. The why lives in the console and the network tab, and most bug reports leave both out.
What the Screenshot Gets Right
A screenshot proves the symptom and shows the state of the UI at the moment it failed. It is the fastest way to confirm you are both looking at the same thing.
What the Screenshot Misses
- Console errors: The exception message and stack trace usually name the file and line that failed.
- Failed requests: A 500 or a blocked CORS request explains many "the button does nothing" reports.
- Timing: Which action came first. A request that fired before the user clicked points to a different cause than one that fired after.
How to Capture Console Output Without Guessing
- Open DevTools before reproducing the bug, so nothing is lost on page load.
- Reproduce once, and keep the console and network panels as they are.
- Copy the first error, not the last. The first error is usually the cause, and later ones are often side effects.
- For network failures, note the URL, the status code, and the response body if it is short.
Attach Both, Labeled
Put the screenshot first, then the error text in a code block, then the failing request. A label such as "Console: TypeError at checkout.js:42" lets the developer jump straight to the line.
Keep Sensitive Data Out
Before you attach logs, remove tokens, cookies, and personal data. Authorization headers and session identifiers should never appear in a bug report. A tool that redacts these automatically reduces the risk, but check the output anyway.
Conclusion
The screenshot shows the symptom and the console shows the cause. Include both, label them, and remove anything sensitive before you send the report.
Found this article valuable? Share it with your team
Help fellow developers and QA engineers triage bugs faster and maintain reliable web apps.