claude-code - 💡(How to fix) Fix [BUG] Subject: UX issue — image dimension limit in Claude Code is breaking workflow [1 comments, 2 participants]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Hi Anthropic team,

Writing as a paying subscriber and a heavy Claude Code user to flag how badly the image dimension limit (2000px per side — error: "An image in the conversation exceeds the dimension limit for many-image requests") is hurting the product.

What's happening:

I run product development for three mobile apps and constantly share screenshots with Claude Code — UI states, bug repros, design mockups, build errors, analytics dashboards. Modern displays (4K, 5K, Retina) produce screenshots well above 2000px by default. I'm not doing anything unusual — I'm just taking a normal screenshot on a normal Mac.

The result: roughly once an hour I hit this error and the entire session becomes unusable. The "Try again" button does nothing, because the offending image is already in the conversation history. The only "fix" is to start a brand new session.

Why this is a serious problem, not a minor annoyance:

I lose all conversation context. Long technical work — debugging, refactors, planning — relies on Claude remembering what we discussed. Forcing a new session every hour throws that away. I can't even ask for a handoff summary. When the error fires, the session is frozen. I can't say "summarize what we did so I can paste it into the next chat." The work is just gone. The error is retroactive. The image was accepted earlier in the session without warning. Then, hours later, after dozens of new messages, the same image suddenly violates a limit and kills the entire conversation. There's no way to predict it or recover. No client-side guardrail. Claude Code doesn't downscale, doesn't warn me at paste time, doesn't offer to compress. It silently accepts the image and then breaks the session later. It's not consistent with the rest of the product. Claude.ai web and the API tolerate larger images. Claude Code — the tool aimed at the most demanding power users — has the strictest limit. That's backwards. What this is costing you:

I'm seriously considering canceling my subscription and going back to ChatGPT, purely because of this single issue. Not because Claude is worse at the actual work — it's better. But "better model, broken workflow" loses to "good-enough model, workflow that doesn't randomly die." I can't be the only one feeling this.

What I'd ask for, in order of usefulness:

Auto-downscale on the client before the image enters the conversation. If 2000px is the limit, resize to 2000px on paste/upload. This is a 1-day fix and it eliminates the entire problem class. Warn at insert time, not retroactively. If an image is too large, reject it immediately so I can resize and retry — don't let it poison the session for later. Raise the limit. 2000px is too low for 2026-era displays. 4096px would cover virtually every real screenshot. Allow sessions to recover by letting users delete an offending image from history instead of killing the entire conversation. I want to keep using Claude Code. Please fix this.

Thanks, Slava

What Should Happen?

Large screenshots should not break the session. Specifically:

1. Claude Code should auto-downscale images that exceed the 2000px limit on paste/upload, before they enter the conversation. The model only needs ~1568px on the long side anyway — anything larger is wasted bandwidth.

2. If auto-downscale is not implemented, the image should be rejected immediately at insert time with a clear warning ("This image is 3024×1964px, exceeds the 2000px limit, please resize"), so I can fix it before sending.

3. The error must NOT be retroactive. Right now an image is silently accepted, the conversation continues for hours, and then the same image suddenly poisons the session and there is no way to recover except starting from scratch — losing all context.

4. When the error does fire, I should be able to delete the offending image from history and continue, instead of being forced to abandon the entire session.

5. Ideally raise the limit itself — 2000px is below the native resolution of basically every modern display. A normal macOS screenshot on a 14" MacBook Pro is already 3024×1964. The current limit guarantees the error for any unmodified screenshot.

Error Messages/Logs

Steps to Reproduce

1. Open Claude Code on macOS with a Retina display.
2. Take a normal screenshot (Cmd+Shift+4) of any UI — it will be ~3000×2000px.
3. Paste it into Claude Code. It is accepted without warning.
4. Continue working for some time, sending more messages and possibly more screenshots.
5. At some point the session starts returning "exceeds the dimension limit (2000px)" on every request.
6. The session is now permanently broken. "Try again" does not work. Only fix is to start a new session and lose all context.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Desktop app v1.5354.0 (macOS)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response