Sharing Meeting Recordings: From Zoom and Teams to Email-Friendly MP3

Every remote team has lived this sequence: an hour-long meeting gets recorded for the people who could not attend, the recording lands as a 500 MB video file, someone tries to email it, the mail bounces, a cloud link gets shared instead, permissions break, and three weeks later nobody absent has actually watched it. The irony is that for a talking-heads meeting, the video track carries almost nothing — slides people already have, thumbnails of faces — while the entire substance rides in the audio. Extract that audio, compress it for speech, and the same meeting becomes a 25 MB MP3 that attaches to a normal email and plays on any device during a commute.

What the platforms actually give you

Where the recording lands, and in what format, depends on the platform and settings:

• Zoom produces MP4 video and — if the host enabled it — a separate M4A audio-only file. Local recordings go to the host's machine; cloud recordings to the web portal.
• Microsoft Teams saves MP4 to OneDrive or SharePoint, with AAC audio inside. No separate audio-only file.
• Google Meet saves MP4 to the organizer's Drive.
• Phone and handheld recordings of in-person meetings typically arrive as M4A.

Two paths follow. If you have an audio-only file already (Zoom's M4A, a phone recording), a straight conversion does the job: run it through an M4A to MP3 converter, or an AAC to MP3 converter for raw AAC streams some tools export. If you have video, extract the audio with an MP4 to MP3 converter — the extraction FAQ covers that path. Either way the video data, which is 90-plus percent of the bytes, is gone.

The compression ladder for meetings

Meeting audio is speech, and speech compresses beautifully. The ladder, from cautious to aggressive:

• 128 kbps stereo — about 56 MB per hour. Transparent, but overkill for a meeting.
• 96 kbps mono — about 42 MB per hour. Indistinguishable for voices; the sensible default.
• 64 kbps mono — about 28 MB per hour. Slightly softened but fully intelligible; a one-hour meeting fits Gmail's 25 MB cap with almost no trimming.
• 48 kbps mono — about 21 MB per hour. Noticeably compressed, still entirely usable for catching up on a discussion.

Use a compression tool to hit a target size directly, and see the compression settings FAQ for the bitrate math. The mono step matters more than people expect: conference audio has no stereo information worth keeping, so a stereo to mono pass is a free halving — the mono vs stereo FAQ explains why voice loses nothing.

Make it worth listening to

Two quick edits turn a raw recording into something colleagues will actually play:

• Trim the dead zones. The five minutes of "can everyone see my screen" at the start and the goodbyes at the end are not content. A trim tool cuts them in seconds. For long meetings, consider cutting the recording into agenda-item segments so people can jump straight to the decision they care about.
• Normalize the levels. Remote meetings are a lottery of microphone quality and speaking distance — one colleague booms, another whispers from a laptop mic across the room. A normalization pass levels the speakers so nobody rides the volume control for an hour.

The audio-plus-notes pattern

The MP3 works best as one half of a pair. Send the recording together with the written notes — decisions made, owners assigned, deadlines set — and each half covers the other's weakness: the notes give absentees the outcome in thirty seconds, the audio gives them the reasoning and the tone when an outcome needs unpacking. Teams that adopt this pattern report a specific behavior change: people stop asking "what did we decide about X" in chat, because the answer is one email search away, with the exact discussion attached and playable. If your team runs meeting transcription, the same prepped MP3 — mono, normalized, decent bitrate — is also the ideal transcription input, so one file serves listeners and the transcript pipeline alike.

Distribution that actually works

The 25 MB attachment is the point. Email attachments require no permissions, no accounts, no link that dies when someone leaves the workspace — the file simply arrives and plays, forever, in every mail client. For chat tools, the same MP3 sails under Slack's and Teams' upload limits. And an audio file changes how the meeting gets consumed: a recording that demanded an hour at a desk becomes something absorbed on a commute, a run, or a school pickup, often at 1.5x. People who would never watch the video genuinely do listen to the MP3.

A note on judgment: a recording that exists to be skimmed by absentees is a different artifact from an official record. If the meeting has legal or HR significance, follow your organization's retention rules and keep the original platform recording; the MP3 is a convenience copy, not the system of record.

The five-minute routine

For a recurring meeting, the whole pipeline becomes a rote post-meeting task:

• Download the recording (or the M4A audio file if the platform made one).
• Extract or convert to MP3.
• Trim the setup and the goodbyes.
• Normalize, downmix to mono, compress to 64 to 96 kbps.
• Attach to the meeting-notes email, subject line and date in the filename: "2026-05-12 product-sync.mp3".

Five minutes of browser work per meeting, and the recording stops being a 500 MB monument nobody visits and becomes what it should have been all along: a small, portable file that lets the people who missed the room hear what happened in it.