X to Tell Users When Governments Force Limits on Post Visibility
X will tell users when their posts have been shown to fewer people to comply with local laws. The change was disclosed on Sept. 21, 2026. It covers visibility limits applied after government legal demands. TechCrunch
The feature is an expansion of Under the Hood, X's existing transparency tool. The expansion will specifically flag downranking of posts due to government-required filtering, where downranking means a post is made harder to find in feeds, search and recommendations. That puts government-ordered visibility cuts in the same user-facing place as other account and distribution checks.
Delivery is through an export file. Users who posted at least 10 times during the month can use the Under the Hood option to download their aggregate stats as a JSON file, a structured text format that software can read and compare. The expanded file will include which posts were withheld in a country following a legal demand and which country made the request. In practice, that gives an affected author a machine-readable record linking a specific post ID to a specific jurisdiction.
The export connects to X's wider disclosure system. X runs the X Transparency Center for its transparency work. The original transparency report grew into the more complete X Transparency Center. That center includes sections on information requests, removal requests, copyright notices, trademark notices, email security, X Rules enforcement, platform manipulation, and state-backed information operations.
The broader context here is the practical difference between deletion, withholding, and downranking. Deletion removes a post everywhere. Withholding keeps the post but blocks it in the requesting country. Downranking keeps it available but lowers its chance of being found through ranking, recommendations and search. For engineers who build moderation and trust and safety systems, those are three separate enforcement actions with different logging, appeal and audit needs. Putting the second and third into a per-user export narrows the gap between platform enforcement logs and what the author can check.
In my view, the delivery method matters as much as the disclosure itself. A JSON export for relatively active accounts is not a push alert or an on-screen label. It favors detailed record-keeping over speed. It is workable for researchers, journalists and power users who already download and compare structured data. It is less workable for a casual user who will never find the export or read the format. Structured exports scale well and leave a lasting evidence trail, but they leave the work of finding the information to the affected person.
Looking at what this means for platform operations, per-post and per-country detail is the part to watch. Saying a post was withheld in a country after a legal demand, and naming that country, turns an unclear drop in reach into a compliance event with a clear source. It does not settle the tension between operating worldwide and following local law. It makes that tension visible at the level of the individual account. Over the long arc, that kind of visibility tends to improve internal care in labeling enforcement and outside ability to track where and how often governments seek to limit visibility rather than seek full removal.
