Skip to main content

Understanding media controls on X

Twitter Sensitive Content: Settings, Warnings and Visibility

Updated

Twitter sensitive content settings control several different things. You can allow sensitive media in your own view and still have it filtered out of search. You can also change a viewing preference without changing the warning other people see on your posts.

That explains a lot of the “I changed the setting and nothing happened” frustration. The switch may have worked perfectly, just on a different part of the problem.

Before changing anything else, identify what you're trying to fix: a hidden image, a missing search result or a label on your own account. Each needs a different check.

Three settings that are easy to confuse

These controls use similar language, but point in different directions. Enabling a display preference allows eligible media; enabling a hiding preference filters it out.

SettingWhat it controls
Display media that may contain sensitive contentYour ability to view eligible sensitive media. It doesn't remove the source post's label.
Hide sensitive contentWhether potentially sensitive posts are filtered out of your search results.
Mark media you post as containing material that may be sensitiveThe declaration for your own uploads, rather than what you want to see from other people.

X documents viewing preferences, safe search and upload labelling separately. Treat them as separate choices when troubleshooting, too.

If a colleague says your product screenshot has a warning, changing what you are willing to view won't fix their experience. Likewise, marking your own uploads as sensitive won't unlock somebody else's image.

How to see sensitive content on X

On the website, the relevant area is Settings and privacy → Privacy and safety → Content you see. Enable the display option from the table above if you want to view eligible sensitive media. To include potentially sensitive posts in searches, check Search settings separately and disable the hiding option.

If your intention is the opposite, to see less sensitive material, reverse those choices: disable the display preference and keep the search filter enabled. “Turn off sensitive content” is an ambiguous instruction, so follow the setting's actual wording rather than the title of a tutorial.

A missing control in the app is a reason to inspect the same account on the website. X's media guidance directs iOS users to the web, and its notice documentation still describes sensitive-media warnings that cannot be opened in the iOS app. A browser comparison is useful; promising that every warning will disappear from the app afterward is not.

Use the same post URL and account for that comparison. Looking at a different post in a different account changes too many conditions to tell you whether the app was the problem. If the original opens on the web, note the difference and use that view where available. If both show an age notice, follow the age-related process instead.

Changing a display preference doesn't make restricted material universally available. It also doesn't alter anyone else's preferences. A screenshot of a post opening normally for you is not proof that every reader can see it.

Why the warning can remain after you allow sensitive media

An age restriction is more than a viewing preference. X's adult-content policy says under-18 viewers and accounts without a birth date cannot open marked adult content. That is one reason a checked display option can coexist with a blocked image.

Providing a birth date to X is separate from publishing it to your followers. The birth-date visibility controls let you restrict who sees the day and month separately from the year. X says dates entered after January 2022 default to private visibility. Check the audience settings instead of assuming that supplying your age requires showing your birthday publicly.

In places where X applies age assurance, a profile date may not be the whole check. Its age-assurance documentation describes using existing account signals, estimation and, where needed, a verification flow. Access may remain restricted until X can determine that a person meets the relevant age threshold.

If X has incorrectly classified an adult account as under 18, that documentation directs the account holder to challenge the decision through X Support in the app or website. Follow the process attached to the account's notice. Repeatedly toggling a media preference won't resolve an age classification.

Read the notice before treating it as a broken setting. An age warning, a country restriction and a notice about removed content describe different conditions. The useful next action depends on which one X is actually showing.

A direct link opening successfully tells you that the post is available to that viewer. It doesn't tell you whether the same viewer's search filters permit it in results.

X's search guidance separates sensitive-content filtering from the option that removes muted and blocked accounts. It also says search preferences apply across web, iOS and Android. Switching devices can therefore preserve the filter you're trying to diagnose.

To test one missing result, keep the account, query and result tab unchanged. If you choose to disable sensitive-content filtering, change only that option and rerun the search after allowing the setting to take effect. X notes that changes can take several minutes. Restore your preferred filter afterward if the change was only for diagnosis.

“This post appears when I change one search filter” is a useful finding. “Search looked different after I changed three settings and switched accounts” is much harder to act on.

