Skip ahead to the main page
Partner Huddle
Pages

3 Teams chat limits before sending client files

Partner Huddle Editorial Team · Published · 13 min read

Microsoft Teams caps a chat message at roughly 100 KB of content, caps attachments on a single message, and allows only 200 members in a group chat. Beyond those limits, client files sent in chat carry phishing risk and belong in your firm's written safeguards plan. Check the official limits page before your next client request, and keep a written record of how your team handles sensitive files in chat.

  • Message size limit — A Teams chat message carries an approximate 100 KB cap covering message text, image links, mentions, connectors, and reactions; base64 encoded images sit outside that cap.
  • Attachment limit — Exceeding the attachment count on a single message shows an error message, so split multi-file requests into separate messages.
  • Phishing risk — Client files in chat carry links and attachments that can steal passwords, download keystroke loggers, or hand control of your computer to a thief, so verify the sender on a call before opening anything.
  • Safeguards duty — The FTC's Safeguards Rule page points businesses to legal resources and guidance on their responsibilities, and your firm's chat handling belongs inside its written safeguards plan.

Why these three limits matter before you hit send

Your team uses Teams chat every day. Clients send tax documents through it. Staff request W-2s, ID cards, and bank statements in thread replies. It feels instant and informal.

Three limits surface most often in a small accounting firm. The first is message size. The second is the attachment count on a single message. The third is how many people a group chat can hold. Each one fails in a visible way at the worst moment, usually with a client waiting.

Microsoft publishes these numbers directly. The limits page at Microsoft Learn, "Limits and specifications for Microsoft Teams" is the reference you should bookmark.

A second layer sits underneath the limits. Client files carry tax and financial data. Sending them through a chat window exposes them to phishing and identity theft in ways a normal document exchange does not. The IRS publishes guidance covering the phishing and malware risk behind that exposure.

Read the three limits first. Then read the risk section and the checklist. You should finish knowing which message content counts toward the cap, when to move a request out of chat, and where your firm's own safeguards plan sits.


Key takeaways

  • Message size limit — A Teams chat message carries an approximate 100 KB cap covering the message text, image links, mentions, connectors, and reactions. Base64 encoded images are outside that cap.
  • Attachment limit — If you exceed the attachment count on a message, Teams shows an error. Plan multi-file requests as separate messages.
  • Group chat cap — A group chat takes only 200 members at once.
  • Phishing surface — Client files in chat come with links and attachments. The IRS warns that a phishing message can steal passwords, download keystroke loggers, or hand control of your computer to a thief.
  • Safeguards duty — The FTC's Safeguards Rule page directs businesses to legal resources and guidance on their responsibilities under the law. Read the rule's business guidance before you set a chat policy.
  • Open question — The sources reviewed here do not address oversized client files; ask Microsoft support or your IT provider. Ask Microsoft support or your IT provider for the right path.

Limit one: the message size cap

Teams puts an approximate 100 KB limit on a single chat message. That number is not a hard file size. It counts the message content itself: the text, the image links, the @-mentions, the connectors, and the reactions.

Read that carefully. A short message with a pasted data table and three mentions can brush against the cap before you attach anything. A long meeting recap with inline images and a dozen mentions can fail on its own, without a client file in sight.

There is one carve-out. Base64 encoded images sit outside the cap. The same page notes that "100 KB size limitation doesn't include base64 encoded image." That carve-out helps for small inline pictures. It does not help for the PDF of a client's bank statement.

What this means at your desk:

  • A one-page summary note in chat will almost never hit the cap.
  • A long block of pasted text plus mentions plus links can brush against the cap before you attach anything.
  • A client file attached on top of a long message is the failure case to watch.

The practical move is simple. Keep the chat message short. Move the file to an attachment or a shared location, and keep the message text to a few lines. When the message is a review note with citations and links, check the size before you send.

Teams shows the failure directly. The limit is approximate and is documented on the Microsoft Learn page. That is the safe failure. The unsafe failure is a message that sends fine today and fails next quarter when your standard wording grows.

A note on where the cap applies. This post is about chat. Channels carry their own numbers on the same Microsoft Learn page. Your firm's chat policy should name chat limits only, so staff do not mix them with channel rules.


