doc/user/storage_usage_quotas.md
{{< details >}}
{{< /details >}}
GitLab projects have a storage limit for their Git repository and Large File Storage (LFS). Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.
When a project's repository and LFS exceed the limit, the project is set to a read-only state and some actions become restricted.
{{< details >}}
{{< /details >}}
Each project in a Free tier namespace on GitLab.com has 10 GiB of free storage.
To increase storage of the project's repository and LFS to more than 10 GiB, you must purchase more storage.
{{< details >}}
{{< /details >}}
Each project in a Premium or Ultimate tier on GitLab.com has 500 GiB of storage.
When a project exceeds the storage limit, owners of the group and top-level namespace receive notifications through the UI and email.
To manage storage usage, contact your account team or GitLab Support.
Expired storage can exist when purchased storage is not de-provisioned at the end of your subscription period. If you experience an unexpected drop in purchased storage, expired storage could have been removed from your account. For more information and solutions, contact support.
{{< details >}}
{{< /details >}}
You can view the following statistics for storage usage in projects and namespaces:
Prerequisites:
To view storage:
If your namespace shows 'Not applicable.', push a commit to any project in the
namespace to recalculate the storage.
Storage and network usage is calculated with the binary measurement system (1024 unit multiples). Storage usage is displayed in kibibytes (KiB), mebibytes (MiB), or gibibytes (GiB). 1 KiB is 2<sup>10</sup> bytes (1024 bytes), 1 MiB is 2<sup>20</sup> bytes (1024 kibibytes), and 1 GiB is 2<sup>30</sup> bytes (1024 mebibytes).
A cost factor is applied to the storage consumed by project forks so that forks consume less namespace storage than their actual size. The cost factors for forks storage reduction applies only to namespace storage. It does not apply to project repository storage limits.
To view the amount of namespace storage the fork has used:
The cost factor applies to the project repository, LFS objects, job artifacts, packages, snippets, and the wiki.
The cost factor does not apply to private forks in namespaces on the Free plan.
{{< details >}}
{{< /details >}}
Excess storage usage is the amount that exceeds the 10 GiB free storage of a project's repository and LFS. If no purchased storage is available, the project is set to a read-only state. You cannot push changes to a read-only project.
To remove the read-only state, you must purchase more storage for the namespace. After the purchase has completed, the read-only state is removed and projects are automatically restored. The amount of available purchased storage must always be greater than zero.
The Storage tab of the Usage quotas page displays the following:
The total storage includes the free and excess storage purchased. The remaining excess storage is expressed as a percentage and calculated as: 100 % - ((excess storage used - excess storage purchased) × 100).
The following example describes an excess storage scenario for projects in a namespace:
| Repository | Storage used | Excess storage | Quota | Status |
|---|---|---|---|---|
| Red | 10 GiB | 0 GiB | 10 GiB | Read-only {{< icon name="lock" >}} |
| Blue | 8 GiB | 0 GiB | 10 GiB | Not read-only |
| Green | 10 GiB | 0 GiB | 10 GiB | Read-only {{< icon name="lock" >}} |
| Yellow | 2 GiB | 0 GiB | 10 GiB | Not read-only |
| Totals | 30 GiB | 0 GiB | - | - |
The Red and Green projects are read-only because their repositories and LFS have reached the quota. In this example, no additional storage has yet been purchased.
To remove the read-only state from the Red and Green projects, 50 GiB additional storage is purchased.
If some projects' repositories and LFS grow past the 10 GiB quota, the available purchased storage decreases.
| Repository | Storage used | Excess storage | Quota | Status |
|---|---|---|---|---|
| Red | 15 GiB | 5 GiB | 10 GiB | Not read-only |
| Blue | 14 GiB | 4 GiB | 10 GiB | Not read-only |
| Green | 11 GiB | 1 GiB | 10 GiB | Not read-only |
| Yellow | 5 GiB | 0 GiB | 10 GiB | Not read-only |
| Totals | 45 GiB | 10 GiB | - | - |
In this example:
To manage your storage, if you are a namespace Owner of a Free GitLab.com namespace, you can purchase more storage for the namespace.
In the Premium and Ultimate tier, depending on your role, you can also reduce repository size. To automate storage usage analysis and management, see storage management automation.
In addition to managing your storage usage you can consider these options for increased consumables:
{{< details >}}
{{< /details >}}
[!note] To exceed the free tier 10 GiB limit on your Free GitLab.com namespace, you can purchase more storage for your personal or group namespace.
Prerequisites:
[!note] Storage subscriptions renew automatically each year. You can disable automatic subscription renewal.
The Purchased storage available total is incremented by the amount purchased. The read-only state for all projects is removed, and their excess usage is deducted from the additional storage.
If you're using GitLab.com, you can purchase additional storage so your pipelines aren't blocked after you have used all your storage from your main quota. You can find pricing for additional storage on the GitLab Pricing page.
To purchase additional storage for your group on GitLab.com:
{{< tabs >}}
{{< tab title="Group owner" >}}
{{< /tab >}}
{{< tab title="Billing account manager" >}}
{{< /tab >}}
{{< /tabs >}}
After your payment is processed, the extra storage is available for your group namespace.
To confirm the available storage, follow the first three steps listed previously.
The Purchased storage available total is incremented by the amount purchased. All locked projects are unlocked and their excess usage is deducted from the additional storage.