How to see who read your message in a WhatsApp group

To see who read your message in a WhatsApp group, tap and hold a message you sent and tap Info; on WhatsApp Web, open the message's menu and choose Message info. The screen lists the members who have read it and those it was delivered to, each with a time. The ticks on the message turn blue only once every member has read it.

Below: the steps on Android, iPhone and WhatsApp Web, what one grey, two grey and two blue ticks mean in a group, why a group message can sit on grey ticks for days, the quirks that make the list look wrong, what the read receipts setting does and doesn't change in groups, and how to compare reads across many groups. Menus are as WhatsApp's help centre gives them on 8 October 2026.

How to open Message info on Android, iPhone and Web

Message info exists only for messages you sent. You can't see who read someone else's message in a group, and nobody else can open the list for yours. On Android:

1. 1Open the group and find a message you sent.
2. 2Tap and hold the message.
3. 3Tap Info (the i in a circle). If it isn't there, tap More options (the three dots), then Info.

On iPhone:

1. 1Open the group and find a message you sent.
2. 2Tap and hold the message, then tap Info.

On WhatsApp Web:

1. 1Open the group and hover over a message you sent.
2. 2Click the menu arrow on the message, then Message info.

The screen lists the members who have read the message, or seen your photo or video, and the members it has been delivered to who haven't read it yet, each with a time. For a voice message it also shows who has played it; someone who has seen a voice message without playing it is listed as having seen it.

What do the ticks mean in a WhatsApp group?

WhatsApp puts ticks beside every message you send. In a one-to-one chat they describe one person. In a group they describe everyone at once, and they only move on when the last member does.

That makes group ticks an all-or-nothing signal. In a 300-member group, 299 readers plus one member whose phone has been off all week, with no linked device online, still shows one grey tick, because the message hasn't reached everyone. The per-person answer is only in Message info.

One more check mark causes confusion. The verified badge some businesses show on their profile, a check mark, comes with Meta Verified, a paid subscription for businesses. It says nothing about whether anyone read your message.

Why is there no blue tick on my group message?

Because blue needs everyone. A group can hold up to 1,024 members, and the more it has, the less likely it is that all of them open the chat; in a large group with a few dormant members, the ticks may never turn blue. The other causes come from WhatsApp's own list of reasons a read receipt doesn't appear:

• Someone hasn't opened the group since you posted. Seeing the message in a notification or in the chat list preview isn't opening the conversation.
• A member's phone is off and none of their linked devices has received it, so the message isn't delivered to everyone and stays on one grey tick.
• There are connection problems on your side or theirs.
• The date and time are set wrongly on your phone or on a member's.

In busy or muted groups, members often catch up days later. Judge a post by its Message info list, not by the colour of its ticks.

Why does Message info look wrong?

Can you turn off read receipts in a WhatsApp group?

No. The switch is at Settings → Privacy → Read receipts (on Android, open More options first). WhatsApp's help centre is plain about groups: turning it off "won't disable the read receipts for group chats or play receipts for voice messages", and there is no way to turn those off. Whatever your setting, people in a group can see when you've read their messages there, and you appear in their Message info lists.

What the switch changes is one-to-one chats. With it off, people there don't get blue ticks from you, you don't see theirs, and you may not see who viewed your status. Read receipts in one-to-one chats covers that side.

For anyone posting to a group, that is useful: a name missing from the read list never means the person switched receipts off. Usually it means they haven't opened the group since you posted, or their phone hasn't reported back yet.

Why a group read count is always a floor

Message info counts the people who opened the group on a device that reported back. It misses everyone who took the message in from a notification, a lock screen or the chat list, and anyone who heard it from someone else. The real audience is at least the number on the screen, and it can be larger. Four habits keep the count honest:

• Compare at the same age. The read list keeps growing for days as members catch up, so compare posts 24 hours after sending, not a fresh post with a week-old one.
• Divide by the group, not by your total. Forty readers is most of a 60-member group and a sliver of a 900-member one, so use the member count at the time you posted.
• Don't read a missing name as a no. It means not opened yet, not rejected.
• Ask when you need an answer. A read isn't agreement; a poll shows who chose which option.

If you want more members to open a post, mention them. WhatsApp's @all notifies everyone in the group, though in groups over 32 members only admins can use it and members can mute it. Tagging everyone in a group covers when that helps and when it annoys.

How to measure reads across many groups

Message info answers one message in one group. If you post the same announcement into twenty groups, open each copy at the same age and note three numbers: members when you posted, how many have read it, and how many have it delivered but unread. One spreadsheet row per group turns that into read rates you can rank, and the groups that sit at the bottom week after week are the ones to question first.

Doing that by hand stops working somewhere past a dozen groups. WavesFlo records delivery and read rates for each group a campaign posts into, per group rather than averaged, reports them over the last 7, 30, 60 or 90 days with a CSV download, and labels read rates as a floor, which they are. See group insights.