TL;DR: Yes. Claude Code accepts JPEG, PNG, GIF, and WebP up to 5 MB, and it genuinely reads them: screenshots of broken UI, error dialogs, design mockups, whiteboard photos, architecture diagrams. What it can’t do is take a screenshot itself or watch your screen live. You provide the image, by paste, drag-and-drop, or a file path.
The short answer
Claude Code can see images. When one lands in your prompt you’ll see a placeholder like [Image #1], and the model reads the actual pixels, not just a filename. It will pick out the text in an error dialog, notice that a button is misaligned, read a hand-drawn schema off a whiteboard photo.
If you’ve only ever used it for text, this is worth building into your workflow. A screenshot is often the fastest possible bug report.
What developers actually use it for
Broken UI, fixed from a screenshot. Snip the misaligned sidebar, attach it, say “the sidebar overlaps the header, fix the flexbox.” Claude sees exactly what you see instead of parsing a paragraph describing it.
Error dialogs that won’t let you copy text. Some Windows dialogs, installer errors, and BSOD-adjacent screens have no selectable text. Screenshot them and let Claude read the message straight off the image.
Mockup to code. A Figma export, a competitor’s page, a napkin sketch. Attach it and ask for the component. It won’t be pixel-perfect on the first pass, but it’s a real scaffold, not boilerplate.
Whiteboard photos. Photograph the architecture diagram from a design session and ask Claude to turn it into a plan, a schema, or a set of stub files.
“What’s different between these two?” Attach a before and after screenshot and ask what changed. Good for visual regressions.
Precision beats prose. A red arrow drawn on the screenshot with “this gap should be 8px” outperforms any sentence describing where the gap is. Annotate before you attach when the detail matters.
What it can’t do
It can’t take screenshots. There’s no command that makes Claude Code capture your screen. If you searched for a “Claude screenshot tool,” what you actually need is a fast way to get your screenshot into the prompt, which is the next section.
It can’t watch your screen. No live view, no video. Every image is a one-time attachment you provide.
5 MB per image, and big images get downscaled. A full 4K desktop capture wastes most of its pixels on your wallpaper and gets scaled down before the model sees it. Crop to the part that matters: smaller image, sharper detail, better answer. If you’re hitting the limit, here’s how to shrink images for Claude Code.
How to get an image in
Three ways, in order of reliability:
- A file path in the prompt.
Look at ./screenshots/bug.png and fix the layout. Works in every terminal, over SSH, inside tmux. This is the method everything else is a shortcut for. - Drag and drop the file onto the terminal window.
- Paste with Ctrl+V (Ctrl+V on Mac too, not Cmd+V). This is the flaky one: Windows Terminal eats the keystroke, WSL needs Alt+V on recent versions, and it never survives SSH.
The full terminal-by-terminal support table is in how to attach images in Claude Code, and if paste is failing with an error, no image found in clipboard has its own set of fixes.
Invoke turns the clipboard image into a PNG on disk and pastes the file path into your terminal — one hotkey, works in Hyper, Wezterm, Windows Terminal, and WSL2. It's also the fastest way to dictate prompts to Claude Code. Free for 7 days, then $49 once.
Quick answers
Does Claude Code accept images? Yes. JPEG, PNG, GIF, WebP, up to 5 MB each, attached by paste, drag, or file path.
Can Claude Code read screenshots? Yes, and screenshots are the highest-value input: UI bugs, error dialogs, terminal output that won’t copy cleanly.
Can Claude Code take a screenshot of my screen? No. It reads images you give it. Snip with Win+Shift+S (or Cmd+Shift+4 on a Mac) and attach the result.
Can it see images over SSH? Yes, but only from a path on the machine where it’s running. Your local clipboard doesn’t cross the wire. Here’s the SSH workflow.
Is there an /image command? No. Paste, drag, or path.
The fast version
The file path method always works, so the real problem is speed: save the snip, find it, type the path, twenty times a day. Invoke collapses that to one hotkey. Snip with Win+Shift+S, press the image key, and the saved PNG’s path lands in your terminal ready to send. Add voice on top: hold a key, describe the bug, release, and the whole prompt is in Claude Code. $49 once. Free 7-day trial.