A useful screenshot shows the symptom and enough context to interpret it. That might be a full error message, a disabled button beside its input or a layout problem at a particular window size. A picture of the whole desktop can expose unrelated information while making the important text too small.
Before capturing, identify the question: “Which message appears after this action?” is specific. “Can someone inspect everything on my screen?” is usually not. A focused image and one sentence explaining the preceding action help the recipient start in the right place.
On Windows, the built-in Snipping Tool can capture a selected region. On a Mac, the screenshot controls or keyboard shortcuts offer selected-area captures. Other devices provide their own screenshot tools. Use the operating system’s documented method rather than installing an unknown capture app.
Include the error’s title and relevant control labels. If the problem is an entire page layout, show a larger part of the page. If the URL contains sensitive information, remove or redact that part and provide a safe public address separately.
A cropped screenshot is an excerpt. Do not crop away information that changes the meaning, such as an earlier warning explaining why an action is unavailable. Where a popup hides the underlying problem, consider two images: the exact error and the relevant page state.
For layout issues, note the browser zoom and approximate window size. A display’s physical resolution is not necessarily the browser’s usable content area. Operating-system scaling, browser zoom, sidebars and window borders all influence how much fits.
The example WAIU screenshot shows several display readings together. They are not interchangeable measurements. If a support agent cannot reproduce a narrow-layout problem on a full-width desktop window, provide the condition that triggers it rather than only the monitor’s advertised resolution. Our screen-size guide explains the distinctions.
Look for account names, email addresses, notifications, other tabs, bookmarks, customer records, private hostnames, QR codes, recovery codes and URL tokens. A QR code can contain a password or private destination even when the surrounding page looks harmless.
Where removal is needed, use an opaque cover or a suitable redaction method, export a flattened copy and reopen that exported file to verify the information is gone. A translucent mark or weak blur can leave text readable. Editing layers or merely drawing over text in a document may not remove the underlying content.
Keep an original privately if required for your work, but share only the reviewed copy through the intended support channel. Avoid uploading a full desktop image publicly just to demonstrate one error. A private support ticket is still a reason to minimise unnecessary information.
| Include | Example |
|---|---|
| The action | “I selected the microphone, then pressed Start microphone.” |
| The actual outcome | “The permission message shown here appeared.” |
| The expected outcome | “I expected a permission prompt and a moving level meter.” |
| The environment | Browser/OS, time, window size or connection type when relevant. |
These are report examples, not evidence of a particular browser fault. Text matters because an image cannot tell support what happened before capture. Copy the exact error as text as well when possible, so the recipient can search or quote it accurately.
Send the image file at a readable resolution rather than repeatedly pasting it through services that shrink it. Zooming a tiny compressed image afterwards does not restore missing detail. If the image is very tall, two focused screenshots may be easier to interpret than a full-page capture reduced to a thumbnail.
For animated or intermittent behaviour, a short screen recording may help, but it can reveal audio, notifications and additional pages. Agree what support actually needs before recording. Do not record someone else’s private conversation as a routine diagnostic step.
Use the reproduction template and reviewed support details. Together they tell support what happened, under which conditions and how to attempt it. The aim is a clear piece of evidence, not a perfect-looking screenshot stripped of useful context.