2026-08-29
Where Zoom, Google Meet, and Teams recordings actually go in 2026 (and how to clip the four minutes that matter without uploading the hour)
Every post in this series so far has been about someone else's upload limit — Discord's 20MB, Gmail's 25, Notion's 5, Etsy's fifteen seconds. This one is about the biggest video file most working people already own, sitting right now on their own machine or in their own cloud drive: the meeting recording. It has a shape nothing else in this series has — an hour long, mostly silence and screen shares, with four minutes somewhere in the middle that the person who missed the meeting actually needs to see. And it has a property nothing else in this series has, either: it's a recording of your team discussing internal business, which makes it precisely the wrong file to drag into a random free "online video cutter" that sends it to a server you know nothing about. Here's where Zoom, Google Meet, and Microsoft Teams actually put their recordings, what their own documentation says those files weigh, how far each platform's built-in trimming goes — and how to cut the clip that matters on your own device, without the recording ever leaving it.
Where the recording actually lands, per each vendor's own docs
Zoom is the one where the file is most likely already on your computer. Zoom's own free-plan page says local recording "is available with all Zoom Workplace plans, including the free (Basic) plan," and that it saves the meeting "as a video file directly on the computer where the recording took place" — desktop only, not mobile, and only the host records. What that leaves in your folder, per Zoom's recording-formats page, is an MP4 video file plus a separate M4A audio-only file. Cloud recording, with its trim tool and share links, is listed on that same plan page only as a paid upgrade, with "5 GB of cloud storage per license." Microsoft Teams records to the cloud: per Microsoft's storage documentation, a private meeting's recording saves to the organizer's OneDrive, in a Recordings folder, and a channel meeting's to the channel's SharePoint site — and Microsoft's support page shows it appearing there as an ordinary .mp4 file. One permission detail from Microsoft's recording-policy page matters for this post: "guests and external attendees can view the recording only if the recording is explicitly shared with them" — sharing outside the meeting is on you. Google Meet gates recording hardest: per Google's own help page, the record button exists only on paid editions — Business Standard and Plus, the Enterprise tiers, Education Plus, Workspace Individual, even Google One with 2TB+ — and recordings save to the organizer's Drive in a Meet Recordings folder, capture the active speaker plus whatever was presented, and stop automatically at 8 hours.
What an hour of meeting actually weighs
Microsoft's storage-planning guidance is refreshingly blunt: "The size of a one-hour recording is 400 MB." Zoom's long-standing guidance — republished on university IT service pages like the University of Oregon's Zoom page — is that "video recording uses about 200 MB of storage per hour, and screen sharing recording uses about 20 MB of storage per hour." Those numbers set up the entire problem this post is about. A one-hour recording is far too heavy for every destination this series has covered — sixteen times Gmail's attachment cap, twenty times Discord's free limit — and 59 of its 60 minutes are usually irrelevant to the person you want to show it to. The fix isn't a better upload; it's a shorter file.
How far the built-in trim goes
Zoom does ship a trimmer — for cloud recordings. Per Zoom's own trimming page, it requires cloud recording (a paid feature) and a desktop web browser, and it's destructive by design: "Trimming affects all associated audio and transcript files, overwriting the original," viewers and downloaders get only the trimmed version afterward, and you can trim each recording at most 5 times every 12 hours. It's built for tidying the dead air off a recording you're about to share — not for cutting a three-minute clip while keeping the full hour intact. And it doesn't exist at all for local recordings, which are the only kind Zoom's free plan makes. On the Microsoft side, the clock is the bigger surprise: per Microsoft's expiration-policy documentation, Teams recordings "have a default expiration time of 120 days," after which they're moved to the OneDrive or SharePoint recycle bin. If the segment where a decision got made matters beyond this quarter, clipping it into a small file you keep is not just a sharing move — it's how the moment survives the default retention timer. Either way, the platform tools stop exactly where the common need begins: you're holding a full-length MP4 — recorded straight to your desktop by Zoom, or downloaded from OneDrive or Drive to share with someone the permission system won't reach — and you need minutes 42 to 46 of it.
The one file you really shouldn't upload to a random trimmer
A vacation clip uploaded to a sketchy free video site is a privacy shrug. An hour of your team's product roadmap discussion is not. Meeting recordings are, almost by definition, internal conversation — names, numbers, screens full of unreleased work — and the standard web answer to "how do I cut an MP4" is a page that uploads your file to someone else's server first. This is the exact situation NearVid was built for: the file stays on your device. NearVid's trim is a stream copy — the video and audio data are copied through byte-for-byte between your chosen start and end, with no re-encoding, no quality loss, and no encoder even involved — and the whole operation runs inside your browser tab. Nothing is uploaded, to us or to anyone. Because a stream copy never touches an encoder, it also runs in any browser NearVid supports and finishes in seconds even on an hour-long file — the work is closer to a file copy than to video processing.
The mechanics, with the caps in view
The arithmetic from the chart above: with Microsoft's own 400MB-per-hour planning figure, a Teams recording of roughly 75 minutes fits under NearVid's 500MB per-file desktop limit; by Zoom's ≈200MB-per-hour guidance, about two and a half hours of Zoom video recording does. (On phones and low-memory devices the limit drops to 50MB — trimming an hour-long meeting is a desktop job.) Drop the MP4 in, type the start and end times around the part that matters, and export. Two honest details about the cut itself: the times are typed fields, not a visual timeline scrubber, and because a lossless cut can only begin on a keyframe, the clip may start a moment earlier than the exact second you asked for — the same tradeoff described in the still-frame post. From the same screen you can also extract the audio as an MP3 — the right move when what you actually want is a transcript, since transcription tools' upload caps treat audio far more generously than video. And if the trimmed clip still needs to fit somewhere tight — a 25MB email attachment, say — the WebM and MP4 re-encode presets with their "≈" size estimates are one card over.
What NearVid doesn't do here
The usual honesty section. NearVid can't reach into OneDrive, SharePoint, Google Drive, or Zoom's cloud — you download the file first, then drop it in. It won't merge two clips, remove or replace an audio track, burn in captions, or blur a name on screen — it's a trimmer and converter, not an editor. There's no "fit under X MB" button: you pick a preset and read the "≈" estimate. The "Convert to MP4" card only appears in browsers whose WebCodecs H.264 support checks out — though that gate is beside the point here, because trimming an MP4 never re-encodes anything and works everywhere NearVid runs. And a recording your admin's policy blocks you from downloading is out of reach for any local tool, NearVid included.
The honest summary
Per each vendor's own documentation — Zoom's free plan records locally, to an MP4 on your own desktop, with cloud recording and its 5-trims-per-12-hours destructive trimmer reserved for paid plans. Teams records to the organizer's OneDrive as an MP4 that Microsoft sizes at 400MB per hour and, by default, expires into the recycle bin after 120 days. Google Meet records only on paid Workspace editions, into the organizer's Drive. All three hand you the same end state: a long, heavy, sensitive file — and a person who only needs four minutes of it. The move this whole series keeps arriving at fits better here than anywhere: trim the minutes that matter, losslessly, on your own device — the recording never leaves it — and re-encode only if the destination's caps demand it.