Brave has been on a busy run lately, with the browser rolling out Brave Origin, pushing v1.91 changes on Android, and drawing attention for its broader strategy around search and AI competition. But alongside those updates, a new complaint has emerged from some desktop users on Brave v1.91.168, and this one sounds annoyingly specific in the way software regressions often do.

The issue affects image drag-and-drop on certain websites and local files when the browser switches to the magnifying-glass cursor. In affected cases, users can still open images, zoom into them, and drag smaller images without trouble. But with larger images, or images that trigger the zoom cursor, drag-and-drop simply stops working. Instead of moving the image to the desktop or a folder, nothing happens.
The problem seems to mostly occur on Windows and seems tied to images that are larger than roughly 1600px in one dimension, though not every image above that threshold is affected. It can also show up even outside websites, including when opening a local image file directly in Brave. That suggests the bug is not tied to a specific site layout or web app behavior.
I tried to reproduce the issue myself on Windows, which appears to be the platform most affected by the reports, but I was not able to trigger it in my own tests. That said, my experience does not cancel out what other users are seeing, and the reports are detailed enough to deserve attention. The behavior also appears on macOS and Linux reports, although Windows users seem to be the most affected overall.

The good news is that Brave’s support team has already picked up the issue and is actively looking into it through the company’s GitHub tracker. In the meantime, some affected users have found a workaround by using the Magic Drop extension from the Chrome Web Store, though that is obviously more of a workaround than a real fix.

For now, Brave users who rely on image drag-and-drop may want to keep an eye on the browser’s next desktop update, especially if they are running v1.91.168.
We will also keep a close eye on the development tracker and let you know when the official fix rolls out.