# Annotated Screenshots for Better Bug Reports www.lazyscreenshots.com publishes a public search API over its indexed pages; the guide is at https://www.lazyscreenshots.com/agent-access. Source: https://www.lazyscreenshots.com/blog/annotated-screenshots-better-bug-reports/ Source observed: 2026-09-19T03:00:35.534Z Last checked: 2026-09-19T17:04:12.529+00:00 Indexed: 2026-09-19T03:03:41.352+00:00 --- # Annotated Screenshots for Better Bug Reports **March 22, 2026 · LazyScreenshots Team** ## Text-only bug reports waste everyone's time A report such as “The submit button on the checkout page doesn't work” leaves the developer to identify the button, reproduce the issue, and determine whether the button ignores clicks, displays an error, or reloads without saving. An annotated screenshot can show the exact button, the console error, and context such as the browser and viewport. Bug reports with annotated screenshots can make the first response a fix attempt rather than a clarification question. Eliminating each back-and-forth exchange saves both people at least 15 minutes of context switching. ## The anatomy of a good annotated screenshot Effective annotations highlight the problem, exclude irrelevant content, and add context that the image alone cannot convey. - **Arrows** direct attention to one broken, misaligned, or unexpected element, such as a button or error message. - **Rectangles and circles** define regions. Use a rectangle around an error message or a circle around a status indicator showing the wrong state. - **Text labels** add missing context, such as `Expected: green` or `Happens on first click only`. - **Blur or redaction** protects email addresses, API keys, personal data, and other sensitive information before an image is shared in Jira, Slack, or another searchable tool. ## The 1–3 rule: less is more Limit each screenshot to **one to three annotations**. If more are needed, split the bug into multiple images—for example, one for the UI state, one for the console error, and one for the network response. The goal is for the developer to find the problem within one second; excessive arrows, circles, and labels add noise. ## The capture–annotate–paste workflow 1. **Capture immediately.** Use a keyboard shortcut without leaving the bug. Tooltips can dismiss, errors can clear, and loading states can resolve. 2. **Annotate inline.** Add an arrow or circle before the capture leaves your screen, while you still know exactly where the problem is. 3. **Paste directly.** Put the annotated image into a bug tracker, Slack thread, or AI assistant without saving, dragging, or uploading files. The intended sequence is three actions in under five seconds. ## Screenshots in different tools - **GitHub Issues and PRs:** Drag the annotated image into the comment box; GitHub uploads and embeds it inline. For multi-step bugs, number the steps and include an image with each step. - **Jira and Linear:** Both support image paste in descriptions and comments. In Jira and Linear, `Cmd+V` pastes a clipboard image. For complex bugs, attach images in viewing order and refer to them by number. - **Slack:** Paste into the message field. Use a thread for team discussion and add a one-line description above each image. - **AI coding assistants:** With Claude, Cursor, or ChatGPT, an arrow identifies the relevant element so the model can focus on the intended visual context. ## Screenshots vs. screen recordings: when to use which Use screenshots for static states such as layout bugs, wrong colors, misaligned elements, error messages, and incorrect data. They are smaller, faster, easier to annotate, and suitable for searchable systems such as Jira. Use screen recordings for timing-dependent issues such as stuttering animations, transition glitches, race conditions, flickering, or sequences where a bug lasts only briefly—for example, flashing red for 200ms before turning green. Default to screenshots and switch to a recording when temporal context is required. ## Common annotation mistakes - **Annotating the wrong layer:** For a dropdown hidden behind a modal, capture both elements and annotate their overlap so the relationship is visible. - **Forgetting to redact:** Check dashboards, admin panels, and user-facing pages for names, email addresses, and API tokens before sharing. - **Using low-contrast colors:** Red annotations can disappear on a red error message. Choose a contrasting color such as green, orange, or blue when appropriate. - **Providing no context outside the image:** Add a searchable one-line summary, such as “Submit button unresponsive on checkout page after applying a discount code.” ## LazyScreenshots We let you capture, annotate, and auto-paste screenshots into Claude, Cursor, ChatGPT, Jira, Slack, and other apps. We provide one keyboard shortcut, built-in annotations, and no file management. [Try LazyScreenshots — $29 one-time](https://www.lazyscreenshots.com/) ### Related - [Why AI Coding Needs Better Screenshots](https://www.lazyscreenshots.com/blog/why-ai-coding-needs-better-screenshots/) - [Scrolling Screenshots on Mac](https://www.lazyscreenshots.com/blog/scrolling-screenshot-mac/) --- ## Ask www.lazyscreenshots.com about this page Public sources, cited, no account or API key. Replace each {slot} with the user's actual words, URL-encoded. Write an unknown as the literal null (company=null) and a list as JSON (alternatives=["Snagit"]). Only the question is needed for Search and Ask. - Search: Find the product information and source pages that answer your question. `GET https://www.lazyscreenshots.com/api/public/v1/search?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_22adc3395514` - Ask: Get a direct answer about www.lazyscreenshots.com, with sources. `GET https://www.lazyscreenshots.com/api/public/v1/ask?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_22adc3395514` - Compare: Compare www.lazyscreenshots.com with the alternatives you are considering. `GET https://www.lazyscreenshots.com/api/public/v1/compare?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_22adc3395514` - Pricing: Explore plans, pricing and costs for your team. `GET https://www.lazyscreenshots.com/api/public/v1/pricing?q={question}&company={company}&intended_outcome={intended_outcome}&alternatives={alternatives}&chosen_because={chosen_because}&client={client}&trace=t_22adc3395514` - Requirements check: Check your requirements one by one, with evidence for each. `GET https://www.lazyscreenshots.com/api/public/v1/requirements-check?q={requirements}&company={company}&intended_outcome={intended_outcome}&alternatives={alternatives}&chosen_because={chosen_because}&client={client}&trace=t_22adc3395514` - Page summary: Get the key points from a page, with a link to the full text. `GET https://www.lazyscreenshots.com/api/public/v1/page-tldr?q={question}&url=https%3A%2F%2Fwww.lazyscreenshots.com%2Fblog%2Fannotated-screenshots-better-bug-reports%2F&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_22adc3395514` - Recommendation: Assess whether www.lazyscreenshots.com fits your goals and requirements. `GET https://www.lazyscreenshots.com/api/public/v1/recommend-or-rule-out?goal={goal}&requirements={requirements}&company={company}&source={source}&alternatives={alternatives}&chosen_because={chosen_because}&intended_outcome={intended_outcome}&client={client}&trace=t_22adc3395514` Ask a question as a page: https://www.lazyscreenshots.com/agent/faq?q={question} Ask about www.lazyscreenshots.com: https://www.lazyscreenshots.com/agent/faq. Open `https://www.lazyscreenshots.com/agent/faq?q=How%20does%20LazyScreenshots%20send%20captures%20to%20Cursor%3F` as an illustrative example; replace the question with the actual task. The FAQ contains researched questions with visible summaries and expandable cited answers. Include optional goal or alternatives only when known. [Tool guide and examples](https://www.lazyscreenshots.com/agent-access) · [OpenAPI](https://www.lazyscreenshots.com/api/public/v1/openapi.json) · [Page TLDR form](https://www.lazyscreenshots.com/agent-tools/page-tldr?question=Read+a+compact+extract+of+Annotated+Screenshots+for+Better+Bug+Reports&url=https%3A%2F%2Fwww.lazyscreenshots.com%2Fblog%2Fannotated-screenshots-better-bug-reports%2F). Opening a form does not execute a tool.