OneDrive is good at the job it was built for. Files sync quietly across devices, sharing a document takes two clicks, and for most day-to-day work in a Microsoft 365 organization it simply disappears into the background, which is the highest compliment infrastructure can get. If you use it personally or run a small team on it, nothing in this article will change your mind, and it should not.
The limitations live at the edges. Organizations wander into them without noticing, usually because a shared library grew past what anyone planned, or because video recordings quietly became the heaviest thing in storage. If your team has started treating OneDrive as the company's video library or evidence store, this article maps where the platform actually ends, with Microsoft's current numbers rather than folklore. Our video content management guide covers what purpose-built systems do differently if you want the bigger picture.
One correction worth making up front, because older articles (including an earlier version of this one) still repeat it: OneDrive's file size limit is not 15 GB. Microsoft raised it years ago. The real numbers are below.
The Hard Limits, With Current Numbers
These are Microsoft's published restrictions as of August 2026:
| Limit |
Current value |
| Maximum single file (upload, download, sync) |
250 GB |
| Recommended sync ceiling |
300,000 total items per account |
| Files copyable at once via the web interface |
2,500 |
| Items in a single shared folder |
50,000 |
| Storage per user |
1 TB on most business plans, more on eligible enterprise plans (plan comparison) |
Two of these bite harder than they look:
The 300,000-item sync guidance is the quiet one. A team that records meetings, trainings, and screen captures accumulates files fast, and sync performance degrades well before hard failure. Microsoft's own recommendation is to stay under 300,000 items for reliable performance, which a media-heavy department can reach in a couple of years.
The 250 GB file cap is generous for documents and fine for most video, but a multi-hour 4K recording, a courtroom exhibit, or raw surveillance export can approach it, and the deeper problem is not the cap. It is what OneDrive does with a large video after upload: nothing. No transcoding, no adaptive streaming renditions, no thumbnails at scale. The file sits there as a file.
The Governance Gaps
For business documents these gaps are tolerable. For sensitive or regulated content they are usually disqualifying:
Permissions are sharing-based, not role-based. OneDrive thinks in terms of "who has this link or membership," not roles with different rights. There is no native way to say viewers can watch but not download, contributors can upload but not share externally, and auditors can see activity but not content. Once a file is shared, granular control over what the recipient can do with it is thin.
Audit depth depends on add-ons. Basic sharing and access events are logged, but the file-level accountability that compliance teams actually need, a complete, tamper-evident history of who viewed, edited, downloaded, or shared an item, requires Microsoft Purview licensing and configuration, and even then it is built for documents, not for demonstrating a chain of custody over media.
And there is no chain of custody. A police department or a legal team whose files may end up scrutinized in court needs an unbroken custody record that makes the evidence defensible, and OneDrive cannot produce one. That is not really a criticism, since it was never designed for the job. It is the reason handling digital evidence in consumer-grade storage is a risk in itself.
Identity runs through Microsoft Entra ID. OneDrive authenticates through Microsoft Entra ID (the renamed Azure AD). Organizations standardized on Okta, Ping, or another identity provider can federate those into Entra, but there is no direct integration path, and every non-Microsoft identity setup adds a layer.
The Media Blind Spots
This is where organizations most often outgrow OneDrive without realizing it, because the limits stay invisible until the library is large.
Playback is a file preview, not streaming. There is no adaptive bitrate, so viewers on weak connections buffer instead of dropping to a lower quality, and a hundred employees opening the same all-hands recording pull a hundred full-bandwidth streams across the network. Nothing like an enterprise content delivery layer exists to absorb that.
Video is also opaque to search. Nothing transcribes it, nothing captions it, and nothing indexes what was said or shown on screen. A library of a thousand recorded meetings ends up searchable by filename alone, and nobody names files well.
Metadata has the same problem. OneDrive gives you no supported way to attach a case number or a retention class to a file, so categorization collapses into folder trees, which stop scaling right around the time the sync ceiling approaches. Anything that involves actually working with media, whether trimming a recording or adding captions for accessibility, means exporting to another tool and re-uploading the result.
When OneDrive Is the Right Answer
To be fair to the tool: if your content is documents and ordinary office files, your sharing is mostly internal, your compliance needs are covered by Microsoft 365's standard controls, and video is an occasional clip rather than a library, OneDrive is not a limitation, it is the correct default, already paid for in your Microsoft 365 subscription. The evaluation only changes when media, scale, or regulation enters the picture. If what you actually need is more storage rather than more capability, our comparison of video cloud storage options covers that decision separately.
When You Need a System, Not Storage
Every gap above follows the same pattern. OneDrive stores files, and at some point an organization needs to manage content, which is a different job with different machinery. Systems built for that job, VIDIZMO's EnterpriseTube among them, answer the specific gaps in this article rather than adding storage: role-based permissions and audit logs where OneDrive has sharing links, transcoding and a native delivery network where OneDrive has file previews, transcription and semantic search where OneDrive has filenames, and custom metadata where OneDrive has folder trees. They also run wherever the content is allowed to live, in the cloud or entirely behind your firewall, and plug into whatever identity provider you already use, Okta and other SAML providers included.
Secure external sharing, the use case that most often pushes teams past OneDrive's link model, is a topic of its own. Our guide to sharing videos securely online walks through the options and their trade-offs.
A practical test for your own situation is to count how many of your OneDrive complaints are about storing files versus managing content. If the second list is longer, you have outgrown the tool rather than misused it, and it is worth seeing a purpose-built platform against your own library before the workarounds calcify.
