Looping clips posted to X, saved as the MP4 that X actually stores them as. Saved to the Downloads folder in the Files app.
Save any public X post as GIF directly to your Chromebook. Looping clips posted to X, saved as the MP4 that X actually stores them as. Everything happens in the browser, so nothing needs installing on a managed device. The whole process happens in Chrome, so there is nothing to install on ChromeOS and no account to create. Below: where the file lands, what opens it on a Chromebook, how large it will be, and what to do if it does not arrive.
The download goes to the Downloads folder in the Files app. Open the Files app from the launcher and click Downloads. On a Chromebook this folder lives in local storage, so it does not sync to Drive unless you move it there.
Because the file is written straight to storage rather than into an app’s private sandbox, anything on ChromeOS that can open GIF can reach it. There is no library to import into and no proprietary folder to dig through.
GIF opens in the built-in ChromeOS media player and any Android video app, and more broadly on every messaging app, including WhatsApp, Telegram, Discord and iMessage, all of which prefer MP4 over true GIF.
This is the practical reason GIF is offered at all. What X calls a GIF is not a GIF file. X converts every uploaded GIF to a silent MP4 on upload, because MP4 is smaller and smoother. You get that MP4, which is both what X stores and what messaging apps want. If a file has to work on a device you do not control, or software old enough that nobody updates it any more, GIF is the option least likely to be refused.
You are downloading H.264 video, silent, usually a few seconds long. Looping clips posted to X, saved as the MP4 that X actually stores them as.
It is worth being precise about what that means for quality. X re-encodes everything uploaded to it, so the source already sits one generation below whatever was originally recorded. Nothing here can recover that. What is within our control is not adding a second generation, and the video path avoids it entirely by copying rather than converting.
If your Chromebook is managed by a school or workplace, downloads may be restricted by policy. Nothing here can work around that, and you should not try to: the restriction is on the device, not on the website.
If the post will not load at all, the account is the usual explanation rather than the device. Protected accounts, deleted posts and region-restricted posts cannot be read, because the media is not publicly available to fetch. Copy the link from the post’s own page rather than from a quote, a notification or a search result, and most remaining failures clear up.
Copying links gets tedious after the third or fourth video. There is a shortcut: in the address bar of any X post, replace x.com with downloadthisx.com and press enter. The download page opens with that post already read, so there is no copying and no pasting.
On Chromebook this works in Chrome exactly as it does anywhere else. It is the same page you are on now, reached by a different route.
Only public posts can be read. Protected accounts, direct messages and anything sitting behind a login are out of reach by design, not by oversight.
Saving a clip for yourself is ordinary. Republishing someone else’s work as your own is not, and downloading it does not change who owns it. The author keeps the copyright whatever folder the file ends up in on your Chromebook.
Open the post in X on your Chromebook and right-click the timestamp on the post and choose Copy link address.
Open this page in Chrome and paste the link. The post is read automatically.
Select GIF and the file saves to the Downloads folder in the Files app.