Fix it now
- Drop the file
- Repair runs locally
- Download the result
Microsoft Teams records meetings to the cloud and stores the finished file as a standard .mp4 — H.264 video with AAC audio — in OneDrive (for one-to-one and group calls) or SharePoint (for channel meetings), with a name like Meeting Title-20240115_143022-Meeting Recording.mp4. When one won't play, the codec is rarely the problem; the file is usually incomplete: the recording never finished processing, or the copy you pulled from OneDrive/SharePoint was truncated. Drop the file above and the tool inspects its real structure in your browser and rebuilds or salvages what the surviving bytes allow — the recording is never uploaded.
How a Teams recording is produced — and where it breaks
When you record a Teams meeting, the media is captured in the cloud and then processed before it becomes a normal MP4 you can play and download. During that window the item in OneDrive or SharePoint may show as still saving or still processing, and a file grabbed too early — or produced by a session that ended abnormally — can be missing the parts a player needs. A finished Teams MP4 is an ISO base-media file: the audio and video payload (mdat) plus a moov atom that indexes every frame. If processing was interrupted, that index can be absent or truncated, and the player reports the file as corrupt, opens to black, or refuses it outright.
The second, more common break happens on the way down. Downloading the recording from OneDrive or SharePoint over a flaky connection, syncing it through the OneDrive client while it's mid-transfer, or copying it off a shared drive early can deliver a truncated MP4 — the front of the file arrived, the tail didn't. Because the moov is often near the end, a truncation is exactly what removes it, which is why a recording that streams fine in the browser can be unplayable once saved to disk.
What can be recovered — and what can't
Where the frames survived but the container is malformed or its index is missing, the fix is a straightforward rebuild: scan the surviving H.264 stream, reconstruct the sample tables, and re-map the frames so a player can decode from the start. Where the file was truncated, the tool salvages the frames that were completely written before the cut and closes a playable container around them — so an hour-long meeting that only half-downloaded still gives back the half that made it, rather than failing whole. All of this runs in your browser as the file is read from disk.
The honest limit is that bytes which never arrived can't be recovered. If a download stopped at 60%, the last 40% of the meeting isn't on your disk and no tool can invent it. The real fix for that is to re-download the recording from OneDrive or SharePoint while it's still there — a clean copy recovers 100% and beats any repair. Repair is for when the cloud copy is gone, expired, or itself broken, and you're left with a partial or damaged file on disk. We also can't reach into a recording that is still genuinely processing in the cloud; wait for Teams to finish, then repair the MP4 if the MP4 is what's broken.
What this can and can't fix
Can fix
- A Teams .mp4 truncated by an interrupted download or OneDrive/SharePoint sync — frames before the cut are salvaged
- Container damage: missing or truncated moov, wrong offsets, zero duration in an otherwise complete file
- Recordings that copied off a shared drive or OneDrive but won't play in any player
- H.264/AAC Teams recordings a download manager or recovery tool returned unplayable, when the video data survived
Can't fix
- The part of a recording that never downloaded (re-download it from OneDrive/SharePoint instead)
- A recording still processing in the cloud — wait for Teams to finish, then repair the MP4 if needed
- A download so short only a fragment of the file arrived
- Files that read as 0 bytes or mostly zeros
If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.