OneDrive’s limits aren’t fixed the way a lot of older guides present them — several of the numbers that get repeated around the web (100 GB file size, 25-version history) are out of date. This post covers the current, verified limits, and which ones are actually likely to bite in practice versus which are edge cases most people never hit.
In this post: Storage and file size limits · Sync limits: file count and path length · Files On-Demand and offline access · Version history and concurrent editing · Sharing limitations · Which of these actually matter? · Related reading
Storage and file size limits
Worth correcting directly, since it’s one of the most-repeated outdated numbers: the maximum individual file size used to be 100 GB for personal accounts, but Microsoft raised it to 250 GB across the board — personal and business plans alike now share the same per-file ceiling. Storage quota is a separate number from file size and depends entirely on the plan: 5 GB free with any Microsoft account, 1 TB with Microsoft 365 Personal, up to 6 TB shared across Microsoft 365 Family, and business plans defaulting to 1 TB per user with admins able to raise it toward 5 TB.
Sync limits: file count and path length
The “300,000 files” number that shows up everywhere is also worth a correction: Microsoft doesn’t currently document a hard cap on total files stored in OneDrive — 300,000 is a recommended ceiling for reliable sync performance, not a threshold that gets an account flagged or blocked. A separate, harder limit of 2,500 items applies specifically to large copy or sync operations, particularly web-based ones — that’s the number more likely to actually interrupt a bulk operation in practice.
Path length is a real, harder constraint: the full file path can’t exceed 400 characters, and no individual file or folder name can exceed 255 characters. This is the limit that actually surfaces as a visible sync error — a deeply nested folder structure with long, descriptive names is the most common way to hit it, especially migrating content over from an on-premises file share that never enforced any path-length discipline.
The 100 GB file size limit and the “300,000 files” hard cap are both outdated — the real numbers are 250 GB per file, and no documented hard limit on total file count.
Files On-Demand and offline access
Files On-Demand is what makes the storage-capacity numbers above mostly theoretical for day-to-day use — files show up in File Explorer without actually being downloaded, so a OneDrive with far more content than the device’s local disk can still browse and open normally. New files sync as online-only by default and take up no local space until opened. The limitation that trips people up isn’t the feature itself, it’s what happens without an internet connection: an online-only file can’t be opened offline at all, so a laptop about to go somewhere without reliable connectivity needs the relevant files explicitly marked “Always keep on this device” beforehand, not assumed to already be available.
Worth knowing as a related gotcha: Windows Storage Sense can silently dehydrate local files back to online-only to free up disk space, even ones a user previously marked as always-available. In a Known Folder Move environment especially, that means offline access someone was relying on can quietly disappear in the background — worth checking explicitly before travel rather than assuming a file marked offline once stays that way indefinitely.
Version history and concurrent editing
Version history is another number that’s often stated vaguely as “25 to unlimited depending on plan” — the current default is a flat 500 versions per file, applied the same way to both SharePoint document libraries and OneDrive. Once a file passes 500 versions, the oldest one drops off to make room for the newest, rather than versions expiring on any kind of schedule. That default only applies to new libraries going forward, not retroactively to existing ones — for the fuller picture on how that gets managed and adjusted at scale, see Managing Document Versioning in SharePoint.
Concurrent editing works as advertised for most real-world cases — multiple people in a document at once, changes merging live — but it isn’t magic. Two people editing the exact same sentence or cell at the same moment is the case where OneDrive can’t always merge automatically, and one edit ends up needing manual reconciliation. Rare in practice, but worth knowing it’s a real edge case and not a bug when it happens.
Sharing limitations
A shared file inherits the same 250 GB size ceiling as any other file, so that’s not a separate limit to plan around. The real limitation is on control, not size: OneDrive’s sharing permissions are simpler by design than SharePoint’s — link-based sharing with a handful of scope options (specific people, org-wide, anyone with the link), rather than the item-level permission breaking, custom groups, and granular access control SharePoint document libraries support. For a one-off file shared with a couple of external people, that simplicity is a feature. For something that needs different access for different groups of people long-term, that’s usually a sign the content belongs in a SharePoint library instead of a personal OneDrive.
Which of these actually matter?
- Path length is the one that actually surfaces as a routine sync error — worth checking before a large migration, not after files start failing to sync.
- File size and total file count rarely matter for typical office documents — they become relevant for video libraries, CAD files, or bulk data migrations, not day-to-day document work.
- Sharing control is the one worth planning around structurally — if content needs granular, long-term access control, that’s a reason to put it in SharePoint rather than a personal OneDrive from the start, not a limitation to work around later.
Microsoft updates these numbers periodically, so treat any specific figure — including the ones above — as accurate as of when it was last verified, not as permanent.
Related reading
- OneDrive vs. Google Drive — how these limits stack up against the alternative.
- Managing Document Versioning in SharePoint — the version-history default and Intelligent Versioning in depth.
Most of these limits are edge cases most people never hit — the practical ones worth actually planning around are path length before a migration, and sharing control before deciding whether content belongs in OneDrive or SharePoint in the first place.
App Catalog Authentication Automation Backup Compliance Content Type CSS Flows Google Javascript Limitations List Metadata MFA Microsoft Node NodeJs O365 OneDrive Permissions PnP PnPJS Policy PowerApps Power Automate PowerAutomate PowerPlatform PowerShell React ReactJs Rest API Rest Endpoint Security Send an HTTP Request to SharePoint SharePoint SharePoint List SharePoint Modern SharePoint Online SPFX SPO Sync Tags Teams Termstore Versioning