What do you do when a group chat gets too big?

First separate the symptom (a member cap) from the disease (chat stops working as memory past ~10 people). Raising the cap by switching apps buys weeks. The durable fix is moving plans, files, and decisions into objects that don't scroll — either a purpose-built group tool or, at minimum, a shared drive plus a chat.

Should our club move to a Discord server?

Only if you want voice chat and community features. A server solves the member cap but hands a volunteer an administration job — channels, roles, bots — and information still gets buried in chat. Most clubs need something simpler, not something bigger.

Guide

Your group hit the group-chat limit. Now what?

The short answer: the member cap you just hit is a symptom. The disease started earlier — somewhere past ten people, when the chat stopped working as the group’s memory. Before you pick a bigger chat, decide which problem you’re solving, because they have different answers.

The caps, for reference

Discord group DMs cap at 10 members — a limit users have asked about for years, usually to be told “just make a server.” iMessage tops out around 32. WhatsApp groups run to the hundreds and beyond, which sounds like the fix until you’ve been in a 60-person WhatsApp group and learned what “474 unread messages” does to participation. The cap is never really the constraint. Attention is.

Option 1: a bigger chat

Moving from Discord DMs to WhatsApp, or iMessage to GroupMe, raises the ceiling and changes nothing else. Fine if your group genuinely just talks — a friends’ chat with 14 people has no organizing problem. If there’s a roster, a season, or a form anywhere in your group’s life, you’ll be back here in a month with the same buried-information problem and more people not scrolling.

Option 2: a server or workspace

The internet’s reflex answer — “make a Discord server,” “get a Slack” — solves the cap and creates an administration job. Someone designs channels, sets roles, explains it to the members who’ve never seen it. Notably, people resist this for a reason worth respecting: group chats are loved precisely because they’re simple. “I don’t want a server, I want a group chat” is a coherent product requirement, and the industry has mostly ignored it. Servers make sense for large communities and voice-centered groups; they’re overbuilt for a 20-person club. Workspaces add per-seat pricing on top.

Option 3: keep the chat, move the record

The version that respects what your group actually is: the chat stays for talking — whichever app it’s already in — and the things that must survive the scroll move to a structure built for them. Events with RSVPs. Files with homes and versions. Polls that close with an answer. Forms with a who’s-missing list. Members reach each of those from a link pasted into the chat, so nobody migrates and nobody administers anything. That’s the shape TinyHubs takes, and the coexistence pattern is described honestly in keep WhatsApp, add a memory.

How to choose in one question

Does anyone in the group have a job — collecting, scheduling, deciding, filing? If no: bigger chat, done. If yes: that person is currently doing their job against a timeline that eats their work, and a bigger timeline makes it worse. Give the job a tool; leave the chat alone.

Bigger than a group chat, simpler than a server — that missing middle is exactly what we build. TinyHubs for clubs →