AI Guides › Claude Mastery
By Nigel Guy · 2 min read
The default instinct when something's wrong on screen — a confusing interface, a formatting bug, a chart that doesn't look right, an error message — is to describe it in words. "The button's in the wrong place" or "the second column doesn't line up" takes several sentences to say and still leaves out details you didn't think to mention, because you're translating something visual into something verbal before Claude ever sees it.
The rule: when the problem is what something looks like, a screenshot carries the information a paragraph is trying to approximate — send the picture, not the description of the picture.
| Situation | Screenshot beats description because... |
|---|---|
| Layout, spacing, alignment issues | "Wrong" is relative to everything around it — you'd have to describe the whole layout for the sentence to mean anything |
| An error message or stack trace | Exact wording and formatting matter; retyping it by hand introduces small errors that change the answer |
| A chart or graph that looks off | Colour, scale, and shape are hard to describe accurately and easy to just show |
| Someone else's design you're reacting to | You can point at what you mean instead of naming it, which matters most when you don't have the vocabulary to name it precisely |
| A form or document you're filling in | Structure and exact labels transfer directly, instead of you re-typing them and possibly getting them wrong |
The reverse also holds: when the problem is about meaning, tone, or logic — not appearance — a screenshot of text is worse than just pasting the text. You lose searchability and Claude has to read an image of words instead of the words themselves.
Skip screenshotting something you could just paste as text — a paragraph, a code snippet, a spreadsheet's numbers. Text-as-text is always easier to work with than text-as-image. And skip sending a screenshot with no framing at all; even one sentence of "here's what I'm expecting instead" turns a picture into a usable request rather than a puzzle.