"Image Dimension Limit Error" in Claude Sessions
How to fix the "image dimension exceeds max allowed size for many-image requests 2000 pixels" error that blocks your entire session.
The Problem
When a conversation accumulates multiple images (e.g. from screenshots, browser automation, or file reads), you may hit this error:
Warning: "An image in the conversation exceeds the dimension limit for many-image requests (2000px). Start a new session with fewer images."
Once this error appears, every subsequent message fails with the same error — even plain text messages. The session becomes stuck.
Why It Happens
Claude's API has two image-size limits:
| Scenario | Max Dimension |
|---|---|
| Few images in conversation | 8,000 px |
| Many images in conversation | 2,000 px |
As your conversation grows and accumulates more images, the API switches to the stricter many-image mode. An image that worked fine earlier (say 2,400 px wide) suddenly exceeds the limit — and because it's already in the conversation history, every new message re-sends it and triggers the same error.
How to Fix It
Start a new session. Once this error occurs, the current session cannot recover — the problematic image is stuck in the conversation history and gets re-sent with every message.
Click New Session to start fresh. Your previous session and its messages are still saved and accessible from the sidebar.
How to Prevent It
- Keep sessions focused — If your task involves many screenshots or images, start a new session before the conversation gets too long.
- Resize images before sharing — Keep screenshots under 2,000 px in both width and height when possible.
- Be mindful of browser automation — Each browser screenshot adds to the image count. Consider starting a new session between heavy screenshot tasks.
Tip: The 2,000 px limit only applies when there are many images in a single conversation. A few large images won't trigger it.
Technical Details
This is a known limitation of the Claude API's multi-image handling. The API returns a 400 invalid_request_error when any image exceeds 2,000 px in a many-image conversation. Because the offending image is embedded in the conversation history, it gets re-sent with every subsequent request — causing the error to persist.
There is currently no way to selectively remove a single image from conversation history. The only recovery is starting a new session.