What this guide is really about
Threads privacy is mostly one switch, and it works the same way in the app and on the web. Switch it on to require approval for new followers and limit who can see your posts.
But the switch is blunt. Some things go private, some things stay public no matter what you do, and one older feature, fediverse sharing, carries a catch that trips people up.
This guide covers the exact steps, what changes, what does not, and which control fits your actual problem better than a private profile.
Open the Threads app and tap your profile picture in the bottom right, then the Menu icon at the top right. Tap Privacy, then Private profile. Tap the toggle next to Private Profile and tap OK. On the web, click More on the left, then Settings. Click Privacy, then Private profile, and click the toggle. Click OK. The same toggle switches you back to public whenever you want.
The toggle lives under Menu or More, then Privacy, then Private profile, in both the app and the web.
Private means approved followers only for posts, reposts, and quotes, plus no story shares and no embeds.
Your photo, name, username, and bio stay public, links to your posts still work, and existing followers keep access.
Going private turns off fediverse sharing, and turning it back on requires a 30-day wait from the day you flipped.
If one person is the problem, restrict or block them instead of locking your whole profile.
The Switch: Exact Steps in the App and on the Web
In the app, tap your profile picture in the bottom right, then the Menu icon at the top right. Tap Privacy, then Private profile. Tap the toggle next to Private Profile, then tap OK to confirm. The same toggle reverses the change whenever you want out. These steps match the official switch guide on the Instagram Help Center.
On the web, click More on the left, then Settings. Click Privacy, then Private profile. Click the toggle, then click OK. One note on age: new profiles for users under 18 are Private by default, and teens aged 16 to 17 can change that setting themselves.
What a Private Profile Actually Changes
The first change is who can follow you. On a public profile, anyone on Threads can follow you without approval. Private means only people you approve can follow you, and each new follower waits for your yes. Meta's table of public and private profile differences is the source for this section.
Your follower and following lists change audience too. On a public profile, anyone on or off Threads can see who follows you and who you follow, including people browsing from other Meta products like Facebook. On a private profile, only your followers on Threads can see those lists. If you follow sensitive accounts or simply keep your circle quiet, that is part of what the gate closes.
Posts change audience next. Public means anyone on or off Threads can see what you write, including people on other Meta products like Facebook. Private means your posts are visible to your followers on Threads and the individual people you reply to. Reposts and quotes follow the same split: followers only while private, anyone while public.
Two sharing routes close as well. Nobody can share your threads to their Instagram or Facebook story once you are private, and nobody can embed your posts off Threads. Public profiles allow both, to anyone. These limits reduce two ways other people can redistribute your posts.

What Stays Public No Matter What
Going private does not hide who you are. Your profile photo, name, username, and bio stay public in both modes. Anyone can still land on your profile, see those four things, and send a follow request. If your goal is to disappear, this toggle will not get you there. If your real goal is not being found rather than not being read, edit those four fields first: a pen-name display name, a neutral photo, a handle without your city or surname, and a bio with no employer. The privacy toggle and the profile cleanup solve different problems, and most people who want one also want the other.
Links are the second surprise. Anyone can still share a link to your threads, and the link keeps working. Sharing a link does not make a private post generally visible: your Threads followers can see your posts, and individual people you reply to can see those replies even if they do not follow you.
Existing followers keep access too, and this is where people get burned. Going private does not remove anyone who already follows you. If that person already follows you, going private does not remove their access. There, restrict and block work better when the problem is one person, and you keep your public reach.
Assuming private hides your identity. Your photo, name, username, and bio stay public in both modes.
Going private to shake one person. Existing followers keep access, so restrict or block them instead.
Expecting fediverse content to vanish. Meta only requests deletion, and copies can stay visible on other servers.
Ignoring the 30-day rule. Fediverse sharing stays locked for 30 days from the day you went private.
Locking the whole profile when a lighter control fits. Hidden words, reply controls, or ghost posts often solve the real problem.
The Fediverse Catch
Threads can share your posts to the fediverse, the network of servers beyond Threads itself. If fediverse sharing was on, switching to private turns it off. Meta requests that those servers delete your content but cannot guarantee deletion. Copies may stay publicly visible elsewhere, out of reach of any Threads setting. That is the short version of what Meta says happens when you switch.
A timing rule follows you back. If you return to public later, you must wait 30 days from the day you went private before fediverse sharing can be turned on again. The clock starts when you flip to private, not when you return.
The practical reading is to assume the worst. Treat anything already shared to the fediverse as potentially still out there. Going private stops new posts from traveling to those servers. It does not reliably erase what already left, so plan around copies instead of a clean slate.

