“The button is broken” sends someone on a search. Which button, in which window, after which action? A useful piece of feedback answers those questions before the person receiving it has to ask. It also stops at the right moment: enough context to understand the issue, without a three-minute tour of your desktop.
This is where Droppy's Element Capture fits. Capture the specific interface, explain what matters, and use a recording when the order of events is the problem. The file tray keeps the evidence nearby while you finish the message. You still decide what to send and where to send it.
Start with the question the capture must answer
Decide whether you are reporting a defect, suggesting a visual change, or explaining a process. A defect needs a reproducible action and the result. A visual suggestion needs the detail you would change and why. A walkthrough needs the steps in the order someone should follow them. Those are different jobs, even when they happen in the same app.
Write a working sentence before you capture: “After I choose a different folder, Save stays disabled.” That sentence tells you what the evidence needs to contain. It also gives the final message a useful opening, instead of making the recipient interpret a file named Screenshot followed by a date.
Use the smallest screenshot that still has context
Switch on Element Capture in Settings, Store, then assign the capture shortcuts you want. Its modes cover individual interface elements, selected areas, windows and the screen. Choose an element when the control itself is the subject. Choose an area when its neighbours explain the problem. Choose a window when the overall state matters.
For a disappearing menu or tooltip, use Pause screen so the state remains available while you capture. A tight image is quicker to understand and often easier to share. Leave enough surrounding interface to identify the location, though. A beautifully cropped error with no app, field or action around it can be harder to investigate than a slightly wider capture.
Annotate the decision, not every pixel
Open the capture in the editor and make one thing unmistakable. An arrow can identify a control. A shape can frame the affected area. A short text label can state what should happen. Numbered step stickers are useful for an instruction sequence because the order stays visible in the image.
Use annotation text that adds information. “This field resets after Save” is more helpful than “Here.” If you are proposing a change, describe the outcome rather than guessing at its implementation: “Keep the chosen folder after saving” gives the developer room to solve the actual problem.
Element Capture also has blur tools for sensitive content and background, radius and shadow controls for presentation. Use the finishing tools when the image will live in documentation or a public post. For a quick internal report, clarity usually needs fewer decorations.
Record when the sequence is the evidence
A screenshot cannot show a menu closing too soon, a drag landing in the wrong place, or a setting reverting after a click. Element Capture's screen recording, available on macOS 26, handles those cases. Rehearse the sequence once, arrange the relevant window, then record only the actions needed to show the behaviour.
Droppy's recording tools include pointer-following zoom, click highlights and keystroke captions. Choose the aids that make the action understandable. A small control may benefit from zoom; a shortcut problem may need the keys. Showing every effect at once can distract from the thing you are trying to explain.
Open Studio after recording to trim the start and end, adjust the framing and style, and review the result before export. Start just before the meaningful action and finish once its outcome is visible. Leave enough time for someone watching without your narration to understand both.
Make a small handoff, not a pile of attachments
Send the annotated still when it explains the issue on its own. Send the clip when movement is essential. Sometimes a still plus a short clip is useful: the still marks the detail, while the clip proves how you reached it. Five near-identical screenshots usually create more uncertainty than evidence.
Element Capture can send screenshots to a folder, the clipboard, Droppy Cloud, or the file tray. The tray is a useful temporary stop while you write the accompanying message. Drag the chosen file from there into your destination. If you use a Cloud link, check that you are sharing the intended file before sending it.
Finish with the expected result and a clear request
A good handoff can be three sentences: what you did, what happened, and what should happen instead. Add the app version and any setup detail that changes the result, such as a second display. For a design review, replace the expected result with the reason the change would help the person using the screen.
Watch exported recordings and inspect screenshots before sharing. Blur is a visual editing tool, so check the final pixels rather than assuming a sensitive area is hidden. Keep source files private when they contain material the recipient does not need. Droppy makes gathering evidence easier; the final review is still an important part of the job.