Frequently Asked Questions

GitLab SaaS Premium and Ultimate

Q: What is changing with Storage and Transfer limits?

We are introducing storage and transfer limits to the GitLab SaaS Paid offerings.

GitLab SaaS Tier	Premium	Ultimate
Storage (in GB per top-level group)	50 GB	250 GB
Transfer (in GB per top-level group per month)	100 GB	500 GB

Note: A 10GB project storage limit for git repository and git LFS is currently active for all projects. Once the namespace storage limit is applicable, the project storage limits will be removed.

Q: Which users are these changes applicable to?

These limits are applicable to users of the GitLab SaaS offerings. These changes do not apply to self-managed users (both free and paid tier) and community programs - including GitLab for Open Source, Education and Startups users.

Customers who are still on the Bronze subscription are not impacted by this change immediately, and the new limits on Premium / Ultimate will be applicable when they upgrade.

If you have questions regarding the storage limit for the Free GitLab SaaS tier please see the Efficient GitLab SaaS Free tier FAQ.

Q: Do these changes apply to Trials?

Yes, GitLab Trial will receive entitlements from GitLab Ultimate.

Q: What is the effective date of the changes?

For existing paid tier users:

Storage limits are not yet applicable for paid customers. GitLab will release additional features in the coming months for users to view and manage storage usage well ahead of the storage limits being applicable.
Storage limits will be added to the subscription terms at a later date, and only top-level groups on the updated terms will be have storage limits applied.
We intend to roll out application of these limits gradually. We will show in-app notifications to affected top-level groups, including any subgroups and projects, prior to the storage limits being applied. Users that are already above the limit will see the in-app notifications at least 60 days ahead of enforcement. Users that go above the limit during the period where the in-app notifications are showing will see them as soon as they go above the threshold.
Transfer limits will not be applicable until further communication from GitLab.

For existing paid tier users on a multi-year contract:

Storage limits will not apply to customers until their first renewal after the storage limits have been added to the subscription terms (slated for a later date). After a customer is on the new subscription terms, limit effective date would apply based on the timeline outlined above.

Q: Will limits apply only once both storage and transfer are available?

No, application of storage and transfer limits will be independent of each other. Storage usage visibility, and storage limits will be first, transfer usage visibility and transfer limits will follow.

Managing your Storage Usage

Q: What constitutes Storage usage?

Currently storage includes pipeline job artifacts, repositories, package and container registries, snippets, Git LFS, wiki storage, dependency proxy. Future product features that allow you to store data will also be incorporated into the storage usage count, when available.

Q: How can I view and manage my storage usage?

You can view the storage usage on the Group Settings page for Usage Quota in the Storage tab. The summaries are divided into all storage types listed in the answer to the "What constitutes Storage usage?" question. Each type provides details on how to proceed with detailed analysis and cleanup procedures.

Q: How can I reduce the amount of Storage consumed?

Below you will find steps for managing the different storage types:

Pipeline job artifacts: You can set an expiration policy for when artifacts can be deleted. If not specified, the default expiration time on GitLab.com SaaS is 30 days. You can also delete job artifacts manually - remember this can lead to data loss.
Repositories: Repositories can become large over time. You can reduce your repository size using the steps highlighted in the documentation.
Container Registry: You can set an cleanup policy to programmatically remove old, unused images and tags. You can also use the user interface or APIto delete items as well.
Packages: You can delete an entire package or files within a package
Dependency Proxy: You can set an expiration policy to programmatically clear the cache. Or, you can manually purge the cache using the API.
Snippets: Snippets follow the same process as reducing repository size.
Wikis: Wikis follow the same process as reducing repository size.

Q: How can I automate storage usage analysis and cleanup?

You can automate storage management with the GitLab API to programmatically view and delete storage data types. For more information, see the storage management automation documentation.

Q: How will the storage limits affect me when I’m contributing to another project?

We plan to apply a cost factor to forks, similar to what is done today for compute minutes, as long as the fork relationship is maintained.

Managing your Transfer Usage

Q: What constitutes transfer usage?

Transfer is measured as the amount of data egress leaving GitLab.com, except for:

Transfer generated by GitLab.com Shared Runners
Transfer generated by GitLab Runners authenticating with a CI_JOB_TOKEN
Transfer generated by deployments authenticating with a DEPLOY_TOKEN
The web interface

The primary use cases affected by transfer limits are end users working with code repositories, and public distribution of containers and packages. Future product features that allow transfer of data will also be incorporated into the transfer usage count, when available.

Q: Can I proactively monitor and reduce my transfer usage?

Viewing transfer usage is not yet available. Until the usage report is available on the Group Settings Usage Quota Page, transfer limits will not be programmatically applied. If your usage is significantly high, the GitLab team will reach out to you to help manage your usage.

Purchasing additional Storage and Transfer

Q: How much does it cost to buy additional Storage and Transfer units?

Additional storage or transfer units can be purchased from the GitLab Customers Portal at $60/year that includes both 10GB of storage and 20GB/month transfer. For example:

If you require 15GB storage, you will pay $120 for the year.
If you require 25GB transfer per month, you will pay $120 for the year.
If you require both 15GB storage and $25GB Transfer per month, you will still pay $120 for the year.
If you have purchased 5 add-ons, you will be entitled to 50GB storage and 100GB transfer/month.

Q: Does my previously purchased additional storage apply to my top-level group once namespace storage limits are in effect?

Yes, once namespace storage limits are in effect any previously purchased additional storage, including additional storage purchased due to project storage limits, will be applicable to the top-level group.

More information

For more information on managing and reducing your storage usage, please contact GitLab support or your GitLab sales representative.

Storage and Transfer limits for the Paid GitLab SaaS tiers FAQ