Sendbird's APIs and SDKs provide two basic types of channels: open channel and group channel. Each type of channel is designed to support a wide variety of use cases that your business requires. This page explains the differences and characteristics of the two types.

Note: Sendbird Chat SDK v4 supports both TypeScript and JavaScript.

Note: By default, the Allow creating open channels and Allow creating group channels options are turned on which means that open channels and group channels can be created by any user with Sendbird Chat SDK. This may grant access to unwanted data or operations, leading to potential security concerns. To manage your access control settings, you can turn on or off each option in Settings > Application > Security > Access control list on Sendbird Dashboard.

---

An open channel is a Twitch-style public chat where millions of users can easily join without invitations. Open channels can be used in short-lived live events, such as streaming, news-feed type messaging to massive audience, or events that don't require a permanent membership.

With our Chat SDK for JavaScript, you can use a variety of behavior related properties when creating different types of open channels.

Sendbird Chat SDK now supports two operation systems for open channels, which are classic and dynamic partitioning. These two systems offer the same features and functions, except that dynamic partitioning allows open channels to accommodate a large number of users. Classic open channels are the original open channels Sendbird has been providing, and a single classic open channel can handle up to 1,000 participants. On the other hand, dynamic partitioning open channels are designed to accommodate much greater number of users than the classic open channels using subchannels where you can divide users evenly.

Note: Sendbird applications created before December 15, 2020 are using classic open channels. The classic open channels will be deprecated soon, but the classic channels created up until the deprecation date will remain and function the same way. When the deprecation takes place, all Chat SDK users will be automatically migrated to the new dynamic partitioning system. If you wish to convert to dynamic partitioning open channels beforehand, contact our support team.

Learn more about how dynamic partitioning open channel operates in the open channel guide of Platform API.

Note: Sendbird's JavaScript Chat SDK v3.0.140 or later is recommended to use dynamic partitioning open channels.

Messages in ephemeral open channels are not saved in the Sendbird's database. This means that old messages pushed out by new ones can't be retrieved as they are one-time data. On the other hand, messages in a persistent open channel are permanently stored in the database, which is the default.

---

A group channel is a chat that allows close interactions among a limited number of users. In order to join a group channel, an invitation from a channel member is required. Depending on how you implement the joining process on the application level, an invited user can automatically join a group channel or manually accept the invitation. Various properties can be leveraged to design different types of group channels that suit your use cases, such as Twitter-style 1-to-1 direct messaging, WhatsApp-style group chat, and more.

With our Chat SDK for JavaScript, you can use a variety of behavior related properties when creating different types of group channels. You can create a group channel after configuring these properties.

A private group channel can be joined only by users that have accepted an invitation from an existing channel member by default. On the other hand, a public group channel can be joined by any user without an invitation, like an open channel.

A private channel can be used for 1-on-1 conversations, such as clinical consultations and Instagram-style Direct Messages, while a public channel for 1-to-N conversations, such as small group discussions among students.

The distinct property determines whether to resume an old channel or to create a new one when someone attempts to open a channel with the same members. For a 1-to-1 chat, it is highly recommended that you turn on the distinct property to continuously use the existing channel.

Let's say there is a distinct group channel with user A, B, and C. If you attempt to create a new channel with the same members, the existing channel will be used. This is similar to Twitter-style 1-to-1 direct messaging. If the distinct property of the channel is set to false, a new channel will be created.

Note: The default value of this property is false. When a new member is invited or an existing member leaves the channel, then distinct of the channel is automatically turned off as well.

For occasions that demand engagement among a relatively high volume of members, you can create a Supergroup channel, an expanded version of a group channel. It can be used for midsize conferences or large group discussions, such as company-wide stand-ups.

When the super property is set to true, a Supergroup channel will be created and up to tens of thousands members can gather in the channel. The maximum number of members for a Supergroup channel can be adjusted depending on your Chat subscription plan.

Note: When the super property is set to true, the distinct property can't be supported.

Messages sent in an ephemeral group channel are not saved in Sendbird's database. As such, old messages that are pushed out of a user's chat view due to new messages can't be retrieved. On the other hand, messages sent in a persistent group channel are stored permanently in the database by default.

---

A Supergroup channel is an expanded version of a group channel, which can accommodate a massive number of members while serving the same functions as a group channel. The maximum number can stretch up to tens of thousands of members depending on your Sendbird plan. Because a Supergroup channel is built upon the same foundation as a group channel, Platform APIs and SDK functions for both channel types are identical.

Note: Supergroup and group channels are alike in terms of Platform API and SDK design, except for the isSuper. The is_super property indicates whether the channel is a Supergroup channel or a group channel.

Supergroup channels can be used for a wide range of occasions that demand real-time engagement among a large number of users. One of the common use cases for Supergroup channels is community building, ranging from public forums to private events with a large membership.

• Ask-me-anything events: Supergroup channels also work as a platform for users to seek advice from an influencer or expert, such as Reddit Chat.

• Gaming community: Another common set-up is gaming communities, where users gather to find players to team up with or exchange ideas and strategies to advance further in the game.

• Stand-ups: Supergroup channels are a great place for midsize conferences, such as a organization-wide stand-up.

Note: To learn about differences among open channels, group channels, and Supergroup channels, see Channel types.

To secure stable operation and optimized user experience of a Supergroup channel, a few functions are subject to limits. Some of those limitations include:

• Visual interactions: Read and delivery receipts aren’t supported in Supergroup channels to provide an optimal performance in Supergroup channels.

• Unread counts: Unread counts are marked up to 100 only. In the case they surpass 100, we suggest you display the counts as 99+ to avoid confusion.

• Push notifications: The way push notifications for Supergroup channels work is determined by two factors: the number of members in a channel and the online status of its member.

  • When there are less than 100 members: A push notification will be sent for every message created in the channel.

  • When there are 100 members or more: A ten-minute time window will be applied to Supergroup channels with more than 100 members. Once the number exceeds 100 members, a push notification for a new message will be sent out to members and then the next push notification can come ten minutes after that.
    For example, the number of members in Channel A surpasses 100 at 13:00 and a new message is sent at 13:01, a push notification will be sent for the 13:01 message and the ten-minute time window begins. For the following ten minutes, there will be no push notifications for any messages created within the time frame. When ten minutes pass and a new message is sent at 13:11, the second push notification will be made for that message.

  • When a user becomes active: If one of the Supergroup channel members enters the channel and reads a message, the user will be recognized as active. Then only for the following one minute, the user will be receiving push notifications for all messages sent within the time frame.

---

The optimal use cases for each channel type can vary because different channels support different features. The following tables compare open channels, group channels, and Supergroup channels in terms of possible use cases and supported features.

Choose which channel type to use based on key factors such as the duration of a chat and the number of users participating in it. The following table lists possible use cases for each channel type.

The following table compares the difference among two types of channels.

---

Users can interact with other users in a channel by sending, receiving, replying to messages, and more. The following is a list of features that our Chat SDK provides. All the functionalities are supported in both open channels and group channels, unless noted otherwise.