Can't save pics


I don’t know exactly how this happened, but I was browsing 4chan via Brave this morning and I saved several memes no issue. Later in the evening I went to Facebook to send one to a friend. I downloaded the wrong version earlier (reoccurring meme) so I returned to the archive to download the right one. It wouldn’t let me.

Right click
Save Image
This comes up:

It won’t say .jpeg or gif like usual, just the all files option and when I try that it downloads but doesn’t work.

*Meme in pic is unrelated to meme I was originally attempting to send.
*Other browsers can download pics just fine

Please help, I appreciate this browser and the work put into it. This is my first major issue :frowning:
Thank you for reading!

Windows 10 Home Version 1709
Brave Data:
Brave: 0.20.29
V8: 6.4.388.40
rev: 4fc3c8ff3bcb6af75088b125e00d3a70382b9bec
Muon: 4.7.9
OS Release: 10.0.16299
Update Channel: Release
OS Architecture: x64
OS Platform: Microsoft Windows
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 64.0.3282.119


I am able to see the file extension when saving

Do you mind clearing browser cache once and trying again?


Just tried, still cannot save pics or Webms.


On gifs it’s a breeze, but not for photos. It’s like every picture has a secret, randomly located, tiny area that you have to long-press to make the dropdown appear with the option to save. Sometimes I can find it. Sometimes I cant. And the times it has worked, when I try to do it again the spot suddenly stops working. It’s like a madhouse in here!


@rjcIII, before we continue with any further troubleshooting, can you go ahead and update Brave to the most recent build? Your info says you’re on version v0.23.29 (which is strange, cc @kamil or @sriram - was this an actual release number?) but the most up to date release is v0.23.107.


That was an older release build. I would suggest to upgrade to the latest version and check once.


@Mattches, it doesn’t look like 0.23.29 was a version that was released [1]. I can’t seem to find 0.23.29 under the releases page either [2]. I wonder if this was one of those situations where 0.23.29 was an off build that was later removed?

@rjcIII, out of curiosity, do you remember how you ended up getting 0.23.29? Was it via a manual install or an automatic update via the browser?

Either way, did updating to a new version fix the issues you were experiencing?


Yeah I also couldn’t find a 0.23.29 release. Thanks for double checking for me @kamil