Groups or channels: picking the right one before you build

Someone sent me a screenshot last month of a spam comment sitting under their company’s announcement post. Not the spam, the interesting part: they were an administrator of that channel with every switch turned on, and the delete option was greyed out.

The comment lived in the linked discussion group, a separate chat with its own list of administrators, and nobody had thought to promote them there.

That is the shape of nearly every problem here. People pick between a group and a channel in about four seconds, on the day they set the thing up, then live inside that decision for years because there is no cheap way back out.

What each one actually is

A channel is a broadcast. You post, subscribers read, and the client does not give a subscriber a text box at all. Silence is structural rather than a permission you granted.

Subscribers also cannot see each other. There is no browsable member list, so nobody in your audience can pick another person out and open a direct message. A channel has no subscriber ceiling either.

A group is a room. Everybody in it can post by default, everybody can see everybody, and every message that lands there becomes your problem the moment it lands.

Both belong to exactly one owner account, which matters more than people expect.

The limits, and the single conversion Telegram will run

A plain group holds 200 members. Cross that and Telegram silently upgrades it to a supergroup, which most owners never notice happening. A supergroup runs to 200,000 members and stops.

That ceiling has one door in it. A supergroup past 200,000 can be converted into a broadcast group, where only administrators send messages and everyone else stays on as a spectator who can still join voice chats. It is one way, with no button to turn it back.

Worth knowing mainly so you stop waiting for a general purpose convert feature. That is the only one.

The linked group is a second thing you own

A channel can have a discussion group attached to it. Your post appears in the group, a comments button shows up underneath, and readers argue below the announcement without being able to post over it. This is the arrangement most businesses actually want, and hardly anybody arrives at it deliberately.

It is also where the confusion lives, because linking two chats does not merge them.

The group keeps its own owner, its own administrator list, its own permissions, and its own public username if you gave it one. Being an admin in the channel grants you nothing in the group, which is the greyed out delete button in that screenshot. Every moderator has to be promoted twice.

Your subscribers are not members of it either. Someone joins the group at the moment they leave their first comment, so it fills with the subset of your audience that felt like talking.

And unlinking is destructive. Detach the group and every comment thread under every post you have published stops being reachable. Attach a different group and the old threads do not come with it.

Moving between them costs you the audience

There is no convert button between a group and a channel. What you do instead is create the other one and ask people to walk across.

You cannot carry them over. An administrator can manually add up to 200 people to a channel, and only if they are already contacts, and only if that person’s privacy settings allow being added. For a public community that clears out to roughly nobody.

So the real migration is posting an invite link in the old place, repeatedly, for weeks, and keeping whatever fraction follows it. Plan on losing most of them.

The read only group, and what it is not

You can take posting rights off everyone instead. Open group permissions, switch off send messages for the default role, and only admins talk. It looks channel shaped and nobody had to move.

What you lose is concrete. No per post view counts, no silent broadcast, no signed posts, no comments section, and the member list stays visible to the room, so every person in there remains addressable by every other person in there.

I use it as a stopgap when a group has drifted into being an announcement feed and the owner is not ready to split things up. I would not choose it on purpose.

Moderation is the actual price of a group

A channel costs you the work of writing posts. A group costs you the work of policing a room every day for as long as the room exists, and that cost never comes down.

Spam does not ramp up gradually. It arrives the hour you become findable, because a public username puts you in Telegram search and there are people whose whole job is joining every public group they can locate. What turns up is boringly predictable: giveaway accounts, forwarded investment pitches, the same person joining under four names in a week, and messages aimed at your members instead of at you.

Most of it happens while your team is asleep. That detail wrecks more otherwise sensible plans than the volume does.

The controls worth setting on day one

Default permissions are per group rather than per person. You can switch off media, stickers, embedded links and polls, and you can remove the right for members to add other members. Take that last one away almost always.

Slow mode is the most useful control in the product. It caps how often one member can send, with options from 10 seconds up through 30 seconds, a minute, five minutes, a quarter hour and an hour. Thirty seconds ends copy paste flooding and a real human being will never notice it is on. I have set it on every group I touch and never had a complaint.

Join requests move the work to the front. Generate an invite link that requires approval and nobody enters until an admin lets them in.

Telegram also ships an aggressive anti spam toggle for groups above 100 members. It is fine. It is not a moderator.

You can hold 50 administrators. If your community is awake around the clock you want people in at least a couple of time zones, because an unstaffed group at three in the morning is where the screenshots come from.

The username is a discoverability decision

People fill in the public username like it is a profile field. It is the switch that decides whether strangers can find you.

With one you are in search, your link is short, and everybody can reach you including the people you would rather not meet. Without one, entry runs through invite links that you issue and can revoke.

An account can only hold a small number of public links across everything it owns, somewhere around ten last time I counted, so spending one on a chat you were only half sure about has a real cost.

Then there is scraping. A public group’s member list is readable by anyone who joins it, and it gets harvested constantly. Your members start receiving direct messages from strangers who know which community they belong to, and they will read that as your fault, because from where they are standing it is. A channel has no equivalent exposure, since there is no list to take.

I built one of these backwards

I started a community of mine as a group, because a conversation is an easier thing to start than a broadcast and a group felt friendlier. Gave it the good short public username immediately. It got to roughly two thousand people and it was a decent room.

Then I needed to announce things, and every announcement was buried within a day.

So I made a channel. The good username was already spent, so the channel got a worse one, and I spent six weeks dropping invite links into the group asking people to subscribe. About a third came across.

The right order had been sitting there the whole time. Create the channel first, put the good username on the channel, then create the group and link it as the discussion side. Same two objects, built in an order I could not undo.

What I would set up for a business today

Start with the channel. It holds the username, it survives being ignored for a month, and it is the surface you control.

Add the linked discussion group when there is a named person whose job includes reading it. Not before. Put slow mode at 30 seconds from the first day, remove the member add permission, and keep join approval on until you have enough admin coverage that you no longer need it.

If nobody is going to staff the group, run the channel with comments off and take the conversation into a support inbox or a bot instead. An unmoderated comments section under a company announcement is worse than having none.

A group on its own is still right sometimes. A paid members community where the conversation is the product. An internal team room. A support group of a dozen customers who know each other by name. What those share is that the talking is the point and somebody owns it.

Where hosting fits

Underneath either structure sits one owner account, which is a phone number on a device somewhere. People spend weeks arguing about architecture and then hang all of it off a personal handset with a prepaid SIM nobody has topped up since March.

Telegramvault is managed Telegram hosting on dedicated hardware in Singapore, on real carrier lines, so the account that owns your channel and your group stays online and its number stays paid. It will not fix a structure you built in the wrong order. It removes the failure that makes the structure question academic. If that is worth handing over, start here and use code TGYT.

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