The short version
Use the GIF button in the X composer to choose an animation, or attach a saved GIF using the media control. Review the preview before posting. A reaction GIF and a short product demonstration have different jobs, so choose the format around the point you want to make.
There are two common reasons to post a GIF on X: to react in a conversation, or to show something that moves. The steps are almost the same, but the second needs more care. A product demo should make one action easy to follow on a phone screen.
Choose the next step
| Your task | Start here |
|---|---|
| Find a reaction GIF | Open the composer’s GIF picker and search. |
| Upload your own animation | Attach the saved file through the media control. |
| Reply with a GIF | Open Reply on the intended post first. |
| Upload fails | Check the file size, animation, and connection. |
Choose from the GIF picker
Open a new post or reply, select the GIF control, and search for the reaction you want. Select an animation, add the text that gives it context, and check the preview before publishing.
Read the text once without the animation. If it no longer makes sense, add the missing context. Nobody should need to know a TV scene to understand your announcement.
- Open the intended post composer or the reply you want to send.
- Choose the GIF control, search, and select an animation.
- Add enough text to explain your point without relying on the animation.
- Preview the result and confirm the destination conversation before posting.
Upload a saved GIF
Use the media attachment control for a file you already have. X lists GIF upload limits of 5 MB on mobile and 15 MB on the web. Its help also says a GIF that does not loop can display as a static image.
If a recording is too large, make the demo simpler before you compress it again and again. Crop to the part of the screen that matters, cut the waiting time, and show one action. For a longer walkthrough, a video often works better than a long looping GIF.
Choose between a GIF, screenshot, and video
Pick the simplest format that shows the action. A screenshot works best when the key detail is a number or a line of text on screen. A loop works when a short change is the point. A video gives a longer explanation room.
Quick check: can you describe the movement in one sentence? If the demo needs three separate explanations, split it up or use a video with narration. A confusing clip does not get clearer on repeat.
| What the reader needs | Useful starting format |
|---|---|
| Inspect one result or setting | Screenshot with a clear explanation in the post. |
| See one short interaction | A tightly cropped looping demonstration. |
| Follow a multi-step process | Video or a written guide with separate steps. |
| Understand your opinion | Text; attach a reaction only if it adds context. |
Use GIF replies where the meaning is clear
Open the conversation you want to answer before you add the GIF. Read the other replies first. A joke that fits a celebration can read badly under a serious customer problem.
For support replies, put the answer in text first. A short GIF can show where a setting is. It should not replace the explanation or the link someone needs to finish the task.
Troubleshoot the file before rewriting the post
If the GIF picker does not show up, check your connection and try again. X says connection problems can hide it on mobile. For an uploaded file, check its size and make sure it is an animated GIF, not a renamed image.
Save your text before you keep troubleshooting. Open the file on your device to see if the animation works, then attach it again. A broken file and a failed upload need different fixes.
- Preview the entire loop, including the transition back to the start.
- Check that important UI text is readable at phone size.
- Make sure the animation does not expose customer details or account tokens.
- Keep the original recording so you can make a cleaner export later.
| Symptom | Check before retrying |
|---|---|
| File is too large | Trim the sequence and check the upload limit for your client. |
| Animation looks still | Confirm that the source animates and loops. |
| UI text is unreadable | Crop to the relevant action and preview at phone size. |
| The first frame gives away private data | Redact in the original recording before exporting. |
| The GIF repeats too quickly to follow | Leave enough time for the action and result to be understood. |
A useful founder example: show one change
Say you simplified a three-step setup form. A good demo shows the old sticking point and the new action, with a caption that says what changed. It does not need a dramatic reaction GIF on top.
Use text such as “We moved workspace selection into the first screen so you can finish setup without going back.” That gives readers something concrete to judge. “Huge update” with a party GIF gives them much less.
Test reaction GIFs and product demos separately. Check whether the right readers ask useful questions or visit the page. A fun loop does not prove the product explanation worked.
Plan the recording around three moments: the initial state, the action, and the result. Cut unrelated clicks and cursor wandering. The demo is done when a reader can explain what changed. It does not need every screen you visited.
If you use a screenshot of a result as proof, keep enough context to read it. A cropped success screen does not prove more conversions. A faster-looking GIF does not measure how long the task really takes. Say what the clip shows and keep bigger performance claims out of it.
Frequently asked questions
Can I post a GIF from my own files?
Yes. Use the media attachment control and check the file against X’s documented upload limits.
Why is my GIF showing as a still image?
X says non-looping GIFs can appear as static images. Check the animation in the source file and inspect the composer preview.
Should every launch post include a GIF?
Only when movement explains something useful. A clear screenshot or text example can serve the reader better.
Build the post around the point, then choose the media
ClimbX helps you turn product work into a clear X draft in your own voice. Use the media that explains the change, review the claim, and schedule the finished post.
Read next
- How to Write a Thread on X That People Finish - Write an X thread with a clear promise, useful sequence, credible evidence, readable pacing and a strong ending, plus structures, editing rules and examples.
- How to Build in Public on X: The SaaS Founder Playbook - A complete build-in-public system for SaaS founders: what to share, what to keep private, how to earn feedback, and how to connect posts to customers.
Sources
- Posting GIFs and pictures - GIF picker, file limits, looping behavior, and upload help.
- How to post on X - Composer and reply basics.