0.1.4 How to Capture a Useful Screenshot

A Screenshot Is Technical Evidence

A screenshot can do much more than prove that you completed a step.

A good screenshot helps another person understand what you saw.

That makes screenshots useful when:

• showing a result,
• documenting an error,
• asking for technical help,
• or providing evidence that a system reached a particular state.

The important skill is not simply knowing which keys capture the screen. The important skill is deciding what the screenshot needs to communicate.

Start With the Question

Before capturing anything, ask:

What am I trying to show?

If you are documenting an error, the error message matters.

If you are showing a successful result, the completed result matters.

If you need help with a particular application, the viewer may also need enough context to identify the application and understand where the problem occurred.

A screenshot should have a purpose before it has a crop.

Include Enough Context — But Not Everything

Two opposite problems can make a screenshot difficult to use.

Too little context

Imagine a screenshot containing only:

Error

The viewer knows that something went wrong, but not:

• which application produced the message,
• what the complete message said,
• or what you were doing.

Too much context

Now imagine a screenshot of an entire desktop where the important error is a tiny box in one corner.

The evidence may technically be present, but the viewer has to hunt for it.

A useful screenshot usually shows the smallest area that still tells the complete story.

Protect Information That Does Not Belong in the Screenshot

Before capturing or sharing an image, look for information another person does not need.

Examples include:

• passwords,
• authentication codes,
• private messages,
• personal email,
• student records,
• unrelated browser tabs,
• or other personal information.

Whenever possible, avoid capturing sensitive information in the first place.

Do not assume that something is safe to share simply because it appeared on your screen while you were working.

Check Readability

After capturing the screenshot, open it and look at it as if you were the person receiving it.

Ask:

• Can I read the important text?
• Is the complete error or result visible?
• Can I tell which application or window this came from?
• Is there a large amount of unrelated information?
• Is anything private visible?

If the image fails one of those checks, capture it again.

Sometimes the Screenshot Needs One Sentence

A screenshot shows a state. It may not explain what happened before that state appeared.

A short explanation can provide the missing context.

For example:

I selected Sign In, and this message appeared before the workspace opened.

That sentence tells the reader what action led to the screenshot without making an unsupported guess about the cause.

Compare that with:

Slack is broken.

The second statement guesses at the cause and provides almost no useful information.

Technical communication is stronger when you describe what you did and what you observed.

The Four-Question Screenshot Test

Before sharing technical evidence, ask:

1. Is the important result visible?
2. Is there enough context to understand it?
3. Is it readable?
4. Is private or unrelated information excluded?

If the answer to all four is yes, the screenshot is probably useful.