Choose who your posts are for
How to make Twitter private and understand what changes
You want more control over who reads your posts. Before changing your account, check the audience you already have and the history you would expose if you go public again.
On this page
Choose the audience before changing the setting
People you did not expect are reading your Twitter posts. You want a smaller audience, but you also want to understand what happens to the people who already follow you and the posts you have already shared.
To make Twitter private, turn on Protect your posts in X's privacy settings. Protected posts are limited to followers, and new followers need approval. This changes who can read your work; it does not delete your publishing history.
Decide what you need before touching the control. If you only want to end one follow relationship, the follower removal guide addresses that narrower task. If you want to choose who can reply to a particular post, review reply settings. Neither is the same as changing the whole account's audience.
For a creator, privacy can matter more than discovery. You do not need to keep personal material public to meet a posting goal. Write down who you want the account to serve, then choose the setting that fits.
Turn on Protect your posts in X
X's protection instructions document this mobile route:
- Open your profile menu and select Settings and privacy.
- Open Privacy and safety.
- Find Audience and tagging.
- Turn on Protect your posts and check that the control is enabled.
Labels and the switch's appearance can vary by app version. Use the named privacy control rather than an unrelated setting that only changes what appears in your own feed.
Before changing anything, confirm that you are signed into the intended account. If you manage a public work account and a personal one, pause long enough to check the handle. A correct setting on the wrong account will not solve the audience problem you meant to address.
After saving, revisit the control. Seeing a post while signed into its author's account is not a useful test of what an unfamiliar reader can access.
Review existing followers and new requests separately
People already following you retain access when you protect your posts. Review that existing audience separately if your concern involves someone who is already there.
For new requests, X's follower request guide directs you to your profile menu's Follower requests list. Approve or deny the requests there. Public accounts do not use this approval flow.
Take each request on its own merits. A recognizable photo or a large follower count does not establish why someone wants access. You can leave a decision until you know whether you want that person in the audience.
If you expected a request but cannot find it, confirm the account's current privacy state before treating the list as broken. X notes that a requester can cancel a request; an earlier email is not proof that it is still pending.
Keep this separate from interpreting follower growth. Choosing a smaller audience is a boundary decision. A lower count afterward is not, by itself, evidence that your latest writing failed.
Understand the sharing and search limits
X's public and protected posts guidance describes these differences:
| Question | Public posts | Protected posts |
|---|---|---|
| Who can read the post? | Anyone. | Your followers. |
| Where is it searchable? | Public search can surface it. | X search is limited to you and followers; protected posts are excluded from third-party search engines. |
| Can followers use the repost control? | Reposting is available. | The repost and quote controls are unavailable. |
| Will a reply reach someone who does not follow you? | The reply is public. | That person cannot see your protected reply. |
Protection is not a promise that a copy cannot leave the account. Followers can capture posts. X also warns that direct media links are not protected, so someone with such a link can view the media.
Making previously public posts protected restricts their visibility on X; it cannot recall copies already shared elsewhere. Avoid putting something in a protected post if you cannot accept the possibility of a recipient saving it.
If your question is why a public post is missing from search, use the search visibility checks instead of toggling privacy as an experiment. A visibility setting should follow your audience choice, not become a reach troubleshooting shortcut.
Review the history before going public again
Turning protection off makes previously protected posts public too. It is not a switch that exposes only your next announcement. Review the older material before deciding whether you want that outcome.
X also says pending follow requests are not automatically accepted when you go public; those accounts need to follow again. Review pending requests before changing the setting, rather than assuming the queue will resolve itself.
A brief note can help you make the choice deliberately:
Intended audience:
Current public or protected state:
Existing followers I need to review:
Older posts I need to review before going public:
Pending requests to decide:
Chosen setting and date:
You can keep the account protected if you are not comfortable exposing its history. A launch date or a quiet week does not require you to change that boundary.
For public posts you choose to review, PilotMyX lets you read collected text beside available impressions and profile visits. Keep original posts separate from your own replies, and retain the metric capture times. If you changed visibility during the period, note the date alongside your review rather than attributing every change in results to the wording.
PilotMyX does not manage this privacy setting. Its metrics are not proof of who could read a protected post, and this guide does not promise collection from a protected account. Decide the audience in X first; use the results of the public work you intended to share to choose a next post worth developing.
Use your own account