Browse articles

Object storage

# Uploads are rejected because the bucket quota is full

Bucket quotas are hard: uploads that exceed the limit are rejected. Raise the bucket quota, delete old objects, set lifecycle rules, or add account quota.

2 min readUpdated: October 22, 2026[Baca dalam Bahasa Indonesia](/help/kuota-penuh)

Every bucket has a _hard_ quota. Once usage reaches the quota, uploads that exceed it are rejected, while existing objects can still be read.

## How to fix it

1.  **Raise the bucket quota**: open the bucket, enter the **Bucket quota (GB)**, and click **Save quota**. The maximum is the remaining account quota plus the bucket's current quota.
2.  **Delete objects you no longer need**, for example with `aws s3 rm` or `rclone delete`.
3.  **Set lifecycle rules** so logs and temporary files are deleted automatically after N days. See [Bucket settings](/docs/pengaturan-bucket).
4.  **Check versioning**: when enabled, older versions of objects stay stored and use quota.
5.  **Add account quota**: if all of your account quota is already allocated, choose a storage plan with a larger quota or open a support ticket.

## Good to know

-   The total quota of all buckets may not exceed the account quota.
-   A bucket quota cannot be lowered below its current usage.
-   Usage figures in the dashboard come from the quota scanner and may lag a little after large uploads or deletions.
-   On pay-as-you-go, billing is based on the average GB stored, not on the allocated quota. Raising a quota by itself does not increase your bill.

## See also

-   [Creating and managing buckets](/docs/bucket)
-   [Pay-as-you-go invoices](/help/tagihan-pay-as-you-go)

Still need help?

Open a support ticket from the dashboard and our team will reply as soon as possible.

[Browse the docs](/en/docs)[Open a ticket](/app/support/new)