Recommended GIF Size for X (Twitter): Best Specs and Aspect Ratio

The recommended GIF size for X is under 3 MB, at 1280 x 720 or smaller, using 16:9 or 1:1 aspect ratio, 12 to 15 fps, and well under 200 frames. That target sits comfortably inside X's hard limits (15 MB desktop, 5 MB mobile, 1280 x 1080, 350 frames), so it uploads cleanly on both desktop and mobile.

This guide covers the recommended specs — the settings that give the best-looking, most reliable result — not just the maximum limits. If you're troubleshooting a failed or downsized upload, read Twitter (X) GIF Size Limit first for the hard caps. This post picks up from there with the settings worth aiming for.

Recommended GIF Specs for X at a Glance

Treat the "recommended" column as the settings to design around, and the "hard limit" column as the wall you never want to get close to.

What Is the Recommended GIF Size for X?

Aiming for under 3 MB is the single most useful habit for GIFs on X. It is comfortably below the 5 MB mobile ceiling covered in our GIF size limit guide, which means:

• mobile uploads go through without X silently recompressing them
• desktop and mobile viewers see the same quality, since nothing gets downsized after the fact
• the file loads fast in a busy timeline, where every extra megabyte competes with autoplay speed

A 3 MB target is not a hard rule — a simple, low-motion loop might come in at 1 MB, while a busier one might need 4 MB. The point is to treat 5 MB as the wall and 3 MB as where you actually want to land, with headroom in reserve rather than sitting right at the limit.

Desktop vs. Mobile: Why the Recommendation Is the Same

X applies different hard caps to desktop (15 MB) and mobile (5 MB) uploads, but the recommended size doesn't change depending on where you upload from. A GIF that stays under 3 MB uploads reliably from either, which means you only have to optimize a file once instead of maintaining a "desktop version" and a "mobile version" of the same GIF.

What Aspect Ratio Does X Crop GIFs To?

For a single GIF in a normal post, X generally displays the file close to its native aspect ratio in the expanded tweet view, but the timeline preview is where cropping shows up. Wide or very tall GIFs commonly get cropped down to fit the feed's preview box, and any post with multiple media items follows X's standard media-grid cropping instead of showing full frames.

The two safest aspect ratios to design around are:

• 16:9 (landscape) — the standard widescreen ratio, and the safest choice for anything screen-recorded, gameplay-related, or shot in landscape video
• 1:1 (square) — crops the least across different surfaces (timeline, quote tweets, grids), because there's no extra width or height for X to trim

Avoid extreme aspect ratios (very tall vertical clips, ultra-wide panoramas) unless the subject is centered — GIFs shaped like that are the ones most likely to lose important content off the edges when a preview crops them.

Practical rule: keep the subject of your GIF centered in the frame regardless of ratio. Even a well-chosen 16:9 or 1:1 export can get clipped slightly in some grid layouts, and a centered subject survives that better than one positioned near an edge.

Recommended Frame Rate and Frame Count

X's documented frame cap is 350 frames, but the recommended target is well below that:

• Frame rate: 12–15 fps looks smooth for reaction GIFs, meme loops, and most UI demos. 24–30 fps is rarely worth the file-size cost for short social loops.
• Frame count: aim for under 200 frames. At 15 fps, that's over 13 seconds of runtime — more than enough for the vast majority of GIFs, which work best at 2–6 seconds anyway.
• Duration: shorter loops read better on autoplay and are far easier to keep under the recommended file size.

Every additional frame adds to file size, so cutting frame rate and duration first — before touching resolution — is usually the most efficient way to hit the recommended target without hurting perceived quality.

Export Settings for Common Tools

Photoshop

1. Open the Timeline panel and trim to the shortest loop that still reads clearly
2. File > Export > Save for Web (Legacy), choose the GIF preset
3. Set Colors to 128 or lower (256 is rarely necessary for short loops)
4. Resize to 1280 x 720 or smaller in the same dialog
5. Check the resulting file size in the preview panel before exporting — resize or drop frames until it reads comfortably under 3 MB

