Can't Share a File in a Teams Group Chat? Two Limits

Microsoft's troubleshooting article for this failure names 100 participants; a separate Microsoft page names 250. Both numbers are official, both are current, and they describe two different things. If you have been searching for why a file won't post in a big Teams chat and keep landing on conflicting figures, that is why.

Here is what each threshold is attached to, and which one applies to the chat you are staring at.

The 100-participant threshold: the message itself fails

Microsoft's page "Unable to share files in a large group chat or meeting chat" describes the symptom in one sentence:

"When you try to share files in a Microsoft Teams group chat or meeting chat that contains more than 100 participants, the message might not be sent successfully when you select Send."

Read that carefully, because the wording is precise in two ways. First, it is the message that might not be sent — the failure shows up at the moment you press Send, not as a rejected upload. Second, Microsoft writes "might not," not "will not." This is a conditional failure, which is exactly why some people in a 150-person chat post files all day and others cannot.

The same page gives the cause:

"This issue occurs if the default setting for file sharing is People currently in this chat. In this scenario, the type of link that's used for the shared files is Specific people. However, we don't recommend using this link when you want to share files with more than 100 users. When there are more than 100 participants in a chat, some participants might need to request permission to access the shared files."

So the mechanism is a sharing-link type, not a size cap. When the default is "People currently in this chat," Teams attaches a Specific people link, and Microsoft's own recommendation is not to use that link type above 100 users. The knock-on effect is the second half of that quote: some participants end up having to request permission to open the file.

The 250-participant threshold: permissions, not sending

The other number comes from a different Microsoft page, about recording and transcript storage:

"For large meetings, if a meeting has more than 250 participants, some participants don't automatically have file permissions. Excluded participants should ask the recording owner to add them to the shared list."

Nothing fails at Send here. The file — a meeting recording — exists and is stored, but a slice of the attendee list does not automatically get permission to it. Microsoft's stated remedy is explicit and worth quoting as-is: the excluded people should ask the recording owner to add them to the shared list.

The same page adds one more figure that is neither of the above:

"For optimal performance, the total number of users in a chat shouldn't exceed 1,000."

Treat these as three separate statements from two separate documents. Microsoft does not reconcile them anywhere we can cite, so do not collapse them into one rule.

What you can actually do about it

The cause Microsoft names is a sharing-link default, and that default is an administrative setting rather than something you flip while typing a message — for the current procedure, check the official documentation. For the 250-participant case, Microsoft gives the user-level answer directly: ask the file's owner to add the excluded people to the shared list.

What you can control is how heavy the thing you are posting is, and that matters because Teams gives two very different size figures. On the same official limits page, the "Messaging / Chat" table reads File size limitation 100 MB, while the "Storage" table lists File upload limit (per file) 250 GB identically across all six plan columns. Microsoft explains the backend but not the boundary between the two numbers:

"Because Teams runs on a SharePoint backend for file sharing, SharePoint limitations apply to the Files section within a Team."

Since the exact scope of each figure isn't spelled out in the official pages, plan against the smaller one. A meeting clip or screen recording that comfortably clears 100 MB is a file that nobody has to guess about.

That runs entirely in your browser tab — the video is read from disk, re-encoded locally, and handed back. Nothing is uploaded, which matters when the clip you are trying to post is an internal meeting. If you want the manual controls instead of a preset, compress video exposes the same pipeline.

Other reasons a file won't post

SharePoint or OneDrive isn't enabled for the tenant. This one is absolute, and Microsoft states it plainly: "If you don't have SharePoint enabled in your tenant, Microsoft Teams users can't always share files in teams. Users in private chat also can't share files because OneDrive for Business (which is tied to the SharePoint license) is required for that functionality." If chat file sharing is dead for everyone regardless of chat size, this is the first thing for an admin to check.

You attached too many files at once. The chat table caps attachments per message at 10, and the footnote says: "If the number of attachments exceeds this limit, you see an error message."

The filename contains a character OneDrive rejects. Because files land in OneDrive or SharePoint, their naming rules apply. The official list of disallowed characters is:

" * : < > ? / \ |

Microsoft adds that "Leading and trailing spaces in file or folder names also aren't allowed," that "Some organizations don't yet support # and % in names," and that these names are not allowed at all: .lock, CON, PRN, AUX, NUL, COM0 - COM9, LPT0 - LPT9, _vti_, desktop.ini, and any filename starting with ~$. Renaming the file costs ten seconds and rules this out.

You used the email-a-channel route instead. That path has its own numbers, and they are much tighter: message size 24 KB, 20 attachments, and "Size of each file attachment — Less than 10 MB." A video that is fine for chat will bounce here. See why a Teams recording is too large to email for that path specifically.

You are sharing outside the organization. Microsoft's guidance on recordings includes a blunt line: "External sharing isn't designed for the distribution of large files or a large number of files."

How to tell it worked

Post the file, then confirm from a second account in the chat that it opens without a permission request. The 100-participant problem shows up as a message that doesn't send; the permission variant shows up later, as colleagues asking for access. Both are checked by having someone else actually open the file, not by the file appearing in your own view.

FAQ

Why can't I share a file in a Teams group chat with 100+ people? Microsoft's troubleshooting page attributes it to the file-sharing default being "People currently in this chat," which produces a Specific people link. Microsoft does not recommend that link type for more than 100 users, and says the message might not be sent successfully when you select Send.

Is the limit 100 participants or 250? Both figures are official but belong to different pages and different symptoms. The 100 figure is about a message failing to send in a large group or meeting chat. The 250 figure is about large meetings, where some participants "don't automatically have file permissions" to the recording.

What is the file size limit for Teams chat? Microsoft's limits page lists 100 MB in the Chat table and 250 GB per file in the Storage table on the same page. The exact scope of each isn't stated, so plan against 100 MB.

Why do some people have to request permission to open the file? Because of the link type. With more than 100 participants in a chat, Microsoft says some participants might need to request permission to access shared files. For large meetings, the remedy given is to ask the recording owner to add you to the shared list.

Will compressing the video fix a permissions error? No — permissions and size are separate problems. Compressing helps only when size or the upload path is the issue. Everything runs locally in Clapr's tools, so an internal recording never leaves your machine.

Figures cited from Microsoft's official Teams documentation, checked 16 September 2026. More troubleshooting write-ups live in fixes.