Match the Control to the Problem
Private mode is one tool on the wall, and often not the right one. Match the control to the problem instead. One person bothering you calls for restrict or block. Specific words in replies call for hidden words. A too-visible presence calls for turning off your active status. Who can reach your inbox is a message request settings question. Some posts need no lock at all, just a shorter life.
That last case is what ghost posts are for. Threads offers ghost posts that disappear after 24 hours from feeds and stay in your archive. Replies from people you do not follow go to message requests when those are enabled; with requests off, they cannot reply at all. It is a lighter touch than a private profile, since your account stays open. For inbox control, the settings for who can send you message requests decide who reaches you.
Presence and likes have their own dials. If the green dot is the issue, the guide to turning off your active status solves exactly that. If likes are the worry, the settings for hide like counts and like privacy cover it.
Three situations make the mapping concrete. A photographer getting creepy comments from one account needs block, not a private profile, because closing story shares and embeds punishes every other follower. A small bakery that suddenly gets quote-bombed by trolls needs hidden words and reply controls, because the whole point of the account is walk-in discovery. A therapist who posts professional takes but wants old classmates out needs the private toggle, because the gate is the product. One control per problem, and only the last one needs this article.
Before You Flip It: The Reach Trade-off
Everything private mode removes is a discovery surface. Per Meta's own comparison table, a private profile loses story shares, loses embeds, and gets reposts and quotes limited to followers. Those are the paths your content travels: other people's stories, other websites, and amplification from strangers. Locking them narrows how far new people can find you.
If you post to be found, measure before you lock. Write down your engagement baseline now, then compare after a few weeks private. An engagement rate calculator turns before and after into numbers instead of a feeling. If discovery was the point and the numbers sink, the same toggle reverses the decision.
There are middle paths, too. If the problem is unwanted replies, reply controls fix that while you stay public. If one person's access is the problem, removing or blocking them is the narrower fix. If personal posts are the worry, you can add another Threads profile and switch between them, one public for reach and one private for life.
If you want a 60-second decision, ask in order. Is one person the problem? Block or restrict them and stop there. Are the replies the problem? Hidden words and reply filters handle that. Is your presence the problem? Turn off active status. Is everything the problem, and would you rather lose discovery than keep the gate open? That is the only case where the private toggle wins, and now you know exactly what it closes on the way out.
Action checklist
Use this as the practical next pass after reading the guide.
- +Flip the toggle: Menu or More, then Privacy, then Private profile, then OK.
- +Audit existing followers and remove or block anyone who should not keep access.
- +Assume fediverse copies already shared may stay public, and note the 30-day clock starts today.
- +Restrict or block the specific person if the problem is one person.
- +Record your engagement baseline before switching so you can judge the reach cost later.
- +Tell close friends to send follow requests, because new followers now wait for approval.

Conclusion
Making your Threads account private takes one toggle and a few seconds, in the app or on the web. It requires approval for new followers, limits post visibility to your Threads followers and the people you reply to, prevents story shares and off-Threads embeds, and hides your follower list from non-followers.
It does not buy anonymity. Your photo, name, username, and bio stay public, links still work, and fediverse copies can outlive the switch.
Match the tool to the problem. One person needs a block, messy replies need hidden words, and only a full-profile gate needs the private toggle.



