How to Capture and Share Bugs with Screenshots
Capture the bug, show enough context to locate it, and share clear reproduction steps. Includes platform capture options, privacy checks, and a ScreenshotNeo shortcut.
A useful bug screenshot shows the problem and enough surrounding interface for someone else to find it. Pair it with concise steps to reproduce the issue, what you expected, and what happened. Use a screen recording when the failure depends on a sequence of actions; use a still image when one visible state explains it.
This guide covers built-in capture options for Android, Apple devices, and Windows, how to prepare evidence, and how to share it responsibly. For a web page you need to capture programmatically, ScreenshotNeo can return a screenshot or PDF from one API request.
1. Decide what evidence the bug needs
Choose the smallest capture that still makes the problem understandable. A screenshot is quick to scan and works well for a single visible state. A recording can explain a bug that appears only after a click, navigation, animation, or other sequence.
| Evidence | Use it when | Watch for |
|---|---|---|
| Still screenshot | The error or incorrect state is visible at once. | Include enough nearby interface to locate the affected control. |
| Screen recording | The steps or timing are essential to reproduce the issue. | Keep it focused and avoid recording unrelated personal or confidential content. |
For a still, decide whether the full screen, an application window, or a selected region gives the right balance. A full screen preserves context but may include distractions or private details. A region focuses attention but can remove the context needed to locate the issue. A window is often a useful middle ground when the application boundary matters.
2. Capture the issue on your platform
Android
- Open the affected screen and reproduce the bug.
- Press Power and Volume Down together. If that shortcut does not work, check the power menu for a Screenshot option or consult the device manufacturer’s instructions.
- Open the capture in Photos or the device gallery, then edit or share it.
On Android 12 and later, scrolling screenshots are available on most screens that allow scrolling. To record a sequence, use Screen Recorder from Quick Settings. Android’s recording flow can offer audio and touch indicators. Menus and behavior vary by device maker and Android version.
Apple devices and Xcode
On Mac, Apple’s screenshot guide covers capturing the full screen, a window, or a selected portion; choosing where to save; and using the floating thumbnail to mark up or share the result. The guide also includes iPhone and iPad capture instructions. Follow the instructions for the device and OS version in use.
For an Apple development workflow, Xcode Device Hub can capture screenshots from simulated or physical devices at the device’s full resolution and save them to the Mac Desktop. It can also record interactions on a simulated device and save the video to the Desktop. See Apple’s Xcode screenshot and video guidance.
If an app captures screen content through ScreenCaptureKit, Apple’s documentation says to request screen-recording permission and recommends the system content-sharing picker so people can select the content source. See ScreenCaptureKit documentation.
Windows
Snipping Tool supports rectangle, freeform, and window image captures, plus a video mode for recordings. The exact controls can vary across Windows versions. Microsoft’s cited documentation describes launching the tool; check the current Snipping Tool interface on your version for the capture steps. See Microsoft’s Snipping Tool launch documentation.
ShareX is an optional project for area capture, recording, annotation, and upload workflows. It is not required for a basic screenshot. Before uploading sensitive evidence through any optional tool, check its current download source, privacy settings, and sharing behavior.
3. Make the screenshot easy to understand
- Reproduce the issue first. Capture the state that demonstrates the bug rather than an unrelated screen.
- Keep useful context. Show enough surrounding interface that a recipient can locate the affected feature, while avoiding excess empty area.
- Annotate sparingly. Use an arrow, highlight, or brief note only when it clarifies the issue. Keep annotations off the error message and affected control.
- Write reproduction steps separately. Include the starting state, actions, expected result, and actual result. The report should make sense without relying on text embedded in the image.
- Check readability. Preserve enough contrast for important controls and messages to remain legible.
- Add alt text where appropriate. If the screenshot appears in documentation or an issue for readers who use assistive technology, provide concise alt text that conveys its relevant content.
GitHub’s screenshot guidance recommends sufficient surrounding context, complete written instructions, adequate contrast, and alt text. See GitHub’s guidance on attaching files.
4. Write a bug report that stands on its own
Use a short report alongside the image or recording. For example:
Summary: Checkout total changes after applying a discount
Environment: Browser and version, operating system, app version, and relevant device details
Steps to reproduce:
1. Open the cart with two items.
2. Apply the SPRING discount code.
3. Change the quantity of the first item to 2.
Expected: The discount remains applied and the total updates.
Actual: The discount disappears from the summary.
Evidence: Attached screenshot showing the cart summary after step 3.Include only environment details that could help someone reproduce the failure. If the issue occurs intermittently, say how often you observed it and whether repeating the steps changes the result. Do not put essential instructions only in an annotation.
5. Review privacy and share the evidence
- Inspect the image or recording before sending it. Look for unrelated account details, personal information, confidential content, or secrets.
- Crop or obscure unrelated sensitive details where appropriate. Keep the evidence needed to understand the bug visible.
- Attach the file to the team’s issue tracker or use its approved feedback workflow.
- If you use a share link, check its audience and access settings before sending it.
A screenshot is a copy of whatever was visible at capture time. Review it before sharing, even when the capture came from a built-in operating-system tool.
6. Troubleshooting capture and sharing
| Problem | Likely cause | What to do |
|---|---|---|
| The screenshot shortcut does nothing. | The device uses a different shortcut, the keys were not pressed together, or the manufacturer changed the behavior. | Try the power menu’s Screenshot option on Android, or consult the device maker’s instructions. On desktop, use the built-in capture app. |
| The image does not show the failure. | The issue was not reproduced before capture, or the failure depends on earlier actions. | Repeat the steps and capture the failing state. If the sequence matters, record it or write each action precisely. |
| The recipient cannot tell where the problem is. | The image is too tightly cropped or lacks interface context. | Capture a little more of the surrounding interface and identify the relevant control in the written report. |
| The annotation hides the relevant detail. | A mark or note covers the error or control. | Move the annotation, use a smaller mark, or provide the explanation in the report text. |
| The recording is hard to follow. | It includes unrelated navigation or too much idle time. | Start near the first relevant action and keep the recording focused on the reproduction sequence. |
| A capture app cannot record the screen. | Screen-recording permission may be missing, or the selected source may be unavailable. | Grant the required permission and use the system content picker when the platform offers one. |
| A shared link does not open for a teammate. | The audience or access settings may exclude that person. | Check the link’s access settings or attach the file through the team’s approved workflow. |
| The image contains information it should not. | Other account or private details were visible during capture. | Crop or obscure the unrelated information, then inspect the edited result before sharing. |
7. Keep capture reliable and lightweight
Capture only what the report needs. A focused still is typically easier to review than a long recording; choose video when interaction or timing is part of the failure. Keep the original evidence available if the team may need to inspect details after sharing an annotated copy.
Check that the resulting file is legible and attached successfully. For a public or externally accessible link, verify who can open it. Avoid adding a third-party upload step when the team’s approved issue tracker already accepts attachments.
Or skip the browser setup
If the bug is in a web page and you need a programmatic capture, ScreenshotNeo returns an image or PDF from a GET request. The example below saves a screenshot of Stripe as WebP. Replace the URL with the page you are investigating and use your API key.
See the ScreenshotNeo API documentation for request options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://stripe.com',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free 1,000 screenshots a month, with no card required.
Frequently asked questions
How do I take a screenshot of a bug?
Reproduce the issue, capture the visible failing state with enough surrounding interface to locate it, then attach concise reproduction steps and the expected and actual results.
How do I share a screenshot with a bug report?
Attach it through your team’s issue tracker or approved feedback workflow. If you send a share link, check its audience and access settings first.
Should I send a screenshot or a screen recording?
Use a screenshot when one state makes the issue clear. Use a recording when the sequence or timing is necessary to reproduce it.
Should I include the whole screen?
Include enough context to make the affected feature easy to find. Crop distractions and unrelated sensitive details while retaining the context the recipient needs.
