Loading page
Loading page
Three steps for you, and a short, deliberately boring sequence on our side. This page describes both, because knowing what a tool does with your data is a fair thing to want before using it.
Demo links
Your side
Nothing to configure, and no decisions until the options appear.
Use the share menu on the post, or copy the address bar in a browser. Tracking parameters are fine — we strip them.
Both x.com and twitter.com links work, with or without www. We check the link before sending anything.
Every option shows format, resolution and size. Tap one and your browser saves the file where it normally does.
Our side
Four things, in order. There is no fifth.
We confirm it is an X or Twitter post permalink and pull out the post id. Anything else is rejected here, which also means a link can never be used to make our server fetch some other address.
Tracking parameters are stripped, the host is standardized and what remains is a plain https://x.com/user/status/id. That normalized form is what gets stored, briefly, never your raw input.
A single request asks which files the post contains. Back comes a list — resolutions, formats, sizes — which we hand to the page in one consistent shape regardless of where it came from.
This is the part people assume works the other way. The media does not pass through our server; when you tap a quality, your browser fetches that file directly. It is faster, and it means we never hold a copy.
Short version: a normalized link for a day, and counters with nothing personal in them.
Each lookup writes one row: the normalized link, the post id, whether it succeeded, how long it took, and how many files were found. The link is removed automatically after twenty-four hours, leaving the row as a bare statistic.
Your IP address is never written down in readable form. For rate limiting we need to tell one visitor from another, so the address is put through a keyed hash and only the result is stored — enough to count requests, not enough to identify anyone or to reverse.
There are no tracking cookies, no advertising profile and no account to attach anything to. The privacy policy sets this out formally, and it describes what the code actually does.
A tool is more trustworthy when it is clear about what it will not do.
Only publicly readable posts can be processed. Protected accounts, deleted posts and age-restricted content all fail, and they fail with an explanation rather than a spinner that never stops. Those limits are not technical gaps we intend to close.
We also do not re-encode anything. If a post has no 1080p file, no 1080p option appears — inventing one by upscaling would produce a bigger file that looks the same.
Every tool on this site runs the same resolver — pick whichever matches what you are trying to save.