[FEATURE] Paste images from clipboard directly into Claude Code (Windows)

[juliojesus]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

When working with Claude Code on Windows, I often encounter visual issues — error messages, UI bugs, terminal output, or diagrams — that are easier to show than describe. My natural workflow is to capture a screenshot with Win+Shift+S, which puts the image directly in the clipboard.

The problem is that I cannot paste that image into Claude Code. I have to stop, open an image editor or file explorer, save the screenshot to disk, find
the file path, and then reference it manually. This completely breaks the flow of the conversation and adds unnecessary friction to what should be a
two-second action.

The core problem is: visual context is trapped in the clipboard with no way to share it inline, forcing a multi-step workaround that interrupts the
debugging or development workflow.

Proposed Solution

Allow Ctrl+V in the Claude Code prompt to detect when the clipboard contains an image and attach it to the current message, the same way text is pasted today. The image would be sent alongside the prompt so Claude can analyze it visually no file path required.

Alternative Solutions

• Saving the screenshot to disk and manually typing or dragging the file path into the prompt. This works but breaks the workflow and requires leaving the terminal.

• Using a third-party clipboard-to-file tool to auto-save screenshots. This adds an external dependency and still requires referencing a path.

  Neither alternative feels native or frictionless compared to a simple Ctrl+V.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

1. I am debugging a layout issue in my web app. I open the browser, see the broken UI, and press Win+Shift+S to capture the relevant area.
2. I switch to my terminal where Claude Code is running.
3. I type: "Why does this component look broken?" and press Ctrl+V to attach the screenshot.
4. Claude sees the image and immediately identifies the CSS issue.

Current experience: Step 3 fails silently nothing is pasted. I have to open Paint, save the image, find the path, and type something like
@/Users/julio/Desktop/screenshot.png before Claude can help.

Expected experience: Ctrl+V attaches the image inline and I send the message in one step, without leaving the terminal or touching the file system

Additional Context

his is consistent with how Claude.ai handles image input in the browser paste from clipboard works there out of the box.
Windows 11 clipboard (Win+Shift+S, PrintScreen, Snipping Tool) stores images in memory without saving to disk by default, making file-path-based workarounds inconvenient.
This feature would also benefit macOS users (Cmd+Ctrl+Shift+4) and Linux users with similar clipboard capture tools.
Common use cases: pasting error screenshots, UI layout bugs, terminal output rendered as image, hand-drawn diagrams, or design mockups.

[github-actions]

Found 3 possible duplicate issues:

1. Screenshot Support via Clipboard Paste in Claude Code CLI #12644
2. [Feature Request] Image drag & drop / paste support in CLI (like VSCode extension) #26001
3. Support pasting files/folders from clipboard as paths, and screenshots from macOS clipboard #25255

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[kallmetony]

that worked a few weeks ago but was broken by some recent changes

[IanVand]

+1 on this feature request. I work at Micron and use Claude Code extensively for engineering workflows on Windows 11. The Anthropic team specifically encouraged me to request this feature.

My workflow relies heavily on the Windows Snipping Tool (Win+Shift+S) to capture screenshots of test results, error messages, and system configurations. Currently there's no way to paste these directly into Claude Code -- I have to save the screenshot to disk first and then reference the file path, which completely breaks the conversational flow.

This would be a huge quality-of-life improvement for Windows users. The clipboard already has the image data; Claude Code just needs to read it.

[holydrug]

+1 on this feature request.

[lvanoverberghe]

Actually, I just got it working.
The shortcut is ALT-V, not CTRL-V.

[artem-ncf]

Actually, I just got it working. The shortcut is ALT-V, not CTRL-V.

Yes, on mac os command + v doesnt work but crl + v does work.

[roscoekerby]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet[x] This is a single feature request (not multiple features)

Problem Statement

When working with Claude Code on Windows, I often encounter visual issues — error messages, UI bugs, terminal output, or diagrams — that are easier to show than describe. My natural workflow is to capture a screenshot with Win+Shift+S, which puts the image directly in the clipboard.

The problem is that I cannot paste that image into Claude Code. I have to stop, open an image editor or file explorer, save the screenshot to disk, find the file path, and then reference it manually. This completely breaks the flow of the conversation and adds unnecessary friction to what should be a two-second action.

The core problem is: visual context is trapped in the clipboard with no way to share it inline, forcing a multi-step workaround that interrupts the debugging or development workflow.

Proposed Solution

Allow Ctrl+V in the Claude Code prompt to detect when the clipboard contains an image and attach it to the current message, the same way text is pasted today. The image would be sent alongside the prompt so Claude can analyze it visually no file path required.

Alternative Solutions

• Saving the screenshot to disk and manually typing or dragging the file path into the prompt. This works but breaks the workflow and requires leaving the terminal.
• Using a third-party clipboard-to-file tool to auto-save screenshots. This adds an external dependency and still requires referencing a path.
  Neither alternative feels native or frictionless compared to a simple Ctrl+V.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

1. I am debugging a layout issue in my web app. I open the browser, see the broken UI, and press Win+Shift+S to capture the relevant area.
2. I switch to my terminal where Claude Code is running.
3. I type: "Why does this component look broken?" and press Ctrl+V to attach the screenshot.
4. Claude sees the image and immediately identifies the CSS issue.

Current experience: Step 3 fails silently nothing is pasted. I have to open Paint, save the image, find the path, and type something like @/Users/julio/Desktop/screenshot.png before Claude can help.

Expected experience: Ctrl+V attaches the image inline and I send the message in one step, without leaving the terminal or touching the file system

Additional Context

his is consistent with how Claude.ai handles image input in the browser paste from clipboard works there out of the box. Windows 11 clipboard (Win+Shift+S, PrintScreen, Snipping Tool) stores images in memory without saving to disk by default, making file-path-based workarounds inconvenient. This feature would also benefit macOS users (Cmd+Ctrl+Shift+4) and Linux users with similar clipboard capture tools. Common use cases: pasting error screenshots, UI layout bugs, terminal output rendered as image, hand-drawn diagrams, or design mockups.

You can just use alt + v instead of ctrl + v on Windows

[roscoekerby]

Actually, I just got it working. The shortcut is ALT-V, not CTRL-V.

Yes, on mac os command + v doesnt work but crl + v does work.

alt + v works