{"version":"2.1.304","anchor":"image-handling-explicit-error-when-a-session-cannot-shrink","canonical_anchor":"image-handling-explicit-error-when-a-session-cannot-shrink","heading":"Clear error when an image is too large in a session that cannot shrink images","tier":"notice","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/image-handling-explicit-error-when-a-session-cannot-shrink","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Clear error when an image is too large in a session that cannot shrink images\n\nOversized images now get a clear message saying the session cannot shrink images, instead of a resize failure\n\n**What**\n\nClaude Code normally shrinks images that are too large before sending them. In a session where image decoding (reading the image's pixels so it can be resized) is switched off, an oversized image used to end in a resize failure message. It now gets an explicit message that this session cannot shrink images.\n\nIn a claude-code-server session, Claude Code now reports that images are not decoded there.\n\n**Why**\n\nIf you send an image that is too big in one of these sessions, you are told the real reason it failed instead of seeing a generic resize error.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}