How LinkedIn actually handles a GIF
Two things get called a LinkedIn GIF. The GIPHY picker inside messaging is one; it's fine for DM reactions, and it was never your file to begin with. The other is the real asset: an animated GIF you attach to a feed post as the image. LinkedIn renders that attachment as a looping inline image. No play button, no tap-to-start, no sound icon. It's simply moving by the time a scroller reaches it.
Compare the native video upload, which waits muted behind a thumbnail until someone decides to engage. A GIF removes the decision. That's the entire strategic case: motion that has already started. The cost is that LinkedIn won't build it for you; you arrive with a finished .gif file and attach it.
You already have the raw material
The source is usually sitting on your disk: a screen recording of the dashboard, an export from your editor, phone footage of the physical product. What the GIF turns any of those into a GIF inside your browser, no upload leg, which is worth pausing on when the clip shows an unreleased feature or a client's data. Footage you haven't posted yet shouldn't be on anyone's server.
Aim small. The feed compresses heavy media, most viewers are on phones, and a lean file means clean playback. Something in the low single-digit megabytes, looping for a few seconds, is the deliverable.
Crop for a narrow, vertical feed
A full-width 16:9 recording posted as-is renders as a short letterboxed band that nobody can read on a phone. Decide the shape first:
- 1:1 is the default that never embarrasses you: maximum feed presence without cropping surprises.
- 4:5 stretches taller and flatters a single vertical UI: an app flow, a checkout, a form completing itself.
- 9:16 only for genuinely vertical phone footage; forcing a desktop capture into it just manufactures dead space.
- 16:9 is a deliberate choice for wide charts and before-and-afters, accepted knowing it renders small.
Crop tightly to the moving detail (the number changing, the button responding) so the payoff is legible at feed size. The tool's crop holds these ratios exactly; there's no drifting into an almost-square that the feed re-crops for you.
Settings that protect UI text
Interface demos die two deaths: illegible type and gradient sludge. The same settings prevent both:
- 12 to 15 fps. Product motion looks smooth there at half the frames of 30. Faster rates are for footage with real speed, which polished feed content rarely has.
- Colors around 128 when there's type on screen. Labels, axes, and monospace need palette headroom; logos and flat illustration can drop lower and bank the savings.
- Crop first, then scale to roughly 600 to 900 pixels wide. That's plenty for the feed at a fraction of a full Retina capture's weight, and cropping first means you're not paying for pixels you already removed.
- Let the size readout referee. The projection updates with every adjustment, so fps, palette, and width get traded against each other before the export instead of across five exports.
For a stubborn clip there's a byte-squeezing order of operations in the small-GIF guide.
Trim like the loop pays rent
The classic LinkedIn mistake is posting all fourteen recorded seconds when the story is the three where the state changes. Cut to the action: the click, the transition, one beat of the result. The timeline here trims against actual frames, and the keyboard walks a cut along in single-frame steps, so the edit is exact instead of close.
Then respect the seam. The GIF restarts forever, and a final frame that clashes with the opening frame turns every restart into a visible glitch. Ending on a stable state, or trimming so the loop wraps somewhere quiet, is what makes it feel hypnotic instead of broken. A loop that holds the scroll half a second longer has done its job.
Attach, caption, publish
Start a post, attach the GIF where an image would go, and let the copy do the arguing:
- Open with a concrete claim. "Onboarding went from nine screens to three; here's the new flow" beats any variation of excitement.
- The loop is silent, so words must be visible. Short labels can be burned in with text captions, three lines at most, in either style, each with optional timing, handy for tagging a before and an after. The full pitch belongs in the post copy, where search and screen readers can reach it.
- Proof it on a phone. That's where the audience is; confirm the type reads before publishing.
- Reuse the file. The identical GIF drops into docs, decks, and a product demo follow-up without re-exporting.
One recording, one local conversion, one file that plays everywhere you paste it.