Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cursor error

Cursor: <filename> is too large (4MB limit)

Error message
<filename> is too large (4MB limit)

Status: By designLast verified 4 documented fixes2 sources

What it means

A file attached to a Cloud Agent at cursor.com/agents exceeds the web attachment limit. Documents and images have a 4 MB per-file limit; videos have a separate 15 MB per-file limit. The browser rejects the file before upload.

Causes

  • The document or image is larger than 4 MB (or a video is larger than 15 MB).
  • Changing the model's context window or enabling Max Mode does not raise the attachment limit.
  • ZIP files are not supported as web document attachments.

How to fix it

  1. Fix 1.

    Keep only the content the agent needs, or split the file into parts of 4 MB or less.

  2. Fix 2.

    For logs and structured text such as JSON, CSV, XML, or HAR, keep the relevant time range and requests instead of the full capture.

  3. Fix 3.

    Start the Cloud Agent from Cursor desktop and attach the file there, since attachment limits can differ from the web app.

  4. Fix 4.

    For non-sensitive files already in source control, ask the agent to read them from its checked-out repository.

More Cursor errors

All 18 Cursor errors

FAQ

What does "<filename> is too large (4MB limit)" mean in Cursor?

A file attached to a Cloud Agent at cursor.com/agents exceeds the web attachment limit. Documents and images have a 4 MB per-file limit; videos have a separate 15 MB per-file limit. The browser rejects the file before upload.

How do I fix "<filename> is too large (4MB limit)"?

There are 4 documented fixes. Start with the first: Keep only the content the agent needs, or split the file into parts of 4 MB or less.

Is this Cursor error fixed?

Status: By design. Expected behavior, not a bug. The documented fixes change the setup that triggers it.

Sources

Last verified against 2 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.