SharePoint vs OneDrive: when to use which

I once watched a project manager spend forty-five minutes searching for a contract her team had been editing for weeks. She knew it existed. Three people had her in the editing chain. But it was nowhere. Eventually we found it: buried in someone else's personal OneDrive, under a folder called "stuff to sort."

That person had left the company two months earlier.

This is the OneDrive vs SharePoint decision, and getting it wrong creates expensive little disasters like that one. Brand-new Microsoft 365 users get tripped up by it. Ten-year veterans still get tripped up by it. Microsoft hasn't exactly made it obvious where things should live.

The 10-second rule that solves 90% of cases

Before any of the nuance — and there is some — there's one question that resolves the vast majority of "where do I save this?" moments:

If I left this company tomorrow, should this file leave with me?

If yes, it goes in OneDrive. OneDrive is your personal locker. Files are private to you by default. You decide who sees what, when, and for how long.

If no, it goes in SharePoint. SharePoint is the team's filing cabinet. Files belong to the team. Everyone in the team can usually see them out of the gate.

A draft of your performance self-review? OneDrive. The team's project plan? SharePoint. A photo you took of a whiteboard during your own brainstorm goes in OneDrive (and then you share it out if it's useful). The signed client contract goes in SharePoint, in the right project library, where it lives on after any one person leaves.

That's it. That's the whole rule.

Some real examples

File	Where it belongs	Why
Your draft expense claim	OneDrive	It's your personal record
Photo of the office whiteboard	OneDrive then share	Started as your capture
The team's project plan	SharePoint	Everyone needs ongoing access
Last year's marketing assets	SharePoint	Institutional history
Your performance review notes	OneDrive	Personal and confidential
The shared client deck	SharePoint	Multiple co-authors
A contract template the legal team owns	SharePoint	Owned by a function, not a person
Notes from a 1:1 with your manager	OneDrive	Personal record
The team holiday calendar	SharePoint	Accessed by everyone
A scratch Excel sheet you're prototyping with	OneDrive (then move it later if useful)	Starts personal; promote to SharePoint when others need it

Why people get so confused

Because in Microsoft 365, Teams channels are backed by SharePoint. Every channel you create in Teams quietly creates a folder inside a SharePoint document library. So when you drag a file into a Teams channel's Files tab, you're actually dropping it on SharePoint, even though nothing in the experience tells you that.

It's a feature, not a bug. The same file is reachable from three different places:

The Files tab in the Teams channel
The matching Documents library on the SharePoint site behind that team
A synced folder in File Explorer if you've clicked Sync

This is also why renaming a Team or its channels can leave files in slightly weird-looking SharePoint folder paths. The folders keep their original channel names. Microsoft has known about this for years. They haven't fixed it. I've stopped expecting them to.

What about chat files?

When you attach a file in a private Teams chat (not a channel — a chat), it does not go to SharePoint. It goes to your OneDrive, into a folder called Microsoft Teams Chat Files, and the file is shared with whoever's in the chat.

Which is one more reason to keep an eye on your OneDrive sharing tab. A year of casual file drops in Teams chat can quietly create dozens of active sharing links you've forgotten exist. I audited my own last spring and found 87 of them. Some going back to people who'd left two jobs ago.

Sharing: the quiet difference that bites people

This is the most important practical difference between the two services. It's also the one most likely to ruin your week:

In OneDrive, every file is private until you share it. You explicitly grant access.
In SharePoint team sites, every file is visible to the whole team by default. Access is inherited from team membership.

This is the single biggest source of the "wait, who exactly can see that?" panic in Microsoft 365. If you put something sensitive into a team's SharePoint, assume the whole team can see it. If your team has 200 people, that's 200 people. Always check the Members of the SharePoint site or Microsoft 365 Group before you save anything sensitive there.

You can break inheritance and set unique permissions on a single folder or file in SharePoint. Yes. But doing that creates a permissions maintenance nightmare over time, and a year from now nobody will remember why one folder is locked down. As a rule of thumb: if a file needs special permissions, OneDrive is usually the cleaner home.

