A GIF is the easiest way to drop a clip into a README, a chat, or a tweet — until it lands at 14 MB and pixelated. The two knobs that decide whether your GIF looks good and stays small are frame rate and size, and they pull in opposite directions. Get the balance wrong and you either get a slideshow or a file too heavy to embed.

Here is how to think about it, and a workflow that lets you tune both before you commit a single credit.

The trade-off in one sentence

Lower the frame rate to shrink the file; lower the dimensions to shrink it more. Quality loss comes from dropping frames (motion looks choppy) and from scaling down (detail disappears). Your job is to spend those trade-offs where they hurt least.

Step 1 — Start from the right source

GIF encodes every frame as a full image, which is why it balloons. Two things you can control at the source:

  • Trim first. A 3-second loop beats a 12-second clip every time. Cut the clip to the exact moment with a trim tool, then convert. You are literally removing 75% of the frames before GIF even sees them.
  • Crop to the action. If the relevant part is a 480×270 corner of a 1920×1080 screen recording, crop it. Every pixel you drop is a pixel GIF does not have to store across hundreds of frames.

Step 2 — Pick the frame rate on purpose

This is the lever most people leave on autopilot.

  • UI, code, static scenes: 10–12 fps is plenty. Nothing moves fast, so the eye fills in the gaps.
  • Talking head / gameplay: 15–20 fps keeps motion smooth without going wild on size.
  • Fast action (sports, particles): 24–25 fps, but expect the file to grow fast — each added frame is a full image.

Rule of thumb: drop the frame rate to the lowest value where the motion still reads, then stop. 15 fps is the sweet spot for most clips people actually share.

Step 3 — Cap the size, not just the rate

Frame rate alone will not save you if the clip is huge. Pair it with a dimension cap:

  • Target 480–640 px on the long edge for chat and social embeds.
  • Keep under ~6 seconds for anything meant to loop in a feed.

A 640×360 clip at 15 fps for 4 seconds is a few hundred frames — small enough to embed anywhere and still sharp.

Step 4 — Convert, then compress in the same pass

The workflow that avoids re-uploading: take the trimmed, cropped source, convert it to GIF at your chosen frame rate and size, and if the result is still heavy, run a compression pass on the output. Because the tools share one credit wallet, the convert and the compress draw from the same balance at per-file rates (from 40 credits, priced by output seconds and shown before the run). Failed jobs cost nothing, so you can tune the settings without spending credits.

If you need the clip for the web rather than a GIF, export VP9 / WebM instead: a typical MP4-to-WebM pass comes out roughly 4× smaller than the GIF at the same visual quality, and it scales to any size. GIF is for ubiquitous embedding; WebM is for actually shipping small.

A note on privacy

Clips you upload for conversion are deleted when the job ends, results are kept 24 hours, and nothing is used to train models. For internal demos and support clips that matters more than people expect — your footage does not linger on someone else's server.

The takeaway

Good GIFs are made before the conversion, not after. Trim to the moment, crop to the action, set the frame rate to the lowest value that still reads (15 fps is the usual answer), and cap the dimensions. Then convert and compress in one session on a per-file balance that never expires. You get a crisp loop that actually embeds instead of a 14 MB smear.

Try the workflow on your own clips: reeloria.com — five browser video tools (video to GIF, compress, convert, trim, burn-in subtitles) on one credit balance, priced per file with the cost shown before every run.