Microsoft's own planning figure for a Teams meeting recording is 400 MB per hour. That one number explains most of this problem: a routine one-hour meeting produces a file that no ordinary mailbox will carry as an attachment, and a half-day workshop produces something several times worse.
Nothing is broken when your mail client refuses it. The file is simply large by design, and Microsoft's documentation says as much in more than one place — including a sentence where it admits that sharing outside your organisation was not built for this.
Where 400 MB an hour comes from
In its storage planning guidance for admins, Microsoft states it flatly: "The size of a one-hour recording is 400 MB." The sentence appears under Planning for storage, alongside advice to make sure you have enough room in OneDrive and SharePoint for recorded files.
Two things are worth noting about that figure. It is written as a statement, not a range — but the same page does not say which resolution, frame rate or bitrate it assumes, so treat it as a capacity-planning number rather than a technical spec. If you need the encoding details, check the official documentation; the pages covering recording storage describe the container only, and Microsoft documents the file as an .mp4 in the step that explains how to find a recording in a channel.
Long meetings don't give you one big file — they give you several
Teams enforces a ceiling on a single recording. From the limits and specifications page:
"Meeting recording maximum length 4 hours or 1.5 GB. When this limit is reached, the recording ends and automatically restarts."
Read the condition carefully: it is 4 hours or 1.5 GB, whichever arrives first. Combine that with the 400 MB per hour estimate and the arithmetic is unflattering — around three and three-quarter hours of recording reaches 1.5 GB, so on a long session the size ceiling usually trips before the time ceiling does.
The practical consequence is the part people mistake for a bug: your six-hour training session comes back as multiple files. That is documented behaviour. The recording "ends and automatically restarts," so you end up emailing a set of files rather than one, each of them potentially up to 1.5 GB. (The meeting itself can run far longer — Microsoft notes a time limit of 30 hours for meetings and events.)
Microsoft's own verdict on sending recordings out
This is the line that settles the argument, from the page on recording storage and permissions:
"External sharing isn't designed for the distribution of large files or a large number of files."
That appears in a note which also recommends "that the recipient is required to be a signed-in user when sharing Teams meeting recordings," and points you at the People in (Your Organization) option when you share the file. In other words, the sharing path Microsoft built is aimed at signed-in colleagues, not at pushing a multi-hundred-megabyte video to an outside address.
If the recipient is outside your tenant and the file has to travel as a file, the size has to come down first.
The fix: shrink the recording before it touches an attachment field
Compression is the only step that changes the number every one of these limits is measured against. A meeting recording is mostly a shared screen and a few talking heads — material that survives a much lower bitrate far better than an action video does.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab: the file is read from disk, re-encoded locally, and handed back. It is never uploaded to a server, which matters when the recording contains internal discussion you would rather not hand to a random web service. The compressor is also on the tools index with the rest of them.
If the only thing anyone needs is what was said, drop the picture entirely. Teams can record audio only in the first place — its help page lists the route as More actions → Record and transcribe → Start recording → More options, then Audio only from the Choose what to record menu, then Confirm. The documentation does not state what file type that produces, so check the official documentation if it matters to you. For a recording you already have, extracting the audio track does the same job in one pass.
Three official routes, three completely different numbers
The reason advice about Teams file sizes contradicts itself online is that the official limits live in different tables and are not the same number.
| Route | Documented limit | Where Microsoft publishes it |
|---|---|---|
| Attaching a file in a Teams chat | 100 MB | Limits and specifications, "Messaging → Chat" table, row File size limitation |
| Emailing a file into a channel | Less than 10 MB per attachment | Limits and specifications, "Emailing a channel" table |
| File upload on the SharePoint/OneDrive backend | 250 GB per file | Limits and specifications, Storage table (identical across all six plan columns) |
The middle row is the one almost nobody knows about, and it matters here because emailing a channel is exactly what people try when the recording is too big for regular mail. The same table caps a channel email at 20 attachments, a message size of 24 KB, and 50 inline images, with a throttling note: "The limit is 6 emails per 10 seconds per channel per user and 8 emails per 10 seconds per tenant per user." Using Microsoft's own 400 MB per hour estimate, under 10 MB is roughly a minute and a half of recording — so this route is closed for anything resembling a real meeting.
On the 100 MB versus 250 GB gap: both figures sit on the same page. Microsoft's explanation for the backend number is that "Because Teams runs on a SharePoint backend for file sharing, SharePoint limitations apply to the Files section within a Team." The page does not spell out the exact boundary between the two, so take each number with the table it appears in rather than assuming which one governs your upload.
Send a link instead — with two caveats
For colleagues inside your organisation, sharing the stored file beats attaching anything. Recordings for meetings and events save "to the organizer's OneDrive, even if the organizer didn't attend," in a folder named Recordings; channel meeting recordings go to the channel's SharePoint site under Documents/Recordings.
Two things can make that link disappoint the recipient. First, recordings expire: Microsoft says "Meeting recordings and transcripts have a default expiration time of 120 days," subject to admin settings, and clarifies that "Watching the recording won't affect the expiration date." A compressed copy on someone's disk has no such clock. Second, captions travel badly — "Closed captions aren't fully supported if the Teams meeting recording is moved or copied from its original location in OneDrive or SharePoint."
Getting stuck on the same problem in other apps is common; the fix archive covers the equivalent walls elsewhere, and Gmail's version of this error is the one most people meet next.
How to tell it worked
Check the size on disk after compressing — that is the number every limit above is measured against, not the duration and not the resolution. If the recording was long enough to split, check each part separately; they are independent files and only one of them may be over.
FAQ
How big is a one-hour Teams recording? Microsoft's storage planning guidance states that "The size of a one-hour recording is 400 MB." That page gives no quality assumptions behind the figure, so treat it as an estimate for capacity planning.
Why did my long meeting produce two recording files? Because a single Teams recording is capped at "4 hours or 1.5 GB" — either condition, whichever comes first — and at that point "the recording ends and automatically restarts." At 400 MB an hour the size ceiling normally arrives first, around the three-and-three-quarter-hour mark.
Can I email the recording into a Teams channel instead? Not realistically. The "Emailing a channel" table caps each file attachment at "Less than 10 MB," which is a fraction of any normal meeting recording.
Can I send the transcript instead of the video? Often the better move. Meeting organizers and co-organizers can download a transcript "as a .docx or .vtt file" by default. If the tool you are feeding it to expects SubRip instead, convert VTT to SRT first.
Does compressing the recording lose the captions? Captions are not part of the video file to begin with — the captions and transcript file "is stored with the video in OneDrive for Business or SharePoint," and Microsoft notes there is "no direct access to see or manage the captions and transcript file in the file explorer." Download the transcript separately and send it alongside.
Figures cited from Microsoft's Limits and specifications for Microsoft Teams and Teams meeting recording and transcript storage and permissions, checked 16 September 2026. Microsoft revises these pages — verify against the official docs before relying on a number.
