Skip to main content

Compress GIF for X / Twitter

Compress your GIF before posting on X, then check the upload route: X lists up to 5MB for animated GIFs on mobile and 15MB on the web. The 1MB preset is a smaller starting target, not a platform maximum.

Updated:

Drop GIFs here or choose files

Paste an HTTPS image URL

Prepare a GIF for your platform

Platform limits and recommended compression targets are different. Check the limit shown in your account before uploading.

X / Twitter

The GIF upload allowance differs between mobile and the website.

  • X lists an animated GIF limit of 5MB on mobile and 15MB on the web.
  • These figures describe posting through X. Upload integrations have their own API requirements; do not assume one universal API limit from the mobile allowance.
  • X displays a GIF that plays only once and does not loop as a static image. Compression preserves loop information; viewer playback settings are another separate check.

Last verified:

How to use this tool

  1. Check whether you are posting from mobile or the X website and use the corresponding allowance.
  2. Add a GIF to the tool with the free 1MB target selected.
  3. Compress and preview movement, text, and color detail throughout the animation.
  4. Download the output and upload it through your chosen posting client. Confirm its actual size if the upload is rejected.

Why can the same GIF upload on a computer but not a phone?

The ordinary web and mobile posting allowances differ. A file can fall below the web allowance while remaining above the mobile allowance. Compare the actual file size with the client you will use.

Upload routeOfficial GIF allowanceHow to use this information
Ordinary mobile postingUp to 5MB.Check the downloaded file before attaching it.
Ordinary web postingUp to 15MB.Do not apply this larger allowance to a phone upload.
Media Studio or APISeparate specifications.Check the documentation for that upload workflow.

Measured examples

Self-authored examples, processed with the same compression engine as this tool. Results vary with the source; these are not promises for your files.

Measurement data (JSON)
TargetOriginalActual size
Detailed tutorial1,141,589 Bytes1,141,589 Bytes
Target: 1000 KB1,141,589 Bytes903,284 BytesTarget met

Detailed tutorial

Original · 1,141,589 Bytes

Detailed tutorial: Original

Dimensions: 640 × 360px
Frames: 40 · Duration: 4 seconds

Inspect detail

Original

Detailed tutorial: Original

Target: 1000 KB

Original · 1,141,589 Bytes

Target: 1000 KB: Original

Output · 903,284 Bytes

Target: 1000 KB: Output

Dimensions: 640 × 360px
Frames: 40 · Duration: 4 seconds

Applied settings: 256 Maximum colors · Lossy level 20

Inspect detail

Original

Target: 1000 KB: Original

Output

Target: 1000 KB: Output

Why does my uploaded GIF look like a still image?

Check whether the source loops. X's help states that a GIF which plays only once and does not loop is displayed as a static image. Making that same file smaller will not change its loop behavior.

The compressor preserves the source's loop information. Also distinguish a static result from a viewer's autoplay setting: a local preview proves the file can animate, but does not control another person's client.

CheckWhat it tells youWhat to do
Play the original locallyWhether the file contains valid animation.Obtain a complete GIF if it fails.
Check loop behaviorWhether it plays once instead of repeating.Re-export a looping source when needed.
Check the destination playback settingsWhether animation is being paused by the client.Test the post in the intended client.

How do I keep the important part of a reaction?

Trim the lead-in and crop irrelevant margins before choosing an aggressive size target. A clear expression or readable caption matters more than retaining unused background.

If the entire clip is a detailed moving scene, consider an accepted video upload instead. GIF to MP4 is available with Pro; it creates a different format and follows X's video rules.

What should I check before posting?

Read the actual bytes, watch the complete loop, and preview any small caption at the size people will see. If compression misses the selected target, edit the source or try a less restrictive target only when the destination allows it.

Mobile posting, web posting, Media Studio, and automated API uploads should not share a single assumed limit. Use the official documentation for the selected route.

Frequently asked questions

Is 1MB required by X?

No. It is this page's starting compression target. Ordinary mobile and web GIF uploads have their own allowances.

Will compression make a non-looping GIF loop?

No. The compressor preserves loop behavior. X says a GIF that plays only once is displayed as a static image.

Can I use the web allowance for an API integration?

Do not assume that. API and Media Studio requirements are documented separately from ordinary posting.

Can compression guarantee autoplay?

No. A file's loop metadata and the viewing client's playback settings are separate from file size.