Storage usage quota (FREE)

Introduced in GitLab 12.0.

Moved to GitLab Free.

Namespace storage limit

Namespaces on GitLab SaaS have a storage limit. For more information, see our pricing page. This limit is not visible on the Usage quotas page, but will be prior to enforcement. Self-managed deployments are not affected.

Storage types that add to the total namespace storage are:

Git repository
Git LFS
Artifacts
Container registry
Package registry
Dependency proxy
Wiki
Snippets

If your total namespace storage exceeds the available namespace storage quota, all projects under the namespace are locked. A locked project will not be able to push to the repository, run pipelines and jobs, or build and push packages.

To prevent exceeding the namespace storage quota, you can:

Reduce storage consumption by following the suggestions in the Manage Your Storage Usage section of this page.
Apply for GitLab for Education, GitLab for Open Source, or GitLab for Startups if you meet the eligibility requirements.
Consider using a self-managed instance of GitLab which does not have these limits on the free tier.
Purchase additional storage units at $60/year for 10GB of storage.
Start a trial or upgrade to GitLab Premium or Ultimate which include higher limits and features that enable growing teams to ship faster without sacrificing on quality.
Talk to an expert to learn more about your options and ask questions.

Namespace storage limit enforcement schedule

Storage limits for GitLab SaaS Free tier namespaces will not be enforced prior to 2022-10-19. Storage limits for GitLab SaaS Paid tier namespaces will not be enforced for prior to 2023-02-15. Enforcement will not occur until all storage types are accurately measured, including deduplication of forks for Git and LFS.

Impacted users are notified via email and in-app notifications at least 60 days prior to enforcement.

Project storage limit

Projects on GitLab SaaS have a 10GB storage limit on their Git repository and LFS storage. Once namespace-level storage limits are enforced, the project limit will be removed. A namespace has either a namespace-level storage limit or a project-level storage limit, but not both.

When a project's repository and LFS reaches the quota, the project is locked. You cannot push changes to a locked project. To monitor the size of each repository in a namespace, including a breakdown for each project, you can view storage usage. To allow a project's repository and LFS to exceed the free quota you must purchase additional storage. For more details, see Excess storage usage.

View storage usage

Prerequisites:

To view storage usage for a project, you must have at least the Maintainer role for the project or Owner role for the namespace.
To view storage usage for a namespace, you must have the Owner role for the namespace.

Go to your project or namespace:
- For a project, on the top bar, select Main menu > Projects and find your project.
- For a namespace, enter the URL in your browser's toolbar.
From the left sidebar, select Settings > Usage Quotas.
Select the Storage tab.

The statistics are displayed. Select any title to view details. The information on this page is updated every 90 minutes.

If your namespace shows 'Not applicable.', push a commit to any project in the namespace to recalculate the storage.

Storage usage statistics

Introduced project-level graph in GitLab 14.4 with a flag named project_storage_ui. Disabled by default.

Enabled on GitLab.com in GitLab 14.4.

Enabled on self-managed in GitLab 14.5.

Feature flag removed in GitLab 14.5.

The following storage usage statistics are available to a maintainer:

Total namespace storage used: Total amount of storage used across projects in this namespace.
Total excess storage used: Total amount of storage used that exceeds their allocated storage.
Purchased storage available: Total storage that has been purchased but is not yet used.

Manage your storage usage

To manage your storage, if you are a namespace Owner you can purchase more storage for the namespace.

Depending on your role, you can also use the following methods to manage or reduce your storage:

Excess storage usage

Excess storage usage is the amount that a project's repository and LFS exceeds the free storage quota. If no purchased storage is available the project is locked. You cannot push changes to a locked project. To unlock a project you must purchase more storage for the namespace. When the purchase is completed, locked projects are automatically unlocked. The amount of purchased storage available must always be greater than zero.

The Storage tab of the Usage Quotas page warns you of the following:

Purchased storage available is running low.
Projects that are at risk of being locked if purchased storage available is zero.
Projects that are locked because purchased storage available is zero. Locked projects are marked with an information icon ({information-o}) beside their name.

Excess storage example

The following example describes an excess storage scenario for a namespace:

Repository	Storage used	Excess storage	Quota	Status
Red	10 GB	0 GB	10 GB	Locked {lock}
Blue	8 GB	0 GB	10 GB	Not locked
Green	10 GB	0 GB	10 GB	Locked {lock}
Yellow	2 GB	0 GB	10 GB	Not locked
Totals	30 GB	0 GB	-	-

The Red and Green projects are locked because their repositories and LFS have reached the quota. In this example, no additional storage has yet been purchased.

To unlock the Red and Green projects, 50 GB additional storage is purchased.

Assuming the Green and Red projects' repositories and LFS grow past the 10 GB quota, the purchased storage available decreases. All projects remain unlocked because 40 GB purchased storage is available: 50 GB (purchased storage) - 10 GB (total excess storage used).

Repository	Storage used	Excess storage	Quota	Status
Red	15 GB	5 GB	10 GB	Not locked
Blue	14 GB	4 GB	10 GB	Not locked
Green	11 GB	1 GB	10 GB	Not locked
Yellow	5 GB	0 GB	10 GB	Not locked
Totals	45 GB	10 GB	-	-