How to Screenshot for a Bug Report and Share It

Capture the screenshot

Use the built-in tools so you get a real image file, not just a clipboard copy.

Windows: Press Windows+Shift+S to select the region with the error, then open the snip in Snipping Tool to crop and save it. Microsoft's Snipping Tool guide covers the flow.

Mac: Press Shift+Command+4, drag over the area, and release. The file saves to your desktop by default. Shift+Command+3 captures the whole screen. Apple's screenshot shortcuts page has the full list. Save a file rather than copying to the clipboard, since you need a file to upload.

Capture the relevant window plus enough surrounding context: the error message, the URL bar if it is a web app, and any state that explains the failure. PNG is the example format used here, but other common image formats upload the same way.

Redact before you share

1. Crop out anything unrelated first; less image means less to scrub.
2. Cover names, email addresses, tokens, and internal hostnames with opaque solid boxes, not blur or semi-transparent highlights.
3. Export or save the result as a flattened raster image such as PNG, with no editable layers. Redactions must be baked into the pixels, not sitting in a layer someone could toggle off.
4. Close and reopen the saved image. Verify the sensitive areas are actually covered in the final file rather than assuming an overlay removed the data.
5. Never include passwords, API keys, session cookies, or source secrets, even if you plan to redact them.

A screenshot with synthetic demo data is the safest option when you can reproduce the bug in a test account.

Upload and get the URL

1. Open the Yoink uploader.
2. Choose Select Files or drag the reviewed image onto the page, then start the upload with the main upload button.
3. Wait for the upload to complete and copy the resulting link, which starts with https://files.yoink.zip/.

Guest uploads work, so no sign-in is required. The link is public: anyone with the URL can view or forward it, and signing in does not change that. For a private issue, your tracker may accept a direct attachment, which is a better fit than a public link.

Write the report around the image

A screenshot shows the symptom; the text makes it reproducible. This example uses synthetic data and placeholders:

Expected: The invoice total updates when the quantity changes.
Actual: The total stays at the old value until the page is refreshed.
Steps:
1. Open the demo invoice in a test account.
2. Change the quantity from 2 to 3.
3. Observe that the total does not change.
Environment: YOUR_BROWSER_VERSION on your OS, demo account
Screenshot: YOUR_FILE_URL

Keep the expected and actual behavior to one sentence each, list numbered steps a developer can follow, and include the browser or app version. Paste the Yoink URL on its own line so it is easy to click.

Things to check

• Open the copied URL in a private window to confirm it loads for someone without your session.
• If the recipient says the link does not display inline in their tracker, try opening the URL directly. Depending on the browser and the image format, it may display in a tab or download as a file.
• Do not treat the link as permanent archival storage. Keep the original image in the issue or repo if the report matters long-term; see limits and retention.