Request access is not a communication strategy
You know the sequence. You paste the Meet recording link into a doc so people can see the thing that happened. Two of them open it fine. Three of them hit a permission wall and click Request access. You get the emails on your phone during another meeting, fix the sharing, and by the time everyone can watch, the conversation has moved on and nobody watches.
A GIF has no access control list. It is pixels in a file, and once it is in the doc or the chat it is simply visible, already looping, with no player to load and no account to check. That is not an argument against Drive, which is a perfectly good place to keep an hour of video. It is an argument against making people negotiate with an hour of video to see five seconds of it.
Where Meet puts it, and how to get the real file
Recording is a Workspace feature rather than a personal-Gmail one, available on Business Standard and above and on the education and enterprise editions. When a meeting is recorded, the file lands in the organizer's Google Drive inside a folder named Meet Recordings, and the person who started the recording gets an email with a link once processing finishes. Meetings inside a shared drive inherit that drive's permissions rather than the organizer's.
One detail costs people time: Drive's preview player streams a transcoded version, so watching it in the browser does not give you the file. Use the download option to get the actual .mp4 onto your disk, then bring that here. If downloading is not available to you and the replay is playing in a tab on a desktop browser, Record a Tab can capture the seconds you need in real time, on your machine, with nothing uploaded. A downloaded file is always the sharper source; the recorder is the shortcut when it is not.
The recording is a composite, and that decides your crop
Meet does not record your view of the meeting. It records a composed layout that follows the active speaker or whatever was pinned or presented, so the finished file may look nothing like what was on your screen at the time. There is no re-layout later, no isolating one participant after the fact. What was composed is what you have.
That makes cropping the whole editorial decision, and it is worth making deliberately. A presented screen is flat, text-heavy footage that stays legible when you keep the palette generous. A camera tile is soft, noisy video that compresses badly and rewards a smaller output size. Cutting to one or the other with a locked ratio (1:1, 9:16, 4:5, 4:3, 16:9) both sharpens the point and takes the biggest single bite out of the file size before you have touched a dial.
A settings pass for slides, faces, and small type
Trim first, and trim harder than feels right. Two to five seconds is the whole of a good meeting clip; anything longer starts explaining instead of showing, and the arrow keys will move each edge a single frame so the loop opens exactly on the moment. Then the four dials:
- Frame rate: 10 to 12 fps. Nobody talking on a call needs more, and every extra frame is stored nearly whole in a GIF.
- Width: 600 to 640 when a presented slide has to stay readable, 480 when the subject is a face and legibility is not the point.
- Colors: 128 for anything with text or a chart, dropping toward 96 or 64 for camera footage where nobody is reading anything.
- Dithering: on when a photo or gradient in the deck starts to band, off for flat slides where it only adds noise.
Since the GIF is silent, the sentence that made the moment can go on the frame: up to three captions, dragged wherever they read best, each able to appear for only part of the loop. And if the destination is the recap doc, the Google Docs guide covers how Docs handles an animated image once it is in there.
This page has never asked for your Drive
The usual online converter that offers to work with Google Drive wants an OAuth grant to do it, which means a third party holding standing access to your files, revocable in a settings page you will never visit again. This one cannot ask, because it has no server to hold the token and no reason to want one. There is no sign-in, no connected app, no scope.
What replaces all of that is a file you hand over on purpose, once, to a page running on your own machine. The decode and the GIF encode happen in the tab, the finished file is saved by you, and pulling your network connection after the page loads changes nothing about whether it works. The same holds for the Zoom side of your calendar. Open the converter and drop the mp4 in.