#Sending image/audio
17 messages · Page 1 of 1 (latest)
On current OpenClaw, the WhatsApp channel is still WhatsApp Web (Baileys), not a separate new image API.
Use this syntax for an image send:
openclaw message send --channel whatsapp --target +60xxxxx --media "C:\Users\Wapapapow\.openclaw\media\output.png" --message "Testing~"
A couple important bits:
- For
message send, the current docs/examples use--target, not--to - Your log looks suspiciously like a text-only send, because on current code a real media send logs
(media) - Example expected log shape:
Sending message -> ... (media)Sent message ... -> ... (media)
So I’d try the exact command above first.
Notes for current WhatsApp media handling:
- Images: accepted from local path,
file://, or HTTP(S), then auto-optimized for WhatsApp - Audio: works too, but keep it simple first, small
.ogg/Opus or.mp3is best - Audio/video practical cap is 16 MB
- Images are auto-resized/recompressed as needed
Docs:
If it still fails, please paste:
openclaw --version- the exact command you reran with
--target - the full log output
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.
06:52:35+08:00 [whatsapp] Inbound message +xxxx-> +xxxx(direct, 69 chars)
06:53:02+08:00 [whatsapp] Sending message -> sha256:287c5b20ea2a
06:53:03+08:00 [whatsapp] Sent message 3EB04F92379C3A8205DF6C -> sha256:287c5b20ea2a (1244ms)
06:55:13+08:00 [whatsapp] Inbound message +xxxx-> +xxxx(direct, 69 chars)
07:07:16+08:00 [whatsapp] Inbound message +xxxx-> +xxxx(direct, 69 chars)
07:08:01+08:00 [whatsapp] Sending message -> sha256:287c5b20ea2a
07:08:03+08:00 [whatsapp] Sent message 3EB032F22F6DAA60F4061A -> sha256:287c5b20ea2a (1210ms)
openclaw message send --channel whatsapp --target +60xxxxx --media "C:\Users\Wapapapow.openclaw\media\output.png" --message "Testing~"
using this does not work.
That still looks off.
There isn’t a newer WhatsApp image protocol to switch to, current OpenClaw still sends via WhatsApp Web (Baileys). The bigger clue is your log:
Sending message -> ...
Sent message ... -> ...
On current code, a real media send should show (media) in those lines. Since it doesn’t, it looks like OpenClaw is sending text only, and the attachment is not making it into the outbound request.
Try these in order:
1) Use a file:/// URL on Windows
openclaw message send --channel whatsapp --target +60xxxxx --media "file:///C:/Users/Wapapapow/.openclaw/media/output.png" --message "Testing~"
2) If that still fails, test with an HTTPS image URL
That isolates whether this is a Windows local path parsing issue vs WhatsApp send itself.
3) Paste your version
openclaw --version
A couple of notes:
--targetis the right flag formessage send- For audio, start with a small
.ogg/Opus or.mp3 - Current docs: https://docs.openclaw.ai/cli/message
- WhatsApp docs: https://docs.openclaw.ai/channels/whatsapp
If you want, paste:
openclaw --version- the exact
file:///...command output
- whether an HTTPS image URL works
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.
PS C:\Users\Wapapapow> openclaw --version
OpenClaw 2026.4.9 (0512059)
17:43:42+08:00 [whatsapp] Inbound message +xxxx-> +xxxx(direct, 221 chars)
17:44:17+08:00 [whatsapp] Sending message -> sha256:287c5b20ea2a
17:44:17+08:00 [whatsapp] Sent message 3EB0015665F4763A274C02 -> sha256:287c5b20ea2a (556ms)
currently using .ogg
no media tools are used. i specifically ask openclaw to use this command already
Yep, thanks, that confirms it.
This does not look like a WhatsApp protocol or .ogg problem anymore. It looks like a bug in the CLI/outbound path on 2026.4.9.
Why I’m saying that:
- on current code, if
--mediaactually reaches WhatsApp send, the log prints(media) - your logs never show that
- so OpenClaw is reaching WhatsApp as text-only, even though you passed
--media
And yeah, by “media tools” I did not mean agent tools. I meant the outbound media branch in the send path.
Short version
Your command is valid, but on your build it appears the attachment is not being forwarded into the send request.
One workaround worth trying
Use a file URL instead of a Windows path:
openclaw message send --channel whatsapp --target +60xxxxx --media "file:///C:/Users/Wapapapow/.openclaw/media/output.png" --message "Testing~"
If you get the same no-(media) log, I’d call this a bug and file it here:
https://github.com/openclaw/openclaw/issues
Include this exact repro:
OpenClaw 2026.4.9 (0512059)- command used
- expected: image/audio attached
- actual: text sends, logs never show
(media)
If you want, I can help you write the exact GitHub issue text from what you already pasted.
openclaw message send --channel whatsapp --target +60xxxxx --media "file:///C:/Users/Wapapapow/.openclaw/media/output.png" --message "Testing~"
just tested. still not happening
Yeah, then I’m comfortable calling this a bug.
At this point it’s not:
--tovs--target- Windows path vs
file:/// - image vs
.ogg - “latest protocol”
The giveaway is still the same: on current code, a real attachment send should log (media), and yours never does. So the attachment is getting lost before the WhatsApp transport layer.
Please file it here:
https://github.com/openclaw/openclaw/issues
You can pretty much paste this:
### Summary
`openclaw message send --media ...` sends text to WhatsApp, but does not attach the media.
### Version
OpenClaw 2026.4.9 (0512059)
### Repro
```bash
openclaw message send --channel whatsapp --target +60xxxxx --media "C:\Users\Wapapapow\.openclaw\media\output.png" --message "Testing~"
Also tested:
openclaw message send --channel whatsapp --target +60xxxxx --media "file:///C:/Users/Wapapapow/.openclaw/media/output.png" --message "Testing~"
### Expected
WhatsApp message is sent with the image/audio attached.
### Actual
Only the text message is sent. No media is attached.
### Logs
```text
[whatsapp] Sending message -> sha256:287c5b20ea2a
[whatsapp] Sent message ... -> sha256:287c5b20ea2a (...)
Notably, the log never shows (media).