Limit two: attachments on a single message

The second limit is the attachment count on one message. Microsoft's page states it plainly: "If the number of attachments exceeds this limit, you see an error message." The error is visible.

Accounting work hits this often. A single client request pulls in a driver's license photo, a prior-year return, a bank statement PDF, and a signed engagement letter. Four files.

Improvisation is the risk. A blocked send leads a hurried team member to zip the files, upload to a personal drive, and paste the link in chat. That link is now outside your firm's controls, and outside your record of who saw the file.

Plan around the cap with three habits:

  • Split the request. Send the cover message first. Follow with the files in a second message, under the cap.
  • Name the files. Give each attachment a clear client-safe name. A blocked send plus a confusing name is a double failure.
  • Record the send. Keep a note of which client, which files, and which date went through chat.

A message already carrying mentions and links has less headroom for files. Treat them as one budget, not two.

When they hit the error, they will look for another path. Some will use a public file-sharing link. That is the moment to give them a better option in writing, before they need it.

What the IRS warns about in chat

Client files travel with links and messages. That is the phishing surface. The IRS describes how a phishing message works: "Has an urgent message to bait you into opening a link or attachment." Urgency is the tell. A "final notice" or "documents expired" line in a Teams message is a reason to stop, not a reason to click.

The same IRS page for tax professionals explains the damage behind that click: "This allows the thief to steal passwords or download malware that tracks keystrokes or gives the thief control of your computer." Password theft, keystroke logging, and remote control are the three outcomes. All three start with one open.

Your firm's rule should be direct. Never open an attachment or link in Teams from a sender you do not recognize, even if it arrives inside an active client thread. Confirm out of band. Call the client on the number you already have. Then open the file.


Here is a compact comparison of the three chat limits as published:

Limit in Teams chatWhat it coversWhat you see when you hit it
Approx. 100 KB in one message Message text, image links, mentions, connectors, reactions; base64 images excludedApproximate limit; see Microsoft Learn
Attachment count in one message Total attachments on one messageError message
200 members in a group chatPeople added at one timeCannot add more

Limit three: the 200-member group chat

The third limit is people, not bytes. A group chat holds only 200 members at once. The limits page states: "Only 200 members can be added to a group chat at the same time."

A working group chat may never reach 200 members. The limit matters in two specific places.

First, seasonal hiring. A firm that adds seasonal preparers, reviewers, and client-service staff into one coordination chat can approach the cap during peak. The add fails at 200, and someone is left out of a thread that carries client file requests.

Second, cross-firm threads. A chat that pulls in your firm, the client's controller, and an outside bookkeeper grows fast. When it hits 200, the natural fix is a second chat. Two chats means two records, two sets of file links, and two places to check when a client asks what happened.

The clean fix is to move the work to a channel inside a team. Channels are built for larger membership. Chat is built for small, fast, private threads. Matching the tool to the size of the group keeps your file trail in one place.

A related note on privacy. A group chat with many members sees every file posted to it. When the thread includes people who should not see a specific client file, the limit is a signal to split the conversation, not to squeeze one more person in.


The risk layer: client files in chat are a phishing target

Limits are visible failures. The risk layer is invisible until it is expensive. Every client file request in Teams chat is a message with links and attachments. That is exactly what a phishing campaign targets.

The IRS page for tax professionals sets out how a phishing message behaves. It carries urgency, and it asks you to open a link or an attachment. The goal is credential theft or malware. In a firm that handles taxpayer data, the damage runs past one workstation.

Three controls work in chat:

  • Verify the sender. Confirm identity on a call, on a number you already hold. Never on a number inside the message.
  • Delay the open. Wait until you have confirmed. Urgency in the message is the reason to wait longer, not shorter.
  • Report the attempt. Move the message to your firm's report path so the next person does not open it.

A fourth control sits above the others. Your firm should have a written policy on how client files move through chat: what can be attached, what must go through a secure exchange, who confirms the sender, and where the record lives. Without that policy, every blocked send becomes an individual decision made under time pressure.

The FTC page quoted above covers general business responsibilities for firms. The FTC Safeguards Rule: What Your Business Needs to Know page points businesses to "Find legal resources and guidance to understand your business responsibilities and comply with the law." Read that page with your firm's existing safeguards plan open beside it. Chat behavior belongs in the plan, not beside it.


