Image-in-chat — paste the screenshot
Most people describe what they see when they could just paste the screenshot. The AI reads pixels better than you can describe them. Stop typing the picture.
::TL;DR · the whole lesson in three lines
- MOVEMost people describe what they see when they could just paste the screenshot. The AI reads pixels better than you can describe them. Stop typing the picture.
- DRILLPick a real thing on your screen or in front of you right now that you would normally describe to a human. We are going to skip the description entirely and let the AI read the source. Once you feel this work, you will never go back to typing the picture.
- WINThe AI quoted specific text, numbers, or details from your image — not generic guesses about what it might contain.
::concept · what's actually happening
The chat box accepts more than text. Drag an image in, paste from your clipboard, hit the attach button — Claude, ChatGPT, and Gemini all read images on the free tier. They see the actual pixels: the layout, the text, the error message, the chart axes, the dog's expression, the way the cabinet door is hanging crooked. When you describe a screenshot in words, you are doing a job the AI is better at than you are, and you are losing information at every step.
read full concept · 3 more paragraphs →collapse concept ↑
Here is what changes when you paste instead of describe. You type 'my code is throwing an error about undefined variable' — the AI guesses at five possible causes. You paste the screenshot of the actual terminal — the AI reads the exact filename, the line number, the stack trace, the surrounding context, and tells you the one thing that is wrong. You type 'this chart looks weird' — the AI asks clarifying questions. You paste the chart — the AI says the y-axis is on a log scale and that is why your numbers look compressed. The gap between describing and showing is enormous.
This works for things that are not screenshots too. A photo of a handwritten note. A picture of the back of a router. A snapshot of a recipe card in a cookbook. A picture of a plant you cannot identify. A photo of a rash before you call the doctor — the AI is not the doctor, but it can tell you whether what you are looking at warrants the urgent-care visit. A photo of the inside of your fridge before grocery shopping. A picture of the parking meter sign you cannot parse. The phone camera plus the chat box is one of the most useful tools you own and almost nobody uses it past 'look at this funny dog.'
One caveat that matters. Image quality affects what the AI can read. A blurry screenshot of fine-print text will fail. A glare-covered photo of a document will fail. If the AI says 'I cannot read this clearly,' that is honest — retake the photo with better light, get closer, or screenshot the source directly instead of photographing your screen. Phone-photo-of-monitor is the worst version of this; native screenshot is the best. The fix is almost always 'get a cleaner image,' not 'try a different AI.'
::drill · do the thing
Pick a real thing on your screen or in front of you right now that you would normally describe to a human. We are going to skip the description entirely and let the AI read the source. Once you feel this work, you will never go back to typing the picture.
::L13 drill · copy-paste into any AI chat
I'm attaching an image of [what the image shows — e.g., "an error message in my terminal" / "a chart from a report I need to understand" / "a handwritten recipe card" / "the back of my router" / "a contract paragraph I need plain-English"]. What I need from you: 1. Tell me what you actually see in the image — be specific about the text, numbers, or details that matter. 2. [The real ask — e.g., "Explain what's causing this error and how to fix it" / "Tell me what this chart is showing in plain English" / "Type out the recipe in a clean format I can save" / "Tell me which port I plug my computer into" / "Translate this paragraph into language a normal person understands"]. 3. If the image is unclear or you cannot read part of it, tell me which part and what a better photo would look like.
::steps
- 01Open Claude, ChatGPT, or Gemini in your browser or app.
- 02Pick one real thing — an error on your screen, a chart in a document, a piece of paper in front of you, the back of a device, a sign you don't understand. Don't overthink it; the first thing you thought of when reading this lesson is fine.
- 03Capture it cleanly. On a computer, use the native screenshot tool (Windows: Win+Shift+S; Mac: Cmd+Shift+4). On a phone, take the photo with good light and the subject filling the frame. Avoid photographing your own monitor.
- 04Drag the image into the chat box, or paste it from clipboard, or use the attach/paperclip button. Confirm the image preview appears before you send.
- 05Paste the drill prompt above. Fill in the two bracketed slots — what the image shows, and what you actually need.
- 06Send. Read the response. Notice how much specific detail the AI pulled from the image — text it read, numbers it parsed, layout it identified. That detail came from pixels, not from your description.
- 07Ask one follow-up that depends on the image. Example: 'Now rewrite that recipe for half the servings' or 'Now tell me which of those settings I should change first.' This proves the AI is still holding the image in the conversation.
::outcome · what should be true
- The AI quoted specific text, numbers, or details from your image — not generic guesses about what it might contain.
- You got a useful answer faster than you would have by typing out a description of the same thing.
- The follow-up question worked without you having to re-explain the image — the AI was still 'looking at' it.
- You noticed at least one detail in the AI's response that you would not have included if you had described the image in words.
::trap · the most common failure
Photographing your monitor with your phone instead of taking a native screenshot. The result is a blurry, glare-covered, off-angle image where the AI can only read half the text — and then people blame the AI for being bad at images. The AI is fine. The image is bad. Win+Shift+S on Windows, Cmd+Shift+4 on Mac, screenshot button on phone for phone screens. Native capture, every time.
::other lessons at User level
Multi-turn conversations — letting the chat build a model of the task
At User level, a single prompt is rarely the win. A 5–10 turn conversation that builds a working model of your task is.
Documents in chat — when paste vs. upload matters
AI is at its best when reading something specific. Knowing how to feed it documents is the next leverage step.
Your first paid tier — which one, when, why
Free tier is enough for most humans for 30+ days. When you outgrow it, you pay for ONE tool. Not four.
Voice mode — when speaking beats typing
Real-time conversation with AI is a different shape than chat. Knowing when to switch modes is the actual skill.
Projects and Custom GPTs — stop re-explaining yourself
Every chat starts cold. A Project remembers your background, your style, your files. Create one for the work you actually do every week, and stop pasting the same context twelve times a day.
Artifacts and Canvas — the side panel that runs your work
Claude Artifacts and ChatGPT Canvas turned chat into a workspace. Code runs. Documents render. Edits happen in place. This is where AI stops being chat and starts being a tool.
::part of the AtomEons /learn curriculum · 45 lessons · 5 levels · cc-by 4.0