Audio Upload Bug?

Hi all, I am experiencing an issue uploading audio files to Blob storage. I believe this is a bug, I’ve done a fair amount of testing and am stumped. Below is the output of Claude that goes over all of the steps we’ve taken to try and figure this out. Anybody else experiencing this?

I'm experiencing an issue with Vercel Blob where audio file uploads consistently fail with a "Token mismatch" error, while the same token successfully uploads images and videos.
Issue Details:
Error: HTTP 403 with {"error":{"code":"forbidden","message":"Token mismatch"}}
Affected Files: All audio formats (MP3, AAC, WAV)
File Sizes: Tested with files from 2.3MB to 27MB (well under 5TB limit)
Working Files: Images (PNG/WebP) and videos (MP4) upload successfully with same token
Technical Details:
Token: Valid BLOB_READ_WRITE_TOKEN with write permissions
Upload Method: Server uploads using @vercel/blob SDK put() method
Account: Pro plan
Formats Tested:
MP3 (2.3MB) → 403 "Token mismatch"
AAC (2.4MB) → 403 "Token mismatch"
PNG (377KB) → ✅ Success
MP4 (55MB) → ✅ Success
Evidence Token is Valid:
Images and videos upload successfully using identical code path and token, confirming the token has proper write permissions.
Documentation Reference:
According to your Blob documentation, audio files should be supported: "audio/*" MIME types resolve to content-disposition: inline header.

Core Questions:
* Are there account-level restrictions on audio file uploads, or is this a configuration issue? The documentation indicates audio files are supported, but our testing shows they're consistently blocked.
* Could you please clarify if there are additional permissions needed for audio file uploads, or if this might be a token scope limitation?

Hi @luismqueral, welcome to the Vercel Community!

I’m sorry that you are facing this issue. Can you share the repo or the code snippet where this upload is initiated from?

sure thing! here you go:

Hi @luismqueral, thanks for sharing more information. Our team confirmed that the error Token mismatch is only returned when the client sends the wrong Authentication Header. Can you confirm the token sent with the request is indeed authorized for this action. Please double check the BLOB_READ_WRITE_TOKEN used for the upload.