Sincron Screen ToolsShare selection
Sales dashboard · 2026
Sales by region — September
Monthly revenue compared with August
Total
$1.25M
+4.2% vs. August
$412K
East
$296K
South
$262K
West
$198K
Central
$77K
North
down 41% here
For support, QA and developers
Screenshots for bug reports.
A screenshot with the full error, enough context and one arrow in the right place gets a ticket resolved faster. Here is what to show, how to mark it up and what to hide before you paste it into Jira, GitHub or Teams.
Download free for WindowsSee the workflowWindows 10 & 11 · capture and annotation are free, with no limits
Sales dashboard · 2026
Sales by region — September
Monthly revenue compared with August
Total
$1.25M
+4.2% vs. August
$412K
East
$296K
South
$262K
West
$198K
Central
$77K
North
down 41% here
Draw here
Hold Shift for a straight line, Ctrl for a rectangle and Ctrl + Shift for an arrow.
For support, QA and developers
What makes a good screenshot for a bug report?
A good bug screenshot shows the error and where it happens: the complete message, the screen or field where it appeared and, when it matters, the URL, environment or version. An arrow or a box says where to look, and a short label says what is wrong.
The screenshot supports the written report. Steps to reproduce, the expected result and the actual result still need to be written out, as Mozilla's bug writing guidelines recommend. Error messages and logs go in as copied text so the person handling the ticket can search for them.
On Windows, Win + Shift + S crops and the Snipping Tool marks it up. With Sincron Screen Tools, Ctrl + Shift + D marks the problem on screen and Ctrl + Shift + C captures it with the marks, ready to paste with Ctrl + V.
Reviewed on October 3, 2026
Checklist
What a bug screenshot needs to show
The full error message
Including the code, date and time when they appear. A crop that cuts off the last line of the message means someone has to ask for another screenshot.
Where it happened
Keep enough of the screen to recognize it: the title, menu or header. A red field with no context doesn't say which screen the error is on.
One mark per problem
An arrow or a box right on the problem. Two problems means two screenshots, or two marks with different labels.
The input you used
The value you typed, the filter you applied and the environment (staging or production) explain half of all bugs. If they don't fit in the screenshot, put them in the ticket text.
Expected versus actual
A label such as "should be $120" next to the wrong value shows the gap without anyone reading the whole ticket.
Nothing else
Customer data, tokens, other tabs and notifications stay out. Tickets travel further than you think.
Step by step
A 5-step workflow for bug report screenshots
From the error on screen to a screenshot pasted into the ticket, with no file saved along the way.
Reproduce it and stop on the error
Walk through the path until the problem shows up and leave the screen on it. Write the steps down as you go: they belong in the ticket text.
Mark it on screen
Press Ctrl + Shift + D. Hold Ctrl + Shift and drag for an arrow, hold Ctrl for a box around the field, and press T to type a short label. The app stays open underneath.
Capture with the marks
Press Ctrl + Shift + C and drag over the area that gives the error its context. The crop keeps your drawings and opens in the Screenshot Studio. For tickets, turn the Frame switch off if you want just the crop, with no background or padding.
Paste it into the ticket
Click Copy image and paste with Ctrl + V into Jira, GitHub or Teams. If your ticketing system only takes attachments, use Save PNG and drag the file in.
Write the rest as text
Steps to reproduce, expected result, actual result, version and environment. Copy the error message as text as well as showing it, so it turns up in search.
Where to paste
How to attach a screenshot in each tool
| Tool | How to attach | Note |
|---|---|---|
| Jira Cloud | Drop or paste the image onto the work item | Files can also go into comments and other long text fields |
| GitHub Issues | Drag, select or paste into the comment box | Images up to 10 MB |
| Microsoft Teams | Paste with Ctrl + V in the chat or attach with the paper clip | Per Microsoft, images pasted directly in chat don't use permission-based sharing |
| Slack | Drag into the message field or use the + button | Up to 10 files at a time |
Per Atlassian, GitHub, Microsoft and Slack documentation, checked on 2026-10-03.
Mark it before you capture
Arrow, box and label in seconds
Draw on the panel the way you would on the broken app: a box around the wrong value and an arrow with a short label.
Sales dashboard · 2026
Sales by region — September
Monthly revenue compared with August
Total
$1.25M
+4.2% vs. August
$412K
East
$296K
South
$262K
West
$198K
Central
$77K
North
down 41% here
Draw here
Hold Shift for a straight line, Ctrl for a rectangle and Ctrl + Shift for an arrow.
Real limits
Before you paste, and what Sincron doesn't do
Check for customer data
Emails, phone numbers, account numbers and tokens in the URL travel with the screenshot. Crop them out or cover them with the opaque pen. Blur doesn't protect anything: it can be reversed.
Bugs that only show in motion
Sincron doesn't record video or GIFs. The Windows 11 Snipping Tool records the screen with Win + Shift + R.
Long scrolling pages
Sincron only captures what is visible. For a full page, use your browser's full-page capture or ShareX.
No links or cloud
Sincron doesn't upload screenshots or create share links. The image goes to the clipboard or a PNG, and you decide where to paste it.
Common questions about bug report screenshots
What should a bug report screenshot include?
The full error message, enough of the screen to recognize where it appears, and one mark on the problem. Steps, expected result and version go in the ticket text.
Screenshot or video for a bug report?
A screenshot when the bug is a state: an error message, a wrong value, a broken layout. A video when it depends on a sequence or an animation. On Windows 11, the Snipping Tool records the screen with Win + Shift + R.
How do I paste a screenshot into Jira?
Copy the image and paste it with Ctrl + V onto the work item, or drag the PNG file in. Jira Cloud accepts dropped or pasted images on the work item and in comments.
How do I hide customer data in a ticket screenshot?
Crop to the error and cover anything else with a solid color box. In Sincron, use a black pen at maximum thickness in the drawing layer before you capture. Don't use blur.
Do I need to install anything to mark up a screenshot?
Not necessarily. The Snipping Tool ships with Windows 11, and Sincron's Annotate Screenshot Online tool runs in the browser. The Sincron app cuts the workflow down to two shortcuts and is free for capture and annotation.
See also
Annotate screenshots on Windows
Arrows, highlights and text on a screenshot, with background and shadow. Free and unlimited.
How to hide sensitive info in a screenshot
Why blur doesn't protect data, and how to crop or cover it in a Windows screenshot.
Technical docs and errors
Docs in Japanese, ERP consoles, stack traces, internal dashboards.
File your next ticket with the bug already marked.
Install Sincron Screen Tools: Ctrl + Shift + D to mark it, Ctrl + Shift + C to capture and paste. Capturing and annotating are free, unlimited and work offline.