SharePoint version history: why it consumes storage and how to limit it

SharePoint storage rarely fills up because of the visible files themselves, but rather from invisible versions and the recycle bin in the background. Since the introduction of automatic version history limits, Microsoft says this storage consumption is reduced by up to 96 percent compared to pure count limits, without users having to forego older versions. Anyone looking for the cause of a full quota should therefore look there first. As of: August 2026.

Why does version history fill up storage even though no one is uploading large files?

A practical case documented in the official Microsoft Q&A forums shows the pattern: A tenant unknowingly lost around 140 terabytes of free storage until the quota was exceeded and the site switched to read-only mode. The answer cites recycle bin contents and accumulated file versions as the main causes, which are precisely the areas that remain invisible in the normal library view. Every saved version of a file counts fully toward the storage quota, even if only a small part of the content has changed.

What makes the Automatic setting different from a fixed count limit?

According to Microsoft's documentation on version history limits, Automatic is the recommended default setting and works according to a graduated algorithm rather than a rigid count limit: Within the first 30 days, all versions are retained up to a limit of 500, between day 30 and 60 only one version per hour, between day 60 and 180 one version per day, and older than 180 days one version per week, until again the 500 upper limit is reached. According to Microsoft's planning guide for version storage, this graduated reduction leads to approximately 96 percent less version storage compared to a pure count limit over a documented example period of six months, and in a separate example with continuous editing over several months to approximately 94 percent reduction. Users do not lose access to relevant recovery points, because precisely the newer, more likely to be needed versions are preserved.

At what levels can version limits be set?

Version history limits apply at four possible levels: organization, site, library, and individual OneDrive account. Global and SharePoint administrators set the default setting for the entire organization, which automatically applies to all newly created libraries. Site owners can break this inheritance for a single site, but according to Microsoft's guide to changing site limits only via PowerShell, not through the graphical interface. A change at the site level can optionally be applied only to new libraries, only to existing ones, or to both simultaneously, with the update of existing libraries running asynchronously in the background and, according to Microsoft, can take up to 24 hours.

What applies if I want to set a manual limit instead of Automatic?

In manual mode, a count limit for major versions can be configured with or without an additional expiration date in days. Important for practice: The user interface prevents values below 100 major versions or below 30 days expiration time, because Microsoft explicitly classifies such low values as a risk for unintended data loss, even though technically lower values could be set via the public API. Versions that exceed a set limit are also permanently deleted and not moved to the recycle bin, so they cannot be recovered after deletion. An exception applies to content under a retention policy or an eDiscovery hold: There, version limits are ignored according to Microsoft until the retention period expires or the hold is released.

If you want to handle SharePoint cleanup as part of an ongoing automation, you'll find support in automation consulting.

Frequently asked questions about SharePoint version history

Should I choose Automatic or a manual limit for my organization?

For most organizations, Microsoft recommends the Automatic setting because it provides the best storage-benefit compromise without administrators having to estimate count or expiration values themselves. A manual limit is worthwhile especially where a fixed, predictable number of versions must be retained for regulatory or internal reasons.

Can I restore already deleted versions from the recycle bin?

It depends on the deletion method. If a user manually deletes a version from the version history of a file, according to Microsoft it lands in the website's recycle bin and can be restored there for a limited time. However, if versions are automatically removed by a set limit or a scheduled trim job, it bypasses the recycle bin entirely and is permanent.

Does a new organization limit automatically apply to existing libraries?

No, not automatically. A changed default setting at the organization level initially only applies to newly created libraries. To align existing libraries and trim existing versions, additional, separate steps are required according to Microsoft.

Does a version limit prevent important documents from being permanently archived as records?

No. According to Microsoft, documents that are explicitly marked as records are exempt from automatic version deletion, regardless of the configured limit.