A worked case: a four-file request that fails mid-send

A small firm requests a full onboarding packet from a new client: prior-year return, bank statement, ID photo, and a signed engagement letter. The operations lead builds one chat message. It carries a short cover note, three @-mentions for the reviewing staff, and four attachments.

Two things go wrong. If the attachment count on a single message goes above the cap, and the message content itself sits close to the approximate 100 KB line because of the mentions and links in the cover note, Teams shows an error message. Teams returns an error. Teams shows an error message. Nothing reaches the client.

The lead, now behind on an onboarding date, considers the fastest fixes. Zip the packet and upload to a personal drive. Paste a public link in the thread. Split the files across three messages with no cover note. Each option moves the file outside the firm's record, or strips the context a reviewer needs later.

The fix that works is the boring one. Send the cover note first, plain text, naming the four files and the due date. Send the four attachments in a follow-up message, split if the cap requires it. Ask the client to confirm each file by name. Log the request and the send in your onboarding tracker.

This case is not exotic. It is a Tuesday. The reason to write the habit down is that the failure arrives under deadline, and deadline is when judgment slips.


Setting a chat file policy your team will follow

A policy that staff ignore is worse than no policy. It creates a record of a rule you do not enforce. Keep the policy short enough to fit on one page, and specific enough to answer a real question.

The five questions your policy should answer:

  • What can be attached in chat? Name the file types your firm allows. Name the ones that must go through a secure exchange instead.
  • How many files in one message? Set a working number below the published cap so staff have headroom for mentions and links.
  • Who confirms the sender? Write the out-of-band step. A call to a known number. Never a reply in the same thread.
  • Where does the record live? One tracker, one field for client, files, date, and sender.
  • What happens on a blocked send? A named path, not a personal workaround.

Roll the policy out with one live exercise. Take a real client request, walk it through the policy, and note where the published limits bite. Staff learn a limit they have hit, not a limit they have read.

Review the policy when your examples change. A longer cover note, more mentions, or a new link format all consume message headroom. Check the official limits page for current values. Your usage moves.


What to check before your next client request

Run this list before you send anything sensitive through Teams chat. It takes a minute and it catches the failures that cost an afternoon.

  1. Confirm the recipient. Right person, right thread, right firm.
  2. Trim the message. Short cover note. Move long recaps to a document.
  3. Count the files. Split if you are near the attachment cap.
  4. Check the size. Remember the message itself counts toward the approximate 100 KB line.
  5. Watch the group size. Move to a channel if the group is near 200.
  6. Verify inbound files. Call before you open any link or attachment from a client thread.
  7. Log the send. Client, files, date, sender. One tracker.

If any line fails, stop. A blocked send is a two-minute fix. A file sent to the wrong thread, or a link opened from a phishing message, is not.


Related guides: Trello and Teams limits for client job tracking: 6 checks · Client folder move: 5 Microsoft storage limits to check · Rent records: 3 essentials for landlord client files.

FAQ

What happens when a client's file is larger than the chat allows?
The sources reviewed here do not cover oversized client files; ask Microsoft support or your IT provider before you suggest a workaround to a client. Ask Microsoft support or your IT provider before you suggest a workaround to a client. A public link is not the answer.

Does the 100 KB cap count a file I attach, or only the message text?
The cap counts the message content: text, image links, mentions, connectors, and reactions. Attachments carry their own separate count limit. Base64 encoded images sit outside the message cap.

Our seasonal team needs a coordination chat with more than 200 people. What do we do?
Move the coordination work into a channel inside a team. The 200-member cap applies to a group chat, where people are added at one time. A channel carries the larger membership and keeps the file trail in one place.

Who in our firm should own the chat file policy?
The operations lead drafts it. The person who owns your safeguards plan reviews it, since your firm's own policy choice puts chat handling inside the plan. Both signatures belong on the one-page policy.

A client sends us a "final notice" link in an active Teams thread. Do we open it?
No. Confirm the sender on a call first. The IRS describes exactly this pattern: urgency baiting you to open a link or attachment. Confirm out of band, then decide.

Sources