#Broken downloads in Clawd browser: files without extensions (UUID) and impossible to locate

1 messages · Page 1 of 1 (latest)

shell dome
#

I really don’t get it — I’m stuck. I’m having an issue with the Clawd browser when it tries to download files. Whether it’s PDFs, images, or anything else, it downloads them but there’s no file extension, so they aren’t recognized as normal files. They end up with a name that looks like a UUID.

On top of that, I can’t figure out which folder they’re being saved to. I’ve tried multiple times to get Clawdbot to fix the issue, but it can’t find them either — it just hallucinates answers. So I can’t pinpoint what’s actually going wrong. Does anyone have an idea?

c9e2ff21-948a-4df4-8b7f-e7fb40e56fd2.png e1eeb537-4697-4fe4-96e1-495c097a63dd.png 25e6465f-19b9-4425-9a22-a96b91b4930b.png
#

@solid haven

#

@solid haven I really don’t get it — I’m stuck. I’m having an issue with the Clawd browser when it tries to download files. Whether it’s PDFs, images, or anything else, it downloads them but there’s no file extension, so they aren’t recognized as normal files. They end up with a name that looks like a UUID.

On top of that, I can’t figure out which folder they’re being saved to. I’ve tried multiple times to get Clawdbot to fix the issue, but it can’t find them either — it just hallucinates answers. So I can’t pinpoint what’s actually going wrong. Does anyone have an idea?

c9e2ff21-948a-4df4-8b7f-e7fb40e56fd2.png 25e6465f-19b9-4425-9a22-a96b91b4930b.png e1eeb537-4697-4fe4-96e1-495c097a63dd.png
solid havenBOT
# shell dome I really don’t get it — I’m stuck. I’m having an issue with the Clawd browser wh...

Based on the images, I can see the issue clearly now. Let me explain what's happening:

The Problem:
The downloads are coming from servers that serve files as "blobs" without sending a proper Content-Disposition header with a filename. When servers don't tell the browser what to name the file, browsers generate random UUID names instead. This happens in any browser, not just Clawd — it's standard web behavior.

The Solution:

  1. Use "Save As" instead of automatic downloads — you can name the file yourself before saving
  2. Right-click → "Save link as..." on PDF/image links to control the filename
  3. Manually rename after download — the files ARE saved, just with UUID names

Where files are saved:
By default, Clawd browser uses your system's download folder (same as Chrome/Edge). Check ~/Downloads or your configured download location.

TL;DR: This isn't a Clawd bug — it's how web servers work. The files are downloading fine; they just need proper headers from the source server, which is outside Clawd's control. The workaround is to use "Save As" to name files yourself.

Happy to help! 🦐