What Apple's picker actually hands you
In Messages, the #images app searches a hosted index and drops a result into your bubble. Apple's own support pages say plainly that GIFs from #images animate only in the Messages app on Apple devices. So the thing in the bubble is less a file than a reference: it plays where Apple says it plays, and elsewhere it may not.
A .gif you attach yourself is the opposite. It is a real file with real frames, it animates in Messages, it sits in Files as itself, and it can be forwarded into Slack or a Notion page or an email without turning into a broken rectangle. That difference is the entire reason to make one.
The short path runs through the Mac, not the phone
The usual instructions have you converting on a laptop, moving the file to a phone, then sending it. Skip two of those steps. Messages on macOS accepts a drag and drop straight into the compose field, so the GIF goes from your Downloads folder to the conversation without ever touching iOS. It syncs to your phone afterward like every other message.
If the phone is where you live, AirDrop the export from the Mac and save it into Files rather than Photos. A GIF routed through the photo library can come back as something other than what you exported, and Files hands it on exactly as encoded. Or build it on the phone in the first place: the converter runs in mobile Safari, so a clip already in your camera roll never has to leave the device it was shot on. Nothing here talks to a server, so the whole loop, so to speak, closes on hardware you own.
One perk of that architecture: once the page has loaded it keeps working with no connection. Airplane, subway, a hotel network that wants your room number. The GIF gets built, and it sends when the signal comes back.
A bubble is about 250 pixels wide, so act like it
iMessage renders attachments at conversation width, which is narrow, and shorter still next to a name and a timestamp. A 1179-pixel iPhone screen recording, shot at 60 fps because that is what phones do, is roughly four times the pixels the bubble will ever show and four times the frames anyone can perceive in a loop.
- Crop before you scale. Cut to the face, the hands, the one control being tapped. Downscaling a full screen keeps everything equally unreadable.
- 320 to 480 px on the long edge. Past that you are paying for pixels the bubble crops away.
- 12 to 15 fps. Faces and gestures read fine there. Below 10 a person turns into a flipbook.
- One to three seconds. A chat GIF is punctuation. Nobody watches a paragraph.
- Under 1 MB. It sends instantly on a bad connection and never stalls mid-thread.
Turning a screen recording into something legible at that size is its own craft, and the screen recording page goes through it properly.
Green bubbles change the rules mid-send
iMessage is Apple to Apple. The moment one recipient is on Android, the thread leaves it, and what happens to your GIF depends on what replaces it. Over RCS, which iPhones have supported since iOS 18, media goes through as media and the loop generally survives. Over old-fashioned MMS it does not: carriers have historically squeezed multimedia messages down to a few hundred kilobytes, and a GIF that survives the trip often arrives as a single frame.
Both ends and both carriers have to agree for RCS to apply, so a mixed group chat is genuinely unpredictable. If the loop has to land for everyone, keep it small and make the first frame carry the message on its own. That is the same discipline classic desktop Outlook forces in email, for the same reason: somewhere in the chain, something will show frame one and stop.
What a GIF cannot be in Messages
- A sticker. Live Stickers are cut from Photos subjects by iOS itself, with their own transparency and their own drawer. A GIF is not one and cannot become one here.
- Audio. Never has been. A clip that is funny because of what someone says is a video.
- A Tapback, a Memoji, or anything with screen effects. Those are Messages features, drawn by the app, not pixels in a file.
- Transparent. Our GIF export flattens onto a solid background, so a loop on a chat background will show its own rectangle.
What it can be is a three-second thing that happened to you, sent to a person who will understand it immediately. Apple's index does not have that one.