Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
SharePoint supports file-type–specific version history limits. It gives organizations finer control over how versions are retained by allowing certain file types to use different version limits than the default library settings.
The extension of a file determines its file type. Today, the following file-type categories are supported:
| Name (case-insensitive) | Description | Extensions |
|---|---|---|
| audio | Audio files | au, flac, m4a, mp3, ogg, wav, wma, aac, m4b, m4p |
| video | Video files | mts, m2ts, ts, 3g2, 3gp, 3gp2, 3gpp, asf, wmv, avi, m4v, mov, mp4, mp4v, webm, movie, mkv, mpg, flv, mpeg |
| outlookpst | Outlook Data File | pst |
When you configure a file‑type–specific version history limit on a document library, that limit replaces the library’s default version history settings for that file type. Versions of the specified file type follow only the file-type version history limit.
Example
Suppose your document library uses an automatic version history limit that applies to all files. You notice that audio files are consuming more storage than expected. To address the storage issue, you want a stricter version limits for audio files and keep the existing automatic limit for all other files.
To implement the version limits, you configure a file-type override that sets a 30‑day manual expiration period and a maximum of 100 major versions for audio files. After this change:
- New versions of audio files follow the file-type–specific manual limits.
- New versions of other file types continue using the library’s automatic limit unchanged.
Note
Today, OutlookPST files use a manual limit that keeps 30 major versions and no expiration by default.
Learn More
For more information, check out the following resources: