Six seconds, and not one frame more
Pick a video in a WhatsApp chat and the editor opens with a duration bar across the top. Drag the handles until the clip is six seconds or shorter and a GIF button appears in the corner. Leave it at seven and the button is simply not there. That is the documented behavior in WhatsApp's own help pages, and it has held for years, though limits move, so check yours before planning around it.
The GIF tab in the attach panel is a different thing entirely. That searches Tenor, Google's GIF index. It is a library, not a maker, and nothing you shot is in it.
Everything that button decides without asking you
One tap is a fair price for a reaction clip. It costs you every choice that separates a loop people replay from one they scroll past:
- The in and out points. A drag handle on a phone lands within a third of a second. Reactions live or die inside that third of a second.
- The crop. WhatsApp keeps the source shape. Vertical phone footage means a tall bubble with your subject occupying the middle fifth of it.
- Words. There is no caption step. Anything you want written on the loop has to arrive already written.
- Two moments in one loop. Setup then payoff needs a sequence. The app converts one clip at a time, full stop.
- Speed and direction. No half speed on the good part, no bounce, no reverse.
Doing it in the editor instead gives you frame-accurate trim handles, a ratio-locked crop, up to three text overlays, and up to ten clips sequenced into one output. Then WhatsApp is only being asked to deliver a finished file, which it is very good at.
Built for a phone on two bars
WhatsApp is the messenger that grew up on weak networks, and it behaves like it. Media gets recompressed on the way out, and a sent GIF plays on the other end as a short muted loop rather than as the file you made. Historically the app has capped shared media around 16 MB, and larger things go through the document path instead. Numbers like that shift with app versions, so treat it as a ceiling to stay well under rather than a target.
Practically, that means building small on purpose instead of building big and hoping. Aim for 480 px on the long edge, 10 to 15 fps, two to six seconds, and a file under 2 MB. Watch the estimated size update as you turn each dial, and if it will not come down, Extra Compression at Medium usually takes another third to a half off. A recipient on a metered plan notices the difference, and they are a large share of who is on the other end of this app.
If the file is already made and simply too heavy, run it through the compression page rather than starting over.
When the GIF tab beats making your own
Most WhatsApp GIFs should not be made. They should be found.
- A generic reaction. Tenor has thousands of people rolling their eyes, and one of them is already better lit than anything you will shoot.
- Anything with sound. GIF carries none. A laugh, a song, someone talking: send it as a video and keep the audio.
- Anything longer than ten seconds. A loop with no off switch beside forty other messages is a nuisance, not a joke.
Making your own is worth it when the footage is yours and nobody else's: your kid taking two steps, the dog doing the thing, a colleague's face at the exact second the number came in. That is not in any library and never will be.
The footage in this app is the personal kind
Look at what actually sits in a WhatsApp camera roll. Family, kids, a whiteboard from a meeting, a photo of a document someone needed urgently. It is the most ordinary and least publishable video anyone owns.
The usual way to make a GIF from it is to upload the clip to a free website, which means a copy of your three seconds of family footage now lives on hardware belonging to a company whose name you will forget by tomorrow. This one works differently by construction, not by promise: the page loads, then your browser decodes and re-encodes the file locally. Turn off the wifi after the page is open and it still works. That is the test that matters.