Quick answer: A good support ticket screenshot shows the full error message, enough of the page to see where you are (including the address bar for web apps), and the state right before or after the problem. Add one box or arrow pointing at the issue, hide passwords and other people’s personal data, and write in the ticket what you clicked, what you expected and what happened.
Support teams see hundreds of screenshots a week. The ones that get problems solved fastest have a few things in common, and the ones that lead to “can you send another screenshot?” are missing the same few things. Here’s what to include, what to leave out, and a template you can copy.
What a support ticket screenshot should show
| Include | Why support needs it |
|---|---|
| The whole error message, uncropped | Error codes and exact wording point to the cause |
| The page or screen you were on | The same error can mean different things on different pages |
| The address bar (web apps) | The URL shows the exact page, environment and sometimes the record ID |
| What you clicked or entered | Lets them reproduce the problem |
| Date and time, if visible or in the text | Helps them find your request in their logs |
| Your account or workspace name | Only if it helps them find your account; otherwise mention it in text |
What to leave out
- Passwords, one-time codes and API keys. Support never needs them. If one is in a screenshot you already sent, change it.
- Full card or bank numbers. Last four digits are enough to identify a payment.
- Other people’s personal data: customers, colleagues, patients. Cover names, emails and phone numbers with solid boxes.
- Unrelated tabs, notifications and chat windows. Crop them out.
How to hide details properly: black out text in a screenshot and hide bank and card details.
Step by step: a screenshot support can act on
- Reproduce the problem so the error is on screen.
- Capture the window, not your whole desktop. On Windows press Win+Shift+S and choose Window; on Mac press Cmd+Shift+4, then Space.
- Make sure the full error and the address bar are visible.
- Add one box or arrow around the problem.
- Cover private data with solid boxes.
- Save as PNG so text stays sharp.
- Attach it to the ticket with a short-written description.
When one screenshot isn’t enough
- Multi-step problems: send two or three screenshots, numbered in order, or a short screen recording.
- Something that “flickers” or disappears: a 10–30 second screen recording shows it better than any screenshot.
- Visual glitches: include a “this is how it normally looks” screenshot for comparison.
- Web app errors: support may ask for browser console messages. In Chrome, press Ctrl+Shift+J (Cmd+Option+J on Mac) and screenshot the red errors.
A template for your ticket
What I was trying to do:
[e.g. Export last month's invoices as CSV]
What I did:
1. Opened Billing > Invoices
2. Selected October 2026
3. Clicked Export
What I expected:
A CSV file downloads.
What happened instead:
Error "Export failed (code 502)". Screenshot attached.
When: Nov 21, 2026, about 10:15 (GMT+6)
Browser / device: Chrome 142 on Windows 11
Happens every time / sometimes / once
Filling in these lines usually saves at least one back-and-forth with support.
Make it faster next time
If you report issues in web apps often, a screenshot tool that captures and annotates in one place saves time. Z-Shot, our Chrome extension, captures the visible area or a single element, adds boxes, numbered steps and redaction in its free editor, and its Pro plan can add the page URL, browser, OS and screen size automatically in a format ready for GitHub or Jira. Captures stay in your browser until you attach them.
For developer-facing reports, see how to write a clear bug report with screenshots, and for teams handling customer data, screenshot privacy for support teams.
A clear support ticket screenshot saves a round of back-and-forth, so it is worth the extra minute.
FAQ
What should a screenshot for a support ticket include?
The full error message, the page you were on (including the address bar for web apps), what you clicked or entered, and one box or arrow pointing at the problem.
Should I include my password in a support screenshot?
Never. Support teams don’t need passwords, one-time codes or API keys. If one appeared in a screenshot you sent, change it.
Is a screenshot or a screen recording better for support?
A screenshot is best for error messages and visual problems. A short screen recording is better for multi-step problems or things that flicker or disappear.
What format should a support screenshot be?
PNG, so text stays sharp. Capture just the relevant window rather than the whole desktop.
How do I hide customer data in a support screenshot?
Cover names, emails, phone numbers and account details with solid boxes in an image editor, then save a new copy before attaching it.
Try it free: Z-Shot captures full pages, records your screen, and blurs or redacts sensitive data right in Chrome. Free plan, no account needed, and nothing is uploaded.




