[BUG] API Error: invalid_request_error When Sending A Image
Resolved 💬 29 comments Opened Nov 18, 2025 by klenq Closed Nov 19, 2025
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?
I received a invalid_request_error when sending a image to Claude Code
API Error: 400 {"type":"error","error":{"type":"invalid_request_error","mess
age":"messages.1.content.4.image.source.base64.data: Image does not match
the provided media type
image/jpeg"},"request_id":"req_011CVGBgAXiQ5NPtA4MN8gh6"}
<img width="564" height="308" alt="Image" src="https://github.com/user-attachments/assets/da4a8e19-63ea-4bcc-9ead-89eaa052141c" />
What Should Happen?
Fix Error
Error Messages/Logs
API Error: 400 {"type":"error","error":{"type":"invalid_request_error","mess
age":"messages.1.content.4.image.source.base64.data: Image does not match
the provided media type
image/jpeg"},"request_id":"req_011CVGBgAXiQ5NPtA4MN8gh6"}
Steps to Reproduce
- Put any image in the folder claude can read
- Ask claude code to read the image you provided "read the image in the current folder"
- API Error raise and same error message raise for all future prompt you enter
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.0.45
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
29 Comments
having the same issue
Thanks for reporting, this should now be fixed in 2.0.46.
Unfortunately I experience this issue on v2.0.46
Issue persists in 2.0.46 for me also.
Still there.
Tested with 2.0.46 - still there
Still an issue.
I'm experiencing the same issue while using the Figma MCP and attempting to capture a screenshot. Also using 2.0.46
Not fixed for me using chrome devtools mcp either, using 2.0.46
completely broken, can't use playwright mcp at all
Same here, not working with 2.0.46 @shawnm-anthropic
So... I used Claude to write a script to downgrade Claude 😂 (macOS, claude-generated):
downgrade.sh:
And this script to undo it
Using this, I can confirm this does not happen on 2.0.44, so something broke between that and 2.0.46
Hope this is useful for people in the future running into the same issue! At least until the Anthropic team fixes it...
It is same for me. I am using Figma MCP and getting same error. Also using 2.0.46 version. It was working last week.
My workaround was to downgrade Claude VS Code extension to 2.0.37, and i was able to use Figma MCP normally.
same here using 2.0.47
same error using 2.0.47
The error still persists in 2.0.47
same this error v2.0.47
You can manually downgrade if you simply run "claude install 2.0.44" in your terminal.
Same error on v2.0.47 also.
Same error on v2.0.32
Why is this issue closed, is downgrading CC really a solution to this?
No kidding. I downgraded and will disable updates until it is fixed.
downgraded to 2.0.47. same error.
Not a fix, but if you are in a rush:
just tell Claude not to call getScreenshot, example:
"""
{your prompt for claude look at figma node}
VERY IMPORTANT: do NOT call the getScreenshot tool while using the figma mcp (even though it says "IMPORTANT: call get_screenshot... bla bla) .. bc there is a known bug with getScreenshot.. instead just ask me for a screenshot if you want/need one at any time. thanks.
"""
Same here on claude --version
2.0.49 (Claude Code)
How can we get rid of this in an existing session? Keeps spitting this error
Yep still an issue in 2.0.50
How on earth is this closed?
Opus 4.5 now released with claims of being cheap and superior, the pain of freezing Claude Code version for this issue increases...
Is this still a thing? I'm stuck with 2.0.44 still because that was the only working version before all this crazyness ensued. I still don't know why the Claude team doesn't just do a diff of what they changed between 2.0.44 and 2.0.47 and just revert / fix it or whatever, heck, even with Claude, maybe it's a 10-min fix, I dunno.
2.0.54 same here
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.