Restricted on Instagram: who sees what, per side
· AnonSight
What does restriction change, and for whom?
Restrict is a flag. One account sets it on one other account, and Instagram then routes part of the traffic between that pair differently. It changes routing, not access. Two role names hold for the rest of this page:
- Setter: the account that switched Restrict on.
- Flagged account: the one it was switched on for.
What the flag does, item by item:
- Comments. New comments from the flagged account on the setter’s posts: visible to their author only, until the setter approves them.
- Messages. Delivered to the setter’s message requests, not to the main inbox.
- Activity status. The setter’s online indicator is withheld from the flagged account.
- Read receipts. The flagged account no longer learns whether the setter opened its messages.
- Profile and stories. Untouched. Both keep loading for the flagged account.
- Notice. None. Instagram tells the flagged account nothing.
Four items redirect or withhold a signal. Two leave the old state in place. In effect, the setter filters contact, and the flagged account receives no event about it. A block removes access; a restriction only filters what passes through it.
Stories carry one practical consequence. If the flagged account opens one of the setter’s stories while signed in, that view appears on the setter’s viewer list under its username, as any signed-in view does. How long a name stays readable there is covered in Watched a story? How long your name stays listed.
One boundary note before the cases. AnonSight reads public accounts with no session of yours in the request, so the flag never enters its responses; the section on outside reads spells out the consequence. Reference state for each Instagram behaviour on this page: iOS and Android apps, personal accounts, 24 Sep 2026. A line carrying its own date overrides it.
Four scenarios, two sides each
“You” can sit on either end of a quiet setting, and restriction is only one of the quiet settings. Four cases cover the common confusions. Each row reads the same event from both ends.
| Case | The account that acted sees | The account on the other end sees | Notice sent? |
|---|---|---|---|
| You restricted them | Their new comments wait for your approval; their messages collect in requests | Your profile loads, stories included; their comments look posted; your online indicator and your Seen marks no longer reach them | No |
| They restricted you | Your new comments wait for their approval; your messages collect in their requests | Their profile loads, stories included; your comment renders for you alone; their status is gone; messages sit at “Delivered” | No |
| They blocked you | On their posts, your likes and comments disappear | Search returns nothing; the profile opens on an unavailable-page notice; a follow attempt fails | No |
| They hid their story from you | Each story reaches its usual audience minus you | The profile opens; their stories do not show for you | No |
Rows one and two are one mechanism read from opposite ends. The setter knows the flag exists; the flagged account can only infer it, from side effects, which is the subject of the next section.
Column four gets checked first and carries no information: “No” in all four rows.
The signal sits in the far-end column: does the profile load for you, and do the stories play? For the account on that end, those two observations sort the cases:
| Profile loads for you? | Stories play for you? | Cases that fit |
|---|---|---|
| No | Nothing to play | A block, or a change to the whole account |
| Yes | Missing | A hidden story, or simply no story posted in the last day |
| Yes | Yes | A restriction is possible; so is no setting at all |
Row one has several causes besides a block, and the full set of in-app block signals, none decisive alone, is sorted in Blocked or gone for everyone: the scope test. Row two is the hide-story setting or an empty story tray. Hiding sends the excluded account no alert. Rarer reasons why one account’s stories fail to appear for you are listed in One person’s stories won’t load: five causes.
Row three is the restriction row. It also fits two accounts with no setting between them at all. The table narrows the candidates to two.
Mute: outside this page’s reference state. The table states nothing on it.
Indirect signs, none conclusive
This part covers the flagged account. No label, banner or message announces the flag. What reaches this role are the side effects of the four rerouted items, and each has a limit.
Comment reach. Your new comment under their post renders on your screen and is missing for other viewers. Limit: on your own screen the comment looks posted, so the sign exists only in someone else’s view of the post. It is the sign most specific to restriction, and it is still a sign.
Activity status. Their online status stops appearing for you. The limit here is that any account can turn off its activity status; that switch also blanks every other account’s status for whoever flipped it. Globally quiet accounts produce exactly this pattern.
Message state. Your messages arrive in the chat and stay at “Delivered”. But an unopened message shows the same state. So does a message opened by someone who disabled read receipts: a single setting for all chats that applies to sender and reader alike. Output from the app is identical in both cases.
Profile access. No change here: their page resolves for you and the stories play. This is not evidence of a restriction. It is evidence against a block.
That makes three signs, each also produced by an ordinary setting or an unopened chat, plus one observation that rules a block out. With all three present, restriction ranks first among the candidates, still unconfirmed.
Maximum confidence from these signals: possible. The restriction itself is never in the payload the flagged account receives.
Turning restriction on or off
The setter applies Restrict per account, one at a time, and can lift it the same way. This page gives no tap sequence: menu positions move between app versions, and no path was recorded for it on the check date. The current route in both directions is documented by Instagram in its help article on Restrict.
The flag leaves access unchanged. Story visibility per person is a separate setting (row four above).
Why no outside read detects it
Restriction state: stored per pair of accounts. It takes effect only in responses served to a signed-in session of one of the pair, namely comment filtering, message routing and two withheld status signals.
A lookup here, traced field by field:
- Request: a handle.
- Session of yours: none.
- Response: the public profile, limited to items its owner made public.
- What a restriction check would need: a session belonging to the setter or to the flagged account.
- In this request: neither.
An outside service that reports a restriction has no such field in its response to read it from. You can look over a public account from a browser and learn what that account posted; how it treats one follower or one stranger is not part of the response.
Not for: anyone who wants an outside viewer to confirm that a specific person restricted them. This page cannot do that, and it offers no workaround to force an answer out of the app either. The indirect signs listed above are the whole of what is observable, and they stop at “possible”.
Restriction questions, verdict first
What changes for the person I restrict?
Four routes. Fresh comments they leave on your posts are shown to them only, pending your approval; their messages land in your requests; your online indicator and Seen marks stop reaching them. No notice is sent to them for any of the four.
Does a restricted person still see my stories?
Yes. A restriction leaves your profile open to that account, stories included. Scope of the flag: comments, messages and two status signals. Viewing works as before. Hiding stories from one person is a separate setting, the fourth case in the table above.
Which signs suggest I’ve been restricted?
Three, all indirect. Your new comment shows for you but not for others, their online status disappears, and your messages sit at “Delivered”. Ordinary causes explain each one as well, so none settles the question.
How does a restricted account appear on my side?
Held back: its new comments come to you for approval instead of posting openly, and its messages arrive among your requests instead of the primary inbox. Other surfaces on your side were outside the check, so nothing is claimed about them.
Blocked or only restricted: what differs for me?
Profile access. After a block, their profile is unavailable to you and search finds nothing; with a restriction, their page still resolves, stories too. Either way, notice sent: none.
Can an outside viewer detect a restriction?
No. The flag sits between two signed-in accounts and changes only what those two sessions receive. A lookup here carries no session of yours and returns only public material, so its response is identical with or without a restriction in place.