Audio recording storage limits

Audio Recording produces real files, and several limits decide whether your recording is saved, posted, or dropped.

✂️ The two limits that cut recordings

Setting	Effect
Timeout (seconds)	Hard cap on recording duration — the bot stops recording when it's reached
Max Audio Size (MB)	Hard cap on the output file size

Long meetings hitting silence? Check the timeout first. Files missing for long sessions? Check the max size.

📦 Where recordings go

By default the finished file is posted to the configured Target Text Channel. That means Discord's own upload limit applies — it depends on the server's boost level, and it is often lower than your configured max size. A recording that exceeds Discord's upload limit will fail to post even if it passed YAWBDB's limit.

☁️ Use external storage for longer recordings

For sessions that outgrow Discord's limits, configure the External provider (S3) in the feature settings:

Works with AWS S3 and S3-compatible storage (MinIO, etc. — set the custom endpoint)
Bucket, region, access key and secret are configured per server
An optional public base URL lets the bot post a download link instead of uploading the file to Discord

🗜️ Keeping files smaller

MP3 bitrate (kbps) — lower bitrate = smaller files. Voice is fine well below music bitrates.
Recording mode — all_mix produces one mixed file; per_user produces one file per speaker (more files, each smaller).
Split long sessions into multiple recordings instead of one marathon take.

📝 Transcripts

If transcription is enabled, the transcript and AI summary are text — they are not affected by audio size limits. A recording that failed to upload may still produce a transcript, depending on where the failure happened.