{"version":"2.1.287","anchor":"mcp-image-blobs-may-be-scaled-large-output-path-normalises","canonical_anchor":"mcp-image-blobs-may-be-scaled-large-output-path-normalises","heading":"Oversize images can be scaled down before they are uploaded","tier":"notice","area":"Attachments","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-image-blobs-may-be-scaled-large-output-path-normalises","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Oversize images can be scaled down before they are uploaded\n\nClaude Code can now shrink oversize PNG, JPEG and WebP images before uploading them, and tries a new image path for images sent by MCP servers\n\n**Unclear.** It is not clear which features use the new upload path, or whether MCP images go through the scaling step.\n\n**What**\n\nClaude Code has a new way of uploading images and files. Before an image is sent, oversize PNG, JPEG and WebP images can now be scaled down, with a limit of 40,000,000 pixels. If an image cannot be scaled, Claude Code logs a note and sends the image at its original size. Files are sent in pieces rather than all at once.\n\nSeparately, when an MCP server sends back an image, it now goes through a new image-handling step first. An MCP server is an outside program that gives Claude Code extra tools through the Model Context Protocol. Before, such images went straight to the general image handler.\n\n**Why**\n\nThis changes how large images and files are uploaded, so very large pictures may arrive smaller than the originals.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}