SharePoint vs Teams Files — which one is actually storing your file?

I lost a client file in 2022. Not really lost — but lost enough that I sweated for about twenty minutes before I found it. A team had been reorganized in Teams. Someone renamed a channel. The Files tab went empty. The client called me. I had no idea where her training videos went.

They were in SharePoint the whole time. Of course they were. Teams files always are.

But Microsoft has done such a good job hiding the SharePoint layer that even people who use Teams every day don't know it exists. And when something goes weird — a file deletes, a link breaks, a folder vanishes — they look in Teams and panic. The actual fix is one layer down.

Let me draw the map.

Every team has a SharePoint site behind it

When you create a team in Teams — let's call it "Marketing 2026" — Microsoft creates more than just a Teams workspace. It creates:

A Microsoft 365 Group (the membership list)
A SharePoint team site (where files live)
An Outlook group mailbox (most people ignore this)
A Planner plan (most people also ignore this)
A OneNote notebook
A Stream video library tied to the SharePoint site

The Teams app stitches all of this together with tabs and pretends it's one thing. But it's six things wearing a Teams costume.

The one that matters for files is the SharePoint site. It has a URL like https://yourcompany.sharepoint.com/sites/Marketing2026. Inside it is a Document Library called "Documents" (sometimes shown as "Shared Documents" — the internal name is different from the display name, classic Microsoft).

That Documents library is what the Files tab in Teams shows you.

Files tab equals SharePoint Documents library

Open Teams. Pick your team. Click the Files tab at the top of the General channel. You see folders and files. That view? It's a window into the Documents library on the SharePoint site. It's not a separate copy. There's only one copy.

Edit a file in Teams — you're editing the SharePoint file. Upload a file in Teams — you're uploading to SharePoint. Delete a file in Teams — you're deleting it from SharePoint.

Once you internalize this, things start making sense. Teams isn't a file storage system. It's a chat-and-collaboration UI on top of SharePoint storage.

Channels are folders

This is where it gets visually weird. Each channel in your team — General, Marketing Updates, Campaign Planning, whatever — corresponds to a folder inside that Documents library. Not a separate library. A folder.

So if your Marketing 2026 site has a Documents library, inside it you'll see folders called "General" and "Marketing Updates" and "Campaign Planning." When you click the Files tab in the Marketing Updates channel, Teams just opens that specific folder.

Rename a channel? The folder gets renamed. Delete a channel? The folder hangs around in SharePoint for retention but the Teams view loses access.

This is what bit me back in 2022. Someone had archived the channel. The folder was still in SharePoint, files intact. But in Teams, the channel was gone, so the Files tab showed nothing. Five minutes in the SharePoint UI and the videos were sitting right there.

Private channels are different

Here's the curveball. Private channels DO get their own SharePoint site. Not just a folder — a whole separate site, with its own URL, its own permissions, its own everything.

So if your Marketing 2026 team has a private channel called "Exec Strategy," there's a second SharePoint site at https://yourcompany.sharepoint.com/sites/Marketing2026-ExecStrategy. Files in that channel live in a totally separate place from files in the public channels.

This matters for two reasons. First, if you're an admin trying to find a file, looking in the main team site won't show you private channel files. Second, sharing links from a private channel won't be accessible to people in the main team unless they're also in the private channel — different site, different permissions.

Shared channels do something similar but with different plumbing. I'll skip those for today because they're a whole separate mess.

The General folder is special

Every team starts with a General channel. You can't delete it. The matching folder in SharePoint is called "General" and behaves like the team's default dumping ground.

But here's the thing. The Documents library has a root level too — files sitting at the top of Documents, NOT inside any channel folder. These files don't show up in any channel's Files tab. They're invisible from Teams.

If you upload directly to SharePoint at the library root, Teams users won't see those files unless they open SharePoint directly. Same library. Just a level up from where Teams is looking.

I've watched this trip up consultants who upload deliverables to "the team's SharePoint" by dragging into the root, then wonder why the team can't find them. Move them into a channel folder and they appear.

Open in SharePoint

This is the most useful menu item in Teams that nobody clicks. In any Files tab, there's a button or three-dot menu called "Open in SharePoint." Click it.

A browser tab opens to the SharePoint site. Same files, same folders, but in the full SharePoint interface — which is significantly more powerful than the Teams Files tab. You get version history with previews. You get column views. You get sort and filter that actually work. You get the recycle bin. You get sharing controls with expiration dates and password protection.

For anything beyond basic upload-and-open, I work in SharePoint and let Teams be the chat layer. The Teams Files UI is a stripped-down version designed to keep people from leaving Teams. If you don't mind leaving, you get a better tool.

Moving files in SharePoint can break Teams links

When you share a file in a Teams chat, the link points to the file's specific location at that moment. If you then go into SharePoint and move the file to a different folder, the link in the old chat will sometimes break.

SharePoint tries to preserve sharing links via redirect. Sometimes it works. Sometimes it doesn't. The longer the link has been around and the more times the file has moved, the more likely it breaks.

If a colleague messages you a Teams link and you click it and get "This link is not valid" — the file probably got moved. Open SharePoint, search for the filename, and it's almost always still there. Just not where the link was pointing.

I'd avoid moving files that have been heavily shared. Rename them in place if you need to, but don't drag them between folders. Or if you must, send a follow-up message in the channel with the new link.

1:1 chat files live in YOUR OneDrive

This one nobody knows. When you send a file in a one-on-one Teams chat — or in a small group chat that isn't a team — the file isn't stored on a team's SharePoint site, because there is no team. There's no SharePoint site behind a chat.

Instead, the file gets uploaded to YOUR personal OneDrive, into a folder called "Microsoft Teams Chat Files." It's automatically shared with the people in the chat.

This means: if you delete the file from your OneDrive, it disappears from the chat too. If you leave the company and your OneDrive gets archived, the chat files become inaccessible to the recipients. If your OneDrive storage fills up, you can't send files in chats anymore.

I've cleaned out a few thousand files from clients' Microsoft Teams Chat Files folders over the years. They accumulate fast and most are screenshots and PDFs nobody needed to keep. Just be careful — deleting them retroactively kills the chat shares.

The recycle bin chain

When you delete a file from a Teams Files tab, it doesn't go to your computer's Recycle Bin. It goes to the SharePoint site's recycle bin. Where it lives for 93 days by default.

If you "empty" that recycle bin, files don't actually leave — they go to a SECOND-stage recycle bin, accessible only to site admins. They sit there for the remainder of the 93-day window.

After 93 days total, gone for real.

So when a client tells me "I deleted a Teams file," I tell them this:

Look in Teams Files tab — if it's there, undelete done
Open in SharePoint, then click Recycle bin in the left nav
If not there, click "Second-stage recycle bin" at the bottom — needs site admin rights
If you're not an admin, you need to ask one. Tell them the filename and approximate date.

Most "deleted file" panics resolve at step 2. The site recycle bin is the unsung hero of SharePoint. I've recovered files from it months after deletion.

The thing about the layered architecture — Teams on top of SharePoint on top of Microsoft 365 Groups — is that it's actually pretty elegant once you see it. Files have one home (SharePoint or OneDrive), and the various apps just present views into that home. The confusion isn't the architecture. The confusion is that Microsoft barely tells you the architecture exists. Once you can name the layers, you stop losing things.