← Back to Blog

MP4 to GIF: Best Settings for Small File Size (Without Looking Terrible)

Published

GIFs are a trap.

They’re unbeatable when you need an autoplaying loop inside a GitHub README or a Notion document.

They’re also an ancient, bloated format that destroys sharp text if you use them wrong.

Here’s how to convert an MP4 into a GIF that keeps decent clarity and a sane file size, and when you should skip the format entirely.


The converter

Convert MP4 to GIF in your browser (no sign-up required): → Free Video Converter


Settings that keep the file small

If you don’t want a 40MB GIF:

  1. Keep it short. 2 to 6 seconds, maximum.
  2. Crop hard. Never make a GIF of your full 4K desktop. Isolate the UI element that matters.
  3. Drop the framerate. 12 or 15 fps.
  4. Limit the width. 480 to 800 pixels is the ceiling for a stable GIF.
  5. Scale up the source. Your UI text has to be large in the original MP4, before conversion.

The math behind the bloat

The GIF format wasn’t built for modern video.

Its compression is inefficient, its color palette is limited, and it fights dense content like syntax highlighting and UI gradients.

Push high duration, high framerate, or high resolution through a GIF encoder and the file size explodes. Lower at least two of those three.


By destination

Inline docs (GitHub/READMEs). The goal is a light loop. Crop to the feature area, cap it at 4 seconds, hold 15 fps, and keep the width under 800 pixels.

Landing page teaser. The goal is a clean visual without hurting page load. Crop tight and bump toward 20 fps for smoother motion. Or, better, use an embedded WebM instead of a GIF here.

Bug report. The goal is quick context in Slack. Frame the glitch tightly, cap it at 8 seconds, and drop to 12 fps so the file is small enough to send.


The golden rule for UI clips

You can’t rescue tiny text in post.

If you record a 1440p desktop with 10pt font and convert it into an 800px GIF, the code will look like smeared ink. Change the capture instead: scale up the font before you record, and center the action. 1080p vs 1440p vs 4K: what keeps text sharp


When to abandon GIF

Switch to MP4 or WebM when:

  • The clip runs longer than eight seconds.
  • You need readable text.
  • Page speed matters.

Save GIFs for the places that won’t autoplay HTML5 video.


A good GIF starts with a good MP4

The conversion looks better when the source is good.

If the original capture has a smooth cursor, calm auto-zooms, and no stutter, the GIF inherits that. AUFZEICHNA automates that layer on Windows. Watch demo · Lifetime pricing


FAQ

Why are my GIFs so huge? The format’s compression is ancient. High resolution plus long duration multiplies the file size fast.

What are the right settings? Six seconds max, a hard crop around the action, 15 to 20 fps, and large source text.

Should I use a GIF for a long demo? No. Anything over ten seconds should be a compressed MP4 or WebM: better quality at a fraction of the size.


Related

Related workflows