ezgif

1. Upload the source video or GIF to ezgif's Resize tool and scale to 1280 px wide or smaller
2. Run it through Optimize and reduce colors (try 128 first)
3. Use Crop to center the subject if the source has excess background
4. Use the Frame rate / Speed tool to drop to 12–15 fps if the source is 24 or 30 fps
5. Check the final size on the result page and re-run optimization if it's still over 3 MB

ffmpeg (one-liner)

For a high-quality GIF at a controlled size and frame rate, ffmpeg's palette-based export beats a naive conversion:

ffmpeg -i input.mp4 -vf "fps=15,scale=720:-1:flags=lanczos,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" output.gif

This generates an optimized color palette for the clip instead of using a generic one, which noticeably reduces banding while keeping the file smaller. Lower the scale value (e.g. 480:-1) or the fps value if the output is still too large.

Should You Upload a GIF or an MP4 to X?

Here's the detail that changes the whole calculation: X converts most uploaded GIFs to MP4 anyway. The platform re-encodes GIF posts into a looping silent video for delivery, because video compresses motion far more efficiently than GIF's limited color palette allows. Our post on why Twitter GIFs are usually MP4s covers this in more detail, including a real-world example of a GIF shrinking by more than 80% once converted to video.

That means that if your only goal is to post a looping animation to X — not to distribute a portable .gif file elsewhere — uploading a native MP4 from the start is often the better move:

• you control the compression and quality directly, instead of relying on X's conversion
• MP4 supports far more colors than GIF's 256-color palette, so gradients and detail look cleaner
• file sizes are dramatically smaller for the same visual result

Stick with true .gif uploads when you specifically need the .gif format afterward — for example, re-downloading and reusing the file somewhere that requires GIF, like an email client, a forum, or a documentation tool. For posting directly to X, an MP4 export at 1280 x 720, 15 fps, and a short duration will usually look better than a GIF at the same file size.

If you're downloading GIF posts from X rather than uploading them, see How to Download Twitter GIFs for the full walkthrough, including why the file you save is often an MP4 regardless of what the original poster uploaded.

FAQ

What is the best GIF size for X?

Under 3 MB is the best practical target. It sits well inside X's 5 MB mobile limit and 15 MB desktop limit, so it uploads reliably from any device without X recompressing or downsizing it after the fact.

What aspect ratio does X crop GIFs to?

X doesn't enforce one fixed aspect ratio, but timeline previews and media grids commonly crop wide or tall GIFs to fit their layout. 16:9 and 1:1 are the safest choices because they crop the least across the timeline, expanded view, and multi-image grids.

Should I upload a GIF or an MP4 to X?

For most posts, MP4 is the better upload choice. X converts most GIF uploads into looping MP4 video anyway, so uploading a native MP4 gives you control over quality and compression instead of leaving it to X's conversion. Only upload a true .gif if you specifically need the .gif format later.

How many frames should a GIF have for X?

Aim for well under 200 frames, even though X's documented cap is 350. At a recommended 12–15 fps, 200 frames covers over 13 seconds — more runtime than most reaction GIFs, meme loops, or short UI demos actually need.

Does resolution or frame rate matter more for GIF file size?

Frame rate and duration usually matter more. Dropping from 30 fps to 15 fps, or trimming a loop from 10 seconds to 4 seconds, typically saves more file size than reducing resolution alone, since every additional frame adds directly to the file.

Final Takeaway

X's hard limits (15 MB desktop, 5 MB mobile, 1280 x 1080, 350 frames) define what's allowed. The recommendations here — under 3 MB, 1280 x 720 or smaller, 16:9 or 1:1, 12–15 fps, under 200 frames — define what actually looks good and uploads reliably every time. When in doubt, export smaller than you think you need to, and consider whether an MP4 gets you a better result than a GIF in the first place.