Read receipts in groups and who can actually see them

The short version

Telegram handles read receipts three different ways depending on where the message lives: private chats, groups, and channels. There is no single, universal receipt the way people expect from WhatsApp or iMessage. Each of the three shows a different amount of information to a different audience. If you run or moderate a group and someone asks “can you see if I read that,” the honest answer is “it depends which kind of chat we’re in.” The feature genuinely changes shape between the three. Most people never get a straight answer.

Private chats: the checkmarks

In a one-on-one conversation, Telegram uses the same two-checkmark system most messaging apps use, but with a simpler meaning. A single gray check means the message left your device and reached Telegram’s servers. A second check appears once the other person’s client has actually rendered that message on screen, which Telegram treats as “read.” There is no separate “delivered but not read yet” middle state shown to the sender the way some other apps display it. Either the recipient’s app has seen the message, or it hasn’t.

This only works if the recipient has an active session that can receive and render the message. If someone has Telegram installed but hasn’t opened the app in days, the message sits as delivered-to-server, single check, until they open it. You can’t force a read receipt. You can’t fake one from the sending side, either. It’s generated by the recipient’s client, not the server pushing an assumption.

Privacy settings can blunt this. Under Settings > Privacy and Security > Read receipts, a user can turn off sending read confirmations in private chats. When that’s off, your messages to them will show as sent. You won’t get the second checkmark, even after they’ve clearly seen and replied to the message. This is a two-way toggle: if you disable it, you also stop seeing other people’s read status. Telegram is fairly consistent about not letting features spy in one direction only.

Groups: the “seen by” list, capped

Group chats work differently. This is the part that trips people up. Instead of a checkmark on your own message, Telegram gives you a way to check who has seen a specific message: long-press it (or right-click on desktop) and look for the read count or “message info.” Tapping it shows an actual list of member names who have opened the chat far enough to render that message.

The catch is that this list only exists in groups with up to 100 members. Past that threshold, Telegram stops tracking and surfacing individual read state for a message. Once a group crosses the 100-member line, that per-message “who’s seen this” list disappears. There’s no toggle to bring it back, short of the group shrinking under the cap again. This is a deliberate design choice, not a bug. Keeping a live seen-by list per message across thousands of members would mean storing and syncing a huge amount of read-state metadata, for something most large groups don’t need moderators poring over anyway.

Anyone in a small group, not just admins, can see this read list. It isn’t a moderation-only tool. So if you’re in a 40-person group and want to know who’s actually reading announcements versus scrolling past them, any member can check that on any given message. That’s worth knowing before you post something you’d rather not have visibly ignored by half the group.

Channels: aggregate views, no names

Channels are the third and most different case. Channels show a view counter, the little eye icon with a number next to each post, but that number is an aggregate and anonymized. There is no list of who viewed a channel post, no way for an admin to click through and see which subscribers opened which announcement. It’s closer to a broadcast metric than a receipt. If your workflow depends on knowing which specific person saw a channel post, Telegram simply doesn’t expose that. That’s by design: channels are built around one-to-many broadcasting, where subscriber anonymity is part of the product.

Secret chats

Secret chats, Telegram’s end-to-end encrypted mode available in private one-on-one conversations, still show the checkmark system, but they add self-destruct timers on top. Read status matters more here, operationally. A message’s countdown to deletion can start once it’s marked as read on the recipient’s device. Outside of that timer interaction, the read indicator behaves the same as in a normal private chat.

What proxies and multiple sessions change, and what they don’t

Since telegramvault.org deals with hosting and proxy configuration for Telegram accounts, it’s worth being direct about a question we get: does routing traffic through a proxy or a different IP hide read status. It doesn’t. Read receipts are generated client-side, based on whether the app has rendered the message, not on network path. A proxy changes what IP Telegram’s servers see your connection coming from. It has nothing to do with whether your client marks a message as read once it’s on screen. If you’re running an account through a proxy for connectivity reasons (blocked regions, latency to Telegram’s data centers, keeping a consistent exit IP across sessions), the read receipt behavior is identical to running the same account with no proxy at all.

Multiple active sessions do matter here, in a way people don’t expect. If you’re logged into the same account on a phone and a desktop client, opening a message on either device is enough to trigger the read checkmark for the sender. It’ll show up in a group’s seen-by list too. There’s no way to open a message on one device “quietly” while leaving it unread on another. Read state is tied to the account, not the specific session or device.

Practical takeaways

If you’re moderating a community and want engagement data, the seen-by feature only helps you while the group is under 100 members. Plan around that cap rather than being surprised when it vanishes after a growth spurt. It’s expected behavior once you cross the threshold.

If you’re a member worried about being tracked reading things you’d rather scroll past silently, the private chat toggle under Privacy and Security lets you opt out, at the cost of losing visibility into others’ read status too. Groups don’t offer that same opt-out. If you’re a member of a sub-100-person group and open a message, your name shows up in that list regardless of your personal read receipt setting. The private chat toggle does not extend to groups.

And if you’re trying to figure out engagement on broadcast content, channels won’t give you names, no matter what settings are adjusted. View counts are the ceiling of what Telegram will expose there. That’s consistent with how channels are built to work at scale.

None of this changes based on which client you use, which proxy your account routes through, or how many sessions you keep alive. It’s server-side logic, tied to chat type and group size. Understanding which of the three buckets a conversation falls into is really the whole answer to “who can see that I read this.”

If you’re setting up Telegram infrastructure and want the account safety and connectivity side handled properly, telegramvault.org covers hosting, proxy configuration, and the operational details that keep accounts stable.

Get new guides and videos first — join the Telegram channel.