Blog

Microsoft Teams File Size Limit in 2026: 250 GB, If You Know Where It Lives

By sto.care editorial9 min read

Microsoft Teams has the highest per-file upload limit of any mainstream chat app: 250 GB. That's 250 times Slack, 125 times Telegram Premium, 25,000 times Discord's free tier.

But “250 GB” isn't the whole story. Teams doesn't actually store files. It hands them to SharePoint or OneDrive, and which one depends on where you dropped the file. That detail matters, because it determines whose quota takes the hit, who can see it later, and whether the file survives when someone leaves the company.

Here's what's really going on under the hood.

What are Teams' actual file limits?

Where you uploadPer-file limitStored in
Channel post250 GBTeam's SharePoint site
1:1 or group chat250 GBSender's OneDrive
Meeting chat (channel meeting)250 GBChannel's SharePoint site
Meeting chat (private meeting)250 GBOrganizer's OneDrive
Meeting recording250 GBSame as meeting chat

The 250 GB cap is set at the SharePoint and OneDrive layer. Teams inherits it. For all practical purposes, Teams has no meaningful per-file limit. If it fits on a hard drive, it fits.

That's wildly different from Slack (1 GB), Discord (10 MB free), and even most business-oriented tools. But Teams pays for it with complexity: you can't understand your real limits without understanding SharePoint.

Why Teams doesn't actually store your files

When you drop a file into a Teams channel, Teams uploads it to a SharePoint site that was created automatically when the team was. The chat conversation just shows a link to the file. The file itself lives on SharePoint, in a document library called “Documents,” under a folder named after the channel.

When you drop a file into a 1:1 chat, Teams uploads it to your own OneDrive. Specifically into a folder called “Microsoft Teams Chat Files.” The recipient doesn't get a copy; they get a share link pointing at your OneDrive. If you delete the file there, the link in their chat breaks.

This is the part that catches people off guard. If an employee leaves the company and their account is deleted, every file they ever shared in 1:1 chats disappears. Including files shared with other current employees. Channel files survive because they live in the team's SharePoint, which belongs to the team, not the individual. Hence the common advice: share work files in channels, not chats.

How much storage you actually have

Storage in Teams depends on your Microsoft 365 plan, and the rules changed meaningfully when Microsoft reworked SharePoint storage pooling:

PlanPer-user OneDriveOrg-wide SharePoint pool
Teams (free)N/A5 GB total (shared)
Teams Essentials ($4/user/mo)10 GB per userNo separate SharePoint pool
M365 Business Basic ($6/user/mo)1 TB per user1 TB + 10 GB/license
M365 Business Standard ($12.50/user/mo)1 TB per user1 TB + 10 GB/license
M365 E3 / E5 (enterprise)1 TB per user (can request more)1 TB + 10 GB/license

The “1 TB + 10 GB per license” pool is the total space your organization's SharePoint sites share. A 50-person company on Business Basic gets 1 TB + 500 GB = 1.5 TB of SharePoint storage, divided across every team's channel files, every channel meeting recording, every document library.

That sounds like plenty. It isn't, if your team has been recording hour-long channel meetings for a couple years. One hour of Teams video at 1080p is roughly 500 MB to 1 GB. Five teams doing a daily standup for a year eats through 1 TB fast.

Why your Teams upload might still fail

Even with 250 GB of theoretical headroom, uploads fail for reasons that have nothing to do with file size:

  • Blocked file types. Tenants can block extensions like .exe, .iso, .js through SharePoint's blocked files list. Admin sets this; it can't be bypassed from the client.
  • Destination storage is full. Your personal OneDrive fills up separately from the team's SharePoint site. An upload to a chat fails when your OneDrive is full even if the team's SharePoint has terabytes free.
  • Illegal characters in the filename. SharePoint rejects #, %, &, *, {}, <>, trailing periods, and names over 400 characters. Rename the file and retry.
  • Upload interruption. Teams uses resumable uploads but fails hard if the connection drops for more than a few minutes. Large files over flaky networks need a wired connection.
  • External sharing disabled. If the tenant blocks external sharing, guest users can't download files even if the link looks fine.

How Teams compares to other chat platforms

PlatformPer-file limitStorage model
Microsoft Teams250 GBSharePoint/OneDrive backed
Slack (free)1 GB5 GB shared; files hidden after 90 days
Slack (Pro)1 GB10 GB per user
Discord (free)10 MBNo dedicated storage
Google Chat200 MBStored in sender's Drive
WhatsApp2 GBEphemeral (30-day server cache)

Teams has the highest per-file cap in the category, and the storage pool is generous on paid plans. Where it falls down is complexity . you need to know which plan you're on, which backend storage applies, and whether the tenant has layered on custom restrictions.

When it's easier to skip Teams entirely

Teams is great for files your team owns and will keep coming back to. Quarterly reports, design files, meeting recordings: put them in a channel.

Where Teams is awkward:

  • One-off transfers to external people. Clients, vendors, freelancers. You have to set up guest access or use the “anyone with the link” setting, which some tenants block entirely.
  • Files you don't want in company storage. Personal files, benefits documents, anything you'd rather not have indexed by the tenant.
  • Time-limited shares. Teams files stick around until someone deletes them. There's no “auto-expire in 7 days” option out of the box.
  • Sending to people outside the Microsoft ecosystem. External users without a Microsoft account keep hitting access walls.

For those cases, a dedicated transfer service is simpler than wrestling with SharePoint permissions. sto.care takes files up to 5 GB, produces a plain download link, and auto-deletes after 7 days. No Microsoft account needed on either end, and the file doesn't live in your tenant's storage.

ServiceFree sizeAccount needed?Link lasts
sto.care5 GBNo7 days
WeTransfer3 GBNo3 days (10/month cap)
SwissTransfer50 GBNoUp to 30 days

See our full comparison of 22 file sharing services for more options.

Frequently asked questions

What is Microsoft Teams' file size limit?

250 GB per file, across channels, chats, and meetings. The cap comes from SharePoint and OneDrive, which actually store the files.

Where are Teams files stored?

Channel files live in the team's SharePoint site. Chat files live in the sender's OneDrive. Meeting recordings follow the meeting type. Channel meetings go to SharePoint, private meetings go to the organizer's OneDrive.

How much storage do I get on Teams free?

Teams free is 5 GB total, shared across the chat. Teams Essentials is 10 GB per user. Microsoft 365 Business plans include 1 TB OneDrive per user plus a SharePoint pool of 1 TB + 10 GB per license.

Why does my upload fail when the file is small?

Usually a blocked extension, a full destination, or illegal characters in the filename. SharePoint rejects #, %,&, and others. Rename the file and retry before blaming the size.

Do chat files count against my OneDrive?

Yes. Files attached in 1:1 or group chats come out of the sender's OneDrive quota. Files attached in channels come out of the team's SharePoint site. Not your personal OneDrive.

Can external guests upload files?

Guests in a team can upload to channels if the tenant allows external sharing. Guests in chats can attach files to their own messages. Anonymous meeting participants can't upload by default.

How long are Teams files kept?

Indefinitely unless an admin configures a retention policy. Teams doesn't auto-delete files like Slack's free tier does.

How do I share files over 250 GB?

You can't, inside Teams. That's the SharePoint/OneDrive hard cap. For smaller files where you don't want company storage involved, a dedicated service like sto.care handles up to 5 GB free with auto-expiring links. We wrote a full comparison of alternatives.