Omniscio

OmniscioGuidesRequest too large

Claude Code: request too large (max 32MB)

Last checked against Anthropic's documentation on November 14, 2026. By the Omniscio team. Updated .

What does the message look like?

The general form tells you what filled it and what to run:

Request too large (max 32MB). Accumulated images and attachments in the conversation pushed the request over the limit. Run /compact, or double press esc to go back and remove attachments.

When the request went straight to the Claude API, Claude Code measures the conversation and tells you what took the space:

Request too large (max 32MB; 20.1MB of about 33.4MB is images or documents).

And when the messages alone are over the limit, you get this line, and it tells you compacting cannot make it fit:

Request too large for the API's 32MB request limit

The words to look for are compacting cannot make it fit. When you see them, /compact will not help.

Through a proxy, a gateway or a cloud provider you get the general message instead of the measured ones.

What does it actually mean?

The request body was over the API's 32MB limit before it was turned into tokens. Large pasted content, tool results and attachments are the usual cause.

This limit is separate from the context window. A conversation can hit it with plenty of window left, because 32MB of raw bytes can overflow before the token count does.

That is why the fix is often about attachments rather than about the conversation's length.

Which version of the message do I have?

Read what follows the opening bracket. That one word decides the fix.

  • It names images or documents. Claude Code retries without them, so you may not need to do anything.
  • It says compacting cannot make it fit. The messages alone are over the limit. Claude Code will not retry, and /compact cannot help.
  • It is the general message. Run /compact and remove attachments.

In non-interactive mode the message tells you to reduce the input or start a new session instead.

How do I fix it?

Commands such as /compact and /clear are typed into Claude Code's own chat box, with a slash in front, then Enter.

  1. If your message names images or documents, wait for the retry. Claude Code strips them and sends again, so the next reply may just work.
  2. Run /compact. This drops accumulated images and attachments from the conversation. It is the step the message itself names.
  3. If the message says compacting cannot make it fit, press Esc twice. That takes you back past the turn that added the large content. Then send a smaller version, or run /clear to start fresh.

If a single image was rejected rather than the whole request, see our page on oversized images.

How do I stop it coming back?

Give Claude a file's path instead of pasting its contents. It can then read a line range at a time and keep the request small.

Keep large images out of long sessions, and run /clear when a task is finished. Both keep the request from building up.

Common questions

What does Request too large (max 32MB) mean in Claude Code?

The request body was over the API's 32MB limit before it was turned into tokens. The usual cause is large pasted content, tool results, or attachments such as images. This limit is separate from the context window, so a conversation can hit it with plenty of window left.

Does /compact fix it?

Often yes. Running /compact drops accumulated images and attachments. But if the message says compacting cannot make it fit, then the messages alone are over the limit and /compact will not help. Press Esc twice to step back past the large turn, or run /clear.

Why did it only start happening now?

Images and documents build up. Each one stays in the conversation, so the request grows with every turn even though your last message was small. The message's measured form tells you how much of the total is images or documents.

How do I stop it coming back?

Give Claude a file's path instead of pasting its contents, so it can read a line range at a time. Keep large images out of long sessions, and clear the conversation when a task is finished.

Where these answers come from