[BUG] Image paste from clipboard not supported on Windows
Status Open
Reported on v2.1.168
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 5 comments · opened Jun 7, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
On Windows, pasting an image from the clipboard (e.g. a screenshot) into the Claude Code chat does nothing — the image is silently dropped. The same action
works correctly on macOS (desktop app).
Workaround: Save the image to disk and provide the file path manually — functional but disruptive.
Environment:
- OS: Windows 10
- Claude Code: desktop app / CLI
What Should Happen?
Expected: Image appears in the message and is sent to Claude for analysis.
Actual: Nothing happens. No image, no error.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce:
- Copy any image to clipboard (e.g. via Win+Shift+S or Print Screen)
- Open Claude Code on Windows
- Paste with Ctrl+V in the chat input
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.168
Platform
Other
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
5 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
It's ridiculous that such a basic function is still a problem, I won't close it as duplicate because you guys don't even read the issues apparently based on the backlog.
It feels like you're silly, it's clearly Alt+V, yet you insist on using Ctrl+V
It's not "clearly" when using Windows basic commands, thanks for the heads-up, but a more respectable response would've been enough. Have a good day.
I was able to root-cause this on my machine (Windows 11, Claude Code 2.1.204, PowerShell 7.6.3 as primary shell alongside Windows PowerShell 5.1).
Diagnosis:
[System.Windows.Forms.Clipboard]::GetDataObject().GetFormats()→Bitmap, System.Drawing.Bitmap, PNG, ...,ContainsImage() = True, correct image dimensions. So the OS-level clipboard is never the problem.Get-Clipboard -Format Imagesucceeds in Windows PowerShell 5.1 (powershell.exe, moduleMicrosoft.PowerShell.Managementv3.1.0.0).pwsh.exe, moduleMicrosoft.PowerShell.Managementv7.0.0.0) with:A parameter cannot be found that matches parameter name 'Format'.PowerShell 7's cross-platform
Get-Clipboardcmdlet only exposes-Raw/-Delimiter(text only) — it has no image-retrieval capability at all, unlike the Windows-only 5.1 version.I can reliably reproduce: image paste works when Windows PowerShell 5.1 is the effective/primary shell, and fails silently when PowerShell 7 (pwsh) is primary — which matches the "Terminal/Shell: PowerShell" reports in this thread, since that's ambiguous between the two editions.
Hypothesis: Claude Code's Windows clipboard-image retrieval shells out to
Get-Clipboard -Format Image(or similar) via whatever PowerShell it treats as primary. On pwsh 7 that call errors, and the failure is swallowed instead of surfaced or falling back.Suggested fix: Use the .NET clipboard API directly (
System.Windows.Forms.Clipboard/System.Windows.Clipboard) instead of theGet-Clipboardcmdlet — I verified this approach works correctly under pwsh 7 as well, so it should be version-independent. At minimum, surface an error instead of failing silently so it's less confusing.(Note: one reporter above said this "never worked," but in my case it worked fine on a previous machine that defaulted to Windows PowerShell 5.1 — so this does look like an edition-dependent regression rather than something that never worked at all.)
Happy to provide more diagnostic output if useful.