Why turn a Loom into a GIF at all
A Loom link is a great way to make someone book five minutes they don't have. Half your async messages don't need a five-minute walkthrough. They need one moment: the cursor lands on the broken button, the toggle flips, the layout reflows. For that, a Loom link is overkill and a GIF is exactly right. The whole point of going from Loom to GIF is that it loops on its own, it sits inline in the thread, and nobody has to leave the page to catch your meaning.
GIFs also dodge the quiet friction of a hosted video. No "this Loom is private" wall for the contractor in another timezone. No view counter. No expiring share setting your IT team flipped last quarter. A GIF is just a file. Paste it and it plays, in a comment, a doc, or a ticket, the same way every time.
The tradeoff: a GIF has no sound and no narration. So it's the right call for short visual proof (a UI change, a bug repro, a before and after), and the wrong call for anything that needs your voice explaining the why. Keep the Loom link for context, attach the GIF for the punchline.
First, get the mp4 out of Loom
Here's the one quirk that trips people up: you can't feed a Loom link into a converter. Loom stores your recording on its servers, so you need the actual video file on your machine first. Good news, Loom hands it over in a couple of clicks.
- Open the recording on loom.com, hit the Download option in the share or options menu, and Loom gives you a standard .mp4.
- If your plan or workspace has downloads turned off, ask the workspace admin, or use the Loom desktop app, which keeps a local copy of recordings you make.
- Save it somewhere you can find it. Loom's filenames are long and forgettable, so a quick rename now saves you squinting later.
Once you have that mp4, the rest is the normal MP4 to GIF path, and you're roughly two minutes from a finished loop. Loom records at 1080p or higher, so the source is sharp; your job is mostly deciding what to cut and how small to make it.
The settings that actually matter for a screen recording
Loom footage is screen capture: crisp edges, flat UI colors, lots of white space, and usually some text. That's the easiest kind of video to make into a clean, small GIF, as long as you pull the right levers.
- Trim first, hard. Use the frame-accurate timeline to set in and out points, then nudge with the arrow keys to land exactly on the click or the change. A 4 to 8 second loop beats a 40 second tour every time.
- Frame rate: 10 to 15 fps. Cursor moves and panel transitions read perfectly fine here, and you're not paying file size for frames nobody notices.
- Crop to the action. Lock to a ratio (1:1 for a chat thread, 16:9 if you're keeping the whole window) and cut away the browser chrome and empty desktop. Crop before you scale so you don't spend file size on dead pixels.
- Scale down. A Loom recorded at 1080p does not need to stay 1080p. Halve the width and the GIF shrinks dramatically while UI text stays legible.
- Colors: 64, up to 128. Flat interface colors compress well, so a 64-color palette is usually plenty. Push toward 128 only if there's a code editor or fine text that's going soft. Watch the live size estimate as you go.
That combination usually lands a clip under a few megabytes. If you need to go further, our notes on a small-file GIF from video cover squeezing the last bit out without it turning to mush, and the screen recording to GIF page goes deeper on capture footage specifically.
Where the GIF actually goes
You're converting a Loom for a reason, and the destination decides your dimensions. A square 1:1 crop sits neatly in a Slack message or a Notion callout. A 16:9 crop fits a doc or a wiki page. For a GitHub README or pull request, a tight crop of just the changed UI does more work than the full window ever would.
If the loop is going into a product update or a customer-facing doc, treat it like a tiny product demo GIF: start on a clean state, show one clear action, and end before the cursor wanders off. The discipline of a 6 second loop forces you to make a point, which is more than most three-minute Looms manage.
Your Loom, your laptop, nobody else's server
This matters more than people admit. A Loom often shows internal tooling, an unreleased feature, a customer's account, a Slack you'd rather not screenshot. Most online converters work by uploading your file to their servers to do the math. That's your internal screen recording taking a field trip through someone else's infrastructure.
What the GIF runs the whole conversion inside your browser tab. The mp4 never leaves your machine, there's no upload, no account, and no watermark stamped across your work. Once the page has loaded you can even pull the network cable and it still works, which is the most honest proof that nothing's being sent anywhere. If privacy is the whole reason you're here, the convert video to GIF without uploading page makes the same promise in more detail.