This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 25%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
I am planning to migrate our DevOps environment from on-premise to Azure DevOps. I have noticed that there is a 2 GB limit for repositories in Azure DevOps.
Could you please clarify how this size limit is calculated? Specifically, I would like to understand whether it includes the entire commit history, branches, and any other data associated with the repository.
Additionally, if our repository exceeds the 2 GB limit, how can we increase this limit? Could you also provide details on the associated costs for increasing the repository size or any alternatives available to manage large repositories?
Azure DevOps calculates repo size based on the entire commit history, all branches, tags, and Git objects. There's a 2 GB soft limit (performance impact) and a 10 GB hard limit (pushes blocked). The limit cannot be increased. To manage large repos, use Git LFS, split repositories, or prune history. Git LFS offers 2 GB free storage;