If the result remains absent, don't keep treating the sensitive-content switch as the only possible cause. X's search troubleshooting page names other factors and explicitly says not every post will appear. Protected posts also require the appropriate access. Our Twitter search troubleshooting guide covers query restrictions, dates and result views without confusing them with media labels.

Why your own tweets receive a sensitive-content warning

For uploads, check Privacy and safety → Your posts. X's media guide describes labelling by authors and by its own review or detection systems.

For an occasional image or video, use the flag control while editing the attachment to apply a one-time warning. That labels the individual post.

For accounts regularly publishing adult content, the adult-content policy calls for the account-wide setting, which places images and videos behind warnings. The same policy excludes some educational, medical and artistic material from its adult-content definition. Context matters, and exemption from that category doesn't settle whether a different policy applies.

For example, a medical explanation may be educational while its accompanying footage is still graphic. X's violent-content policy addresses graphic medical procedures and injury imagery separately. Evaluate the actual image or video, not just the harmless intent of the caption.

Nor does adding a warning make every upload permitted. That policy prohibits some severe violent material, while the adult-content policy restricts where adult imagery can appear, including profile pictures and headers. A warning is a way to handle eligible material, not permission to ignore the underlying rules.

Can you remove a sensitive-content label?

X's media guidance says changing account settings won't clear labels already applied to images. Repeated mislabelling can also lead to a permanently imposed account-wide setting.

If you enabled the upload setting by mistake and can still change it, correcting it addresses that setting. Check an affected post separately before assuming the old warning has gone. Avoid deleting and reposting a whole history simply to test a theory about a label.

For an enforcement decision you believe is wrong, use the review or appeal route offered with that notice. X's enforcement documentation describes appeals on visibility-limitation labels. It doesn't establish that every kind of sensitive-media warning has the same button or review process.

Make a review request specific. Include the affected URL, the wording of the notice, the relevant policy distinction and a short explanation of the context. For instance, explain why a particular educational image has been misclassified rather than submitting only “my account is shadowbanned.” Keep a copy of what you submitted and any response.

There is no basis in these documents for promising that a label disappears after a particular number of quiet days. X even publishes a review outcome explaining that a label was retained. Treat a review as a request for a decision, not a guaranteed reset.

What a sensitive-content warning means for reach

There are two distinct reasons fewer people might encounter labelled material. Some viewers filter it out. Separately, X may restrict distribution. Its retained-label notice says an affected account and its content may be excluded from timelines, recommended notifications, trends and search results.

That notice describes possible consequences of the account label under review. It doesn't establish that every self-labelled photo receives all of those restrictions. X also lists certain sensitive-media warnings among actions on content that doesn't violate its rules. A warning is not, by itself, proof of an account suspension.

If you're investigating a drop in reach, separate what you can observe from what you're inferring. Record whether the direct post opens, whether a warning appears, whether an eligible viewer can find it in search and whether X sent an account notice. A lower impression count cannot tell you which of those changed.

Our Twitter shadowban guide goes further into visibility checks. The important point here is to follow the specific evidence. One sensitive image, an account-wide label and a missing reply are not interchangeable diagnoses.

A useful check before changing more settings

Choose one affected post and save its URL. Note the account you're using, the client, the warning text and whether the problem occurs on the direct post, the profile or in search. Then make one relevant comparison. This gives you a repeatable example instead of a vague impression that the whole account is broken.

If the same account can open that post in a browser but the app fails, investigate the client difference. If the browser itself fails to load or save settings, X's web troubleshooting guidance covers browser updates, extensions and stored site data. Those checks address a malfunctioning page; they don't overturn an account decision.

If your goal is simply to see less of a disturbing topic, media filtering may be too broad. X also offers account and keyword muting. Those controls let you address the source or subject, rather than expecting a sensitive-media label to cover everything you'd prefer to avoid.

Once you have identified the cause, stop changing unrelated settings. A search preference calls for a search adjustment. A mistaken age classification calls for an age review. A label on your upload calls for checking that upload and its notice. Getting that distinction right is usually more useful than another round of switching every media option off and on.

Research checked October 7, 2026 against X's linked Help Center documentation. Controls and availability can vary by client, account and location. Troubleshooting examples are editorial guidance, not tests of a particular reader's account or promises that a label will be removed.