Member limits
A WhatsApp group supports up to 1,024 members, up from earlier limits of 256 and 512.
A plain-English glossary entry on WhatsApp groups — member caps, admin controls, broadcast lists, and when a shared inbox beats a group.
At a glance
What you get
A WhatsApp group supports up to 1,024 members, up from earlier limits of 256 and 512.
Creators are admins by default and can add or remove members, approve joins, change settings, and delete messages.
One-to-many messaging where replies return as private DMs — capped at 256 contacts, and distinct from groups.
Control who can add you, edit group info, or send messages, plus disappearing-message options.
Community, family, project coordination, and light business updates where everyone needs visibility.
For customer-facing or multi-agent work, a shared inbox adds roles, assignments, SLAs, and audit logs groups lack.
How it works
Tap New Group, pick members, name it, and set an icon.
Promote admins and tighten privacy settings for who can add members or edit info.
Use a group for conversation; use a broadcast list for one-to-many announcements.
Once you need roles, routing, and auditing, move customer conversations to a shared inbox.
Deep dive
A plain-English reference for WhatsApp group limits, admin controls, and the difference between a group and a broadcast list. Plus the case for switching to a shared inbox when your team outgrows groups.
| Limit | Value |
|---|---|
| Members per group | 1,024 |
| Broadcast list size | 256 |
| File share size | 2 GB |
| Voice message length | 30 min |
| Video status length | 90 sec |
| Group description length | 2,048 chars |
These limits have moved over time — the group member cap rose from 256 to 512 to 1,024, and file sizes have increased repeatedly. Treat the table as the current state, not a permanent fact, and check WhatsApp's own help pages if an exact number is critical to your plan.
Group creators are admins by default. Admins can:
In group settings, an admin can restrict who may edit group info, send messages, add members, or approve new joiners. In larger groups, the common configuration is: only admins can add members or edit info, while everyone can send messages. This cuts down on spam and accidental removals.
Admins cannot see deleted-for-me messages, cannot recover messages a member deleted before others read them, and cannot prove who said what after the fact in any attributable way. For customer-facing work, those gaps matter.
Groups on your personal WhatsApp and groups on WhatsApp Business look the same but sit in different accounts. Keep customer groups off personal numbers: there is no business profile, no catalog, and no clean way to hand the account over if you leave.
WhatsApp groups are great for small, informal coordination. The moment you're using a group for customer conversations, support tickets, or team operations across shifts, the cracks show:
Greenbubble's shared inbox keeps the same WhatsApp number but adds unlimited agents, roles, assignments, SLAs, audit log, CRM sync, templates, and automations. Use the Greenbubble shared inbox when groups stop working.
| Need | WhatsApp group | Shared inbox |
|---|---|---|
| Casual team chat | ✅ | Possible, not ideal |
| Customer support | ❌ | ✅ |
| Ownership of a conversation | ❌ | ✅ |
| First-response SLA | ❌ | ✅ |
| Audit trail | ❌ | ✅ |
| CRM contact records | ❌ | ✅ |
| Templates and automation | ❌ | ✅ |
| Customer privacy | ❌ (all members see all) | ✅ (role-based) |
Nothing here says groups are bad. For an internal ops channel, a group is cheap and fast. The problem is only when a group becomes the system of record for customer work — at which point you are running a support desk inside a chat app, with none of the tooling that implies.
If you do keep a group for internal work, a few habits keep it useful. Name it for its purpose, not its people, so membership can change without confusion. Keep one pinned message with the current priorities. Move decisions out of the chat into your actual system of record once they are made. And review membership quarterly — dead groups and stale members are the main reason people mute or leave.
A group gives no signal when a message is ignored. There is no assignment, no deadline, and no escalation path, so a customer request can sit unanswered while every member assumes someone else handled it. In a shared inbox the same request has an owner and a clock. That difference alone resolves most of the "we thought someone replied" incidents teams describe.
As of 2026, a WhatsApp group supports up to 1,024 members. The limit has been raised several times — historically 256, then 512, then 1,024.
Yes. There is no documented cap on the number of groups a single user can create, but quality and engagement fall sharply above ~30 active groups per user.
A group is a many-to-many chat where every member sees every message. A broadcast list is a one-to-many channel: you send, your contacts receive it individually, replies come back as private DMs. Broadcast lists are capped at 256 contacts.
Group creators are admins by default and can promote other members. Admins can add/remove members, change group settings, approve new-member requests, and delete messages.
WhatsApp groups are great for small, informal coordination (family, friends, side project). For customer-facing or business coordination across a team, a shared inbox like Greenbubble offers roles, assignments, SLAs, and audit logs that groups cannot match.
A group is discoverable by its members and by anyone who is added, but it is not a public listing. There is no true "private" group in the enterprise sense — every member sees the full history and can export or screenshot it. That is another reason customer data does not belong in a group.
Ownership passes to another admin if one exists. If the last admin leaves, WhatsApp promotes another member, which can be surprising. For business-critical groups, always keep at least two named admins.
Yes. Individual files can be up to 2 GB, voice messages up to 30 minutes, and status video up to 90 seconds. These limits apply across WhatsApp, not just groups.
Start free trial → · See the shared inbox → · Compare Greenbubble vs Wati →
FAQ
Up to 1,024 members as of 2026, raised over time from 256 then 512.
There is no documented cap, but engagement drops sharply above roughly 30 active groups per user.
A group is many-to-many where everyone sees every message. A broadcast list is one-to-many; replies come back privately, and it caps at 256 contacts.
Creators are admins and can promote others. Admins add or remove members, change settings, approve joins, and delete messages.
Groups suit small informal coordination. Customer-facing work across a team needs an inbox with roles, assignments, SLAs, and audit logs.
Keep reading
Beyond groups
Roles, assignments, SLAs, and audit logs for teams that coordinate with customers.