TL;DR: Claude Code caps images at 5 MB, and a full-screen 4K PNG can be double that. The fastest fix is to snip only the region you care about instead of the whole screen. If you need the whole thing, save it as JPG instead of PNG, or resize it below 2000 pixels wide. Smaller, focused images also get you better answers.

Why you’re hitting the limit

Claude Code accepts images up to 5 MB each. That sounds like plenty until you screenshot a 4K monitor. A full-resolution PNG of a busy screen can run 6 to 12 MB, because PNG stores every pixel losslessly and a detailed desktop has a lot of pixels.

So the error isn’t really about your image being “big” in any visual sense. It’s about raw file size, and PNG plus high resolution is the combination that pushes you over.

Fix 1: Snip the region, not the screen

This is the best fix, and it makes your answers better too. Instead of capturing the whole display, grab only the part that matters.

A cropped region is a fraction of the file size, and Claude Code isn’t distracted by the rest of your desktop. If you only need Claude to see one error dialog or one misaligned button, don’t send the whole screen.

Fix 2: Save as JPG instead of PNG

PNG is lossless, which is why it’s large. For a screenshot of a UI or an error message, JPG at high quality looks identical to the eye and is often a quarter of the size. Open the PNG in any image editor and export as JPG, or set your screenshot tool to save JPG by default.

Keep PNG only when you genuinely need pixel-perfect sharpness, like a tiny-text terminal capture. For most screenshots, JPG is fine.

> Sounds interesting?

Invoke is $49 once. Free 7-day trial, all features, no credit card.

Try it free →

Fix 3: Resize the dimensions

If a full capture is unavoidable, shrink the pixel dimensions. Claude Code doesn’t need a 3840-pixel-wide image to read a screenshot. Resize to around 1600 to 2000 pixels wide and the file size drops sharply while text stays perfectly readable.

Any image editor does this in seconds. On Windows, even Paint can: open the image, hit Resize, set the width, save.

Fix 4: Reference a file instead of pasting

Here’s a quieter benefit of using file paths over clipboard paste. When you point Claude Code at a file on disk:

Look at C:\Users\zach\Pictures\Screenshots\error.png and explain this stack trace

you can crop, compress, or resize that file first, and you can see exactly what you’re sending before you send it. Pasting straight from the clipboard gives you no chance to shrink it, so you only find out it’s too large after it fails.

This is part of why I default to file paths, and why Invoke saves each snip as a real PNG file you can inspect and reuse. Snip with Win+Shift+S, press one hotkey, and Invoke drops the file path into Claude Code. Because you snipped a region rather than the whole screen, the size problem usually never comes up in the first place.

A quick sanity checklist

  1. Did you snip a region, or the whole screen? Region first.
  2. Is it PNG? Try JPG.
  3. Still over 5 MB? Resize to about 1600 pixels wide.
  4. Reading tiny text? Crop tighter rather than sending more.

The two-keystroke workflow

Invoke is a dictation app for developers that also smooths out the screenshot workflow. Snip a tight region, one hotkey, path in place, no size errors. Then add voice: hold a key, say what you need, release, and the prompt lands in Claude Code. $49 once. Free 7-day trial.