{"version":"2.1.311","anchor":"attachment-downloads-over-memory-files-spill-to-disk-with","canonical_anchor":"attachment-downloads-over-memory-files-spill-to-disk-with","heading":"Very large attachments are saved to disk instead of failing","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/attachment-downloads-over-memory-files-spill-to-disk-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Very large attachments are saved to disk instead of failing\n\nAttachments too big to hold in memory are now written to the uploads folder rather than rejected, and large images get a smaller copy for Claude\n\n**Unclear.** This new download handling sits behind conditions that were not identified, so it is unclear whether it is active for you.\n\n**What**\n\nClaude Code has reworked how it downloads files attached to a conversation. Before, a file larger than the memory limit failed as too large. Now:\n\n- such a file is written to the uploads folder on disk, or fetched by the machine that holds that folder\n\n- a large image also gets a separate, scaled-down copy, which is the one Claude looks at\n\nWhen the download cannot be completed, Claude Code can report that the machine with the uploads folder could not download the file.\n\n**Why**\n\nLarger attachments may now reach Claude where they used to fail.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}