When you contact support about a website, email, or hosting issue, a screenshot can help explain what you are seeing. A clear screenshot often makes it easier to identify the cause of a problem and reduces the need for follow-up questions.
Not every screenshot contains the information needed to investigate an issue. Including a few important details can help support teams understand the context and provide assistance more quickly.
Table of Contents
What a useful screenshot should include
Whenever possible, make sure your screenshot shows:
- The full error message, including any error codes.
- The complete browser window, not just the affected area.
- The website address (URL) visible in the address bar.
- The date and time displayed on your device.
- Any relevant buttons, settings, or actions that led to the problem.
If the issue occurs inside a control panel, webmail interface, or application, include the surrounding interface so that support can see where the problem occurred.
Avoid cropping important information
It can be tempting to capture only the error itself, but context is often just as important as the message.
For example, the same error may have different causes depending on:
- Which page you are viewing.
- Which account is currently logged in.
- Which browser or device you are using.
- Which action triggered the problem.
A wider screenshot is usually more useful than a tightly cropped one.
Include multiple screenshots when necessary
Some issues involve several steps. If the problem appears after completing a sequence of actions, consider sending multiple screenshots that show:
- The page before the problem occurs.
- The action you performed.
- The result or error message.
This can help support teams reproduce the issue and understand how it happened.
Protect sensitive information
Before sending a screenshot, check whether it contains confidential information.
You may want to hide or blur:
- Passwords.
- Payment information.
- Personal identification numbers.
- Private messages or documents.
- Access tokens or API keys.
Do not hide error messages, URLs, or technical details unless instructed to do so, as they may be necessary for troubleshooting.
If possible, include the browser console or developer tools
For some website issues, support may ask for additional technical information from your browser’s developer tools. This can include console errors or network requests.
If support requests these details, include a screenshot that clearly shows the relevant messages along with the affected page.
What to expect
A screenshot does not always provide enough information to diagnose an issue on its own. Support may still ask for additional details, such as the time when the problem occurred, the browser you are using, or the steps required to reproduce it.
Clear screenshots help provide context and often make it easier to investigate technical problems efficiently.