Figma Slides grew up. The decks are still frozen.
Figma Slides started as a side room off the design canvas. It isn't anymore. Product managers draft launch decks in it, founders pitch from it, and people who have never touched an auto layout run their weekly reviews in it, because the deck lives where the work already does. What most of those decks still lack is motion: the demo is a screenshot, the launch moment is a bullet point.
Video is the obvious fix and the unreliable one. What video can do on a Figma slide depends on your plan and on where the deck is being viewed, and that support has shifted more than once (file everything here under mid-2026). A GIF skips the whole question. That's the entire story of a GIF in Figma Slides: Figma treats it as an image: it shows as a still while you edit, then loops in present mode, for you on stage and for whoever opens the shared deck and presents it later.
Why a GIF wins the slide
Against embedded video, the humble GIF racks up a surprising number of wins in a deck:
- It autoplays in present mode. No click, no play button, no fumbling on stage. The slide appears and the motion is already running.
- It loops. The demo repeats while you field questions, instead of ending awkwardly on a paused final frame.
- It has no plan dependency. An image is an image. Nobody on the free tier sees an upgrade prompt where your demo should be.
- It survives the share. Duplicate the deck, hand off the file, open the link from another org: the loop is baked into pixels, so it travels wherever the slide does.
The honest flip side: a GIF has no sound and no scrub bar. If the moment needs narration or three minutes of runtime, link the full video and let it be a video. The GIF's job is the eight-second proof that the thing works.
The two GIFs a deck actually needs
The first is the demo. A screen recording of the feature doing the thing, cut to its best few seconds, beats a static screenshot in every deck it appears in. The screen recording page covers capturing UI cleanly, and the product demo guide covers making the clip persuasive.
The second is the meme. All-hands decks, retro slides, the closer that earns the laugh: a well-chosen reaction loop does more for a room than another gradient. Either way the path is the same: bring the clip to What the GIF, and if the joke needs words, meme-style captions bake straight onto the frames.
Crop to the slide, then mind the total
A Figma Slides deck is a 16:9 canvas, and the crop can lock to exact ratios, so a full-bleed GIF is one setting: crop at 16:9 and it drops onto the slide edge to edge. For a GIF sitting inside a layout, 1:1 or 4:3 usually reads better next to text. Weight is the other discipline, because a deck is a file people duplicate, forward, and open on hotel wifi, and every placed GIF is stored inside it.
- Hold each GIF under about 2MB. Most demo loops can land well below that, and the live size estimate updates as you tune, so you know before you export.
- 10 to 15 fps is plenty. UI motion and reaction clips both read smoothly there, at a fraction of the weight.
- 128 colors covers most footage. Flat interface recordings often look identical at 64 with dithering on.
- Downscale to display size. A GIF filling a third of a slide doesn't need 1080p of pixels. The small-file walkthrough runs the full squeeze.
Loops that don't flinch mid-pitch
A loop with a visible jump reads as a glitch, and it will glitch sixty times during one Q&A. The fix is choosing the cut, not hoping. Set the in and out points where the footage rests on the same state, then walk the trim with the arrow keys one frame at a time until the last frame hands off to the first without a stutter. For motion with no natural resting point, the per-clip bounce toggle plays it forward then backward inside one loop, which closes the gap by construction.
The launch isn't public. The conversion shouldn't be either.
Launch decks are made of footage that doesn't exist publicly yet. The conversion runs entirely in your browser, on your machine: the recording is decoded, trimmed, and encoded locally, and it keeps working with the network off. Nothing about the unreleased feature transits a server on its way to slide four, and there's no account attached to any of it.