{"version":"2.1.271","anchor":"image-resize-now-uses-a-separate-adjustable-reject-dimensio","canonical_anchor":"image-resize-now-uses-a-separate-adjustable-reject-dimensio","heading":"Image resize now uses a separate, adjustable reject-dimension threshold","tier":"internal","area":"Images","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/image-resize-now-uses-a-separate-adjustable-reject-dimensio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Image resize now uses a separate, adjustable reject-dimension threshold\n\nImage resizing now uses a separate, adjustable threshold for rejecting images instead of reusing the resize target size\n\n**What**\n\nWhen Claude Code resizes an image before passing it to a tool, it used to reuse the same target width and height as the cutoff for rejecting an image outright when its dimensions couldn't be verified. It now uses separate `rejectMaxWidth` and `rejectMaxHeight` values, supplied by a new helper, for that rejection check and its error messages, independent of the dimensions the image is actually resized to.\n\n**Why**\n\nSeparating the reject threshold from the resize target means an image can be resized down to a smaller target size without being rejected outright for exceeding it, since rejection is now judged against its own, more permissive limit.\n\n- Area: Images\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}