| title | Size and count limits |
|---|---|
| description | Package count and size limits in Azure Artifacts |
| ms.service | azure-devops-artifacts |
| ms.topic | limits-and-quotas |
| ms.date | 02/25/2022 |
| monikerRange | <=azure-devops |
[!INCLUDE version-lt-eq-azure-devops]
Azure Artifacts is a highly scalable package management solution that enables developers to create, host, and share different types of packages. In this article, we will cover the size and count limits that developers should be aware of when using Azure Artifacts. Some of these limits are imposed by the client tools that Azure Artifacts integrates with (example nuget.exe).
Note
Azure Artifacts provides 2 GiB of free storage for each organization. This free tier is designed to help you evaluate if Azure Artifacts fits your workflow. As your organization starts handling more critical tasks, we recommend set up billing to ensure you have the appropriate resources.
- 5000 versions per package ID.
- Unlimited package IDs per feed.
- 20 upstreams per package type per feed.
Note
You can use retention policies to automatically delete older package versions.
-
NuGet packages: limited to 500 MiB per file.
-
Npm packages: limited to 500 MiB per file. Additionally, Azure Artifacts enforces a separate hard limit of 375 KB specifically for the package.json file.
-
Maven packages: limited to 500 MiB per file.
-
Python packages: limited to 500 MiB per file.
::: moniker range="= azure-devops"
-
Cargo packages: limited to 500 MiB per file.
-
Universal Packages: up to 4 TiB per file (Recommended for large binary files).
Note
Universal Packages containing an exceptionally large number of files (100K+) may fail to publish. In this case, we recommend bundling the files into a ZIP or TAR archive to reduce the file count.
::: moniker-end