On this page
Prepare a GIF for your platform
Platform limits and recommended compression targets are different. Check the limit shown in your account before uploading.
| Discord | Message attachment limits depend on your subscription and may vary during experiments.
|
|---|---|
| Slack | Custom emoji need a small file and a short animation; file size alone is not enough.
|
| X / Twitter | The GIF upload allowance differs between mobile and the website.
|
| Gmail | For personal Gmail accounts, the attachment allowance applies to the total attached to a message.
|
WhatsApp separates chat media, animated stickers, and document attachments with different size and format rules.
| |
| Shopify | Shopify checks both file size in megabytes and pixel resolution in megapixels for product and theme images.
|
| GitHub | GitHub caps drag-and-drop issue and PR GIF attachments separately from repository social preview images.
|
Last verified:
Which rule applies to my upload?
Use the platform guidance above with this task comparison. Account settings and platform experiments can change what a particular upload accepts; the limit shown in the destination is the final practical check.
| Upload entry point | What the rule measures | Additional check | Suggested next step |
|---|---|---|---|
| Discord message attachment | Account-based per-file allowance. | Current account allowance and valid file. | Use the Discord guide. |
| Discord custom emoji | A smaller-than-256KB file rule. | Emoji permissions and a recognizable small image. | Crop, then compress below the cap. |
| Slack custom emoji | Recommended under 128KB; at most 50 frames. | Square shape, transparency, workspace permissions. | Prepare the source, then try 100KB. |
| Ordinary X post | Mobile 5MB; web 15MB. | Loop behavior and upload client. | Check the client, then actual bytes. |
| Personal Gmail message | Up to 25MB across attachments. | Other attached files and delivery method. | Add all file sizes before sending. |
| Work or school Gmail | Administrator-defined limits. | Workspace policy and recipient access. | Check the applicable account rule. |
Why are recommended targets smaller than the limits?
A target such as 100KB or 1MB is a practical starting point, not an official platform rule. A lighter file can leave room for other attachments or make a small visual easier to share.
Do not use a recommendation to overwrite the actual limit, and do not treat an official maximum as a reason to make a file that large. Preserve the detail needed for the task.
What else can reject a GIF that is small enough?
A file can meet its byte budget but exceed a frame requirement, lack a useful loop, or be sent through an account that lacks permission. These are separate checks.
| Check | Example | Can compression alone fix it? |
|---|---|---|
| Frames | Slack custom emoji over 50 frames. | No; trim or re-export the source. |
| Looping | A single-play GIF displayed as static on X. | No; prepare a looping source. |
| Permissions | A restricted custom-emoji upload. | No; check workspace or server access. |
| Combined attachments | An email containing a GIF and large documents. | Only if reducing the GIF makes the combined total fit. |
Where can I check the platform-specific steps?
The dedicated guides explain the upload choices and practical preparation. Their official source links and verification date show which guidance the comparison uses; platform rules can change after that date.