Increase Default Audio Upload Limits and Offer Paid Options

Problem

The current default audio upload limit of 10 per month is extremely low.
At this rate, I—and many others—cannot fully realize the vision we have for our games.

Audio plays a critical role in game development by enhancing immersion, storytelling, and overall player experience. This strict limit negatively impacts developers who want to create high-quality projects.

While it’s true that verifying your ID can increase the limit (Account Verification), many developers—including myself—choose not to verify for personal reasons. This leaves a large portion of the community restricted by the default cap.

Proposal

  • Increase the default monthly upload limit to a more reasonable number that better supports development needs.
  • Introduce an option to pay for additional uploads, making it scalable for developers who need more assets.
    • Ideally, this would be integrated cleanly with Open Cloud API so developers and automation systems can manage uploads efficiently.
10 Likes

even tho it would be nice, the 10 audio limit is obviously there to stop spammers, it’s ok to not use an ID to verify but still if you’re that desperate to upload more you should verify

1 Like

Paid option would be as good as badges where it lets you create 5 free badges per day, then you get charged 100 robux to create more than 5 free badges.
Though I have huge upload limits without id verification, I still believe those who weren’t picked and havent ID verified (and potentially dont want to) should have opportunity to somehow exceed this hardcap.
It is cool that we can upload audios for free rather than getting charged robux for it.
… but at what cost?

3 Likes

bump, they need to let us pay a (small) robux fee to upload past the limit

it could also be like datastore limits, where the upload limit is based on your game’s players (or possibly place visits in this case)

2 Likes

Bumping.
I agree that they should add fee for audio (if you want to upload more than you can).

1 Like

OP here — adding more specifics so it’s easier to evaluate.

Problem:

The default limit (10 uploads per 30 days) is too restrictive for legitimate development. Original audio work often needs:

  • multiple variations per action (hits, misses, distance, material)
  • iteration (volume fixes, trimming, EQ, re-exports)
  • replacements when placeholders get swapped out

That means devs hit the cap quickly even when behaving normally.

Solution:

  1. Higher base quota: raise default to ~25–50 per 30 days (still modest).
  2. Tiering via trust signals (not only ID): account age, verified phone/email, place activity/visits, history of non-moderated uploads, DevEx/verification, etc.
  3. Paid options: expansion packs or pay-per-upload once you exceed your free tier.
  4. Abuse controls: rolling rate limits, cool-downs, extra restrictions for new accounts, and tighter review triggers for high-volume accounts.
  5. Open Cloud support: better for teams + CI pipelines and reduces repetitive manual work.

Intent:

Make it easier for developers to iterate and ship high-quality games, while still preventing abuse.

2 Likes