Storage limits — they're wildly different

The two services have very different storage budgets, and this matters when you're hitting quota:

Plan	OneDrive per user	SharePoint per tenant
Microsoft 365 Business Basic / Standard	1 TB	1 TB + 10 GB per licensed user
Microsoft 365 E3 / E5	1 TB (up to 5 TB on request)	1 TB + 10 GB per licensed user
Microsoft 365 Personal	1 TB	n/a
Microsoft 365 Family	1 TB per person, up to 6	n/a

A single SharePoint site library has a cap of 25 TB. Individual files can be up to 250 GB, which is huge — bigger than most video files anyone's actually editing. If you're bumping against your OneDrive quota, the answer is often to move project files into a SharePoint site, where storage is pooled across the whole tenant.

Sync them both into File Explorer

Both OneDrive and SharePoint libraries can be added to File Explorer through the same OneDrive client. For a SharePoint library:

In your browser, go to the SharePoint document library you want.
Click Sync at the top of the file list.
Approve the prompt to open the OneDrive client.
The library appears in File Explorer under your company's name. You'll see a small building icon next to it, distinct from the cloud icon for personal OneDrive.

You can also click Add shortcut to OneDrive instead. This adds the SharePoint folder under your OneDrive, which is handy because the shortcut travels with you to other devices automatically. Sync, by contrast, has to be set up on each machine, which is annoying when you get a new laptop.

I tend to prefer Add shortcut for everyday team libraries. Sync for the one or two libraries I'm in heavily every day.

Versioning, retention, and recovery

Both services keep version history, both have a Recycle Bin, both inherit retention policies set by tenant admins. A few things worth knowing:

SharePoint by default keeps the last 500 versions of a file. OneDrive keeps versions too, though the default is lower in some plans.
Deleted files go to the user Recycle Bin for 30 days. Then to the site collection Recycle Bin for another 60 days. Then they're really gone.
If you accidentally delete a SharePoint folder full of files, don't panic. Restore from the Recycle Bin first. Restore from version history if you need an older state.
OneDrive has a Restore your OneDrive feature that can roll the entire account back to a point in time within the last 30 days. This is the right answer if you get hit by ransomware that encrypted everything. Bookmark that feature mentally — you'll be glad you knew about it the day you need it.

Why this is even a thing

The historical reason for the OneDrive vs SharePoint split is that they grew up apart. SharePoint started in 2001 as on-premises team collaboration software for enterprises. Lots of XML, lots of headaches. OneDrive (originally SkyDrive) started as a consumer file-sync product. Different team, different code, different audience.

Microsoft eventually built OneDrive for Business on top of the SharePoint engine, which is why they look so similar under the hood — they kind of are the same thing now. Same storage technology. Different sharing and ownership defaults bolted on top. The split persists because changing it would break too much existing behavior.

The classic mistakes I see in audits

Burying team work in personal OneDrive. That contract I mentioned at the top? Classic example. If you save the team's only copy of a critical document in your OneDrive, it disappears when you leave. Move shared work to SharePoint early.
Setting OneDrive folders to share with "Everyone in your organization." Functionally similar to SharePoint, except no one expects to find files there. Use SharePoint for org-wide content.
Mixing personal Microsoft Account OneDrive with work OneDrive. Completely separate services. The sync client treats them as separate cloud icons. Make sure you're saving into the right one — I've watched people send a personal screenshot to a work OneDrive sharing link and only realize later.
Renaming SharePoint folders that came from Teams channels. This confuses the Teams Files tab. If you need to rename a channel folder, do it in Teams.

Closing thought

OneDrive is for your stuff. SharePoint, often surfaced through a Teams channel, is for the team's stuff. When you can't decide, ask the leaving-tomorrow question: if the file should go with you, OneDrive. If it should stay with the team, SharePoint.

Get that one habit right and you'll avoid most of the mess I see when I do these audits. And nobody will spend forty-five minutes hunting for a contract that's hiding inside a former colleague's personal cloud.