X automatically loops short videos, and both official pages that document it put the boundary at 60 seconds — they just disagree on whether 60 seconds itself is inside the rule or outside it.
X's help centre page on sharing and watching videos states it one way: "All videos posted to X that are 60 seconds or shorter will automatically loop." X's Ads creative specs page states it the other way: "Looping: Videos will loop if the video length is under 60 seconds."
Those two sentences agree about every clip except one: the clip that lands exactly on 60. "60 seconds or shorter" includes it. "under 60 seconds" excludes it. If you are cutting a loop on purpose — a product shot, a reaction, a seamless animation — that single word is the whole decision.
The two official sentences, at a glance
| Official page | Verbatim wording | Does exactly 60s loop under this wording? |
|---|---|---|
| Help centre, "How to share and watch videos on X" | "All videos posted to X that are 60 seconds or shorter will automatically loop." | Yes |
| X Ads creative specs, Vertical Video Ads | "Looping: Videos will loop if the video length is under 60 seconds." | No |
The scopes are not identical either, and that matters when you decide which line to trust. The help centre sentence sits in a general FAQ about videos posted to X. The Ads sentence sits inside the creative specifications for an ad format. Neither page references the other, and X does not publish a page that reconciles the two. If the exact boundary is load-bearing for your edit, check the official documentation before you build around it.
Why the mechanism matters more than the number
Looping is a playback behaviour, not an upload limit. Nothing about the 60-second line changes whether your file is accepted — X's upload caps are a separate set of numbers entirely, and they vary by account tier and by which of X's pages you read. We walk through all of them in how long a video can be on X. So "make it loop" is an editing decision you make before export, not a setting you toggle at upload time.
The practical rule: land at 59 seconds, not 60
Here is the judgement, and it is not a compromise — it is the one length both official sentences agree on.
- Target 59 seconds or less. Any clip at or below 59 seconds loops under either wording. You get the behaviour without depending on which page is authoritative.
- Avoid landing exactly on 60. This is the only value where the two pages contradict each other, and X publishes no tiebreaker.
- Above 60 seconds, looping is off under both sentences. There is no partial case.
If your cut is sitting at 60 or 61 seconds, trimming two seconds off the tail is almost always cheaper than any other fix. Loop content usually has a natural in-point and out-point anyway, and shaving the last beat is invisible to a viewer who is about to see the clip restart.
When a GIF is the better format
If the clip cannot be trimmed under the line, or you want motion that repeats without any player chrome, the other route is to post it as an animated GIF. X treats a GIF as a separate media type from video, with its own caps — X's developer documentation lists animated GIF size at <= 15 MB, against 5 MB for a still image.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs entirely in your browser tab: the video is read from disk, converted locally, and handed back. Nothing is uploaded to a server, which matters when the clip is a client draft or something unreleased.
Before you convert, know that X's documentation is explicit that file size alone does not decide whether a GIF posts. Quoted verbatim: "A GIF may fail during Post creation even if it is within the file size limit." Four constraints are listed together:
| GIF constraint | Official value |
|---|---|
| Resolution | <= 1280x1080 |
| Number of frames | <= 350 |
| Number of pixels | <= 300 million (width * height * num_frames) |
| File size | <= 15 MB |
The frames and total-pixels rules are the ones that catch people, because neither is visible in a file manager. A 350-frame ceiling is a hard cap on duration times frame rate, so a GIF is realistically a short loop, not a minute of footage. We break down all four checks in why an X GIF is rejected when it is under 15 MB.
One scope warning: on the Ads side, X's creative specs page states "Note: GIFs uploaded will render as a static image." That sentence is about ad creatives, not organic posts — do not generalise it, but do know it exists if you are building a paid placement.
How to choose: keep it as a video if it has audio, if quality matters, or if it is longer than a few seconds of motion. Convert to GIF only when the clip is short, silent, and visually simple enough to survive the frame and pixel caps. Our MP4 to GIF converter applies the same constraints locally so you can check the result before posting.
Other things X's pages actually say about short video posts
A few adjacent rules that come up constantly whenever someone is building a short looping post:
- One video per post. X's developer documentation states: "You may attach up to 4 photos, 1 animated GIF or 1 video in a Post." You cannot post a loop next to a GIF, or two loops side by side.
- The video does not eat your text. From the help centre FAQ, verbatim: "No, videos do not count towards the character limit in a post."
- Clickable timestamps need a solo video. X states they "will only be visible on posts that have 1 video attached," are not clickable on posts with multiple videos or a video plus an image, and that "for now timestamps are only clickable on iOS. Android and Web are coming soon." The maximum is 50 per post.
- Playback resolution depends on the account. X's documentation states: "Subscribed users can upload a 1080p video and get 1080p playback. Unsubscribed users can upload a 720p video and get a 720p playback."
That last one is worth pairing with looping, because a loop is the format people rewatch. If the file is bulky enough that you are tempted to cut quality, compress it deliberately rather than letting it get squeezed by accident — X's help centre notes it may "modify or adapt your original video for distribution," including "modifying the resolution and bitrate of the original video while streaming based on the speed and stability of the viewer's internet connection."
FAQ
Do X videos loop automatically? Yes, for short videos. X's help centre states that videos "60 seconds or shorter will automatically loop." X's Ads creative specs page words the same rule as "under 60 seconds," so the two differ only at exactly 60.
Does a video that is exactly 60 seconds long loop on X? It depends on which official page you read, and X publishes no page that settles it. Cut to 59 seconds or less and both wordings agree the clip loops.
How many times does an X video loop before it stops? X's documentation does not state a repetition count in the pages cited here — only that qualifying videos loop. Check the official documentation if you need a specific number.
Can I turn looping off for a short video? X's documentation does not describe a setting for this. The only stated condition is length. If you need a definitive answer, check the official documentation.
Should I post a short clip as a GIF instead of a video?
Only if it is short, silent, and simple. A GIF on X must satisfy four constraints at once — <= 15 MB, <= 350 frames, <= 1280x1080, and <= 300 million total pixels — and X warns that a GIF can still fail even when it is inside the size cap.
Does looping inflate my view count? X's documentation does not state how loop replays interact with the post view counter. Do not assume either way.
All figures quoted from X's help centre, X's developer media documentation, and X's Ads creative specs, checked 21 September 2026. X's own pages disagree on the 60-second boundary, so verify against the official pages before building an edit around it. More on platform caps in our limits guides, and the full browser-based toolkit is at Clapr tools.
