About Shadcn UI Chat UI Blocks
A chat UI is the messaging screen of an app: a list of conversations, a thread of messages and a composer for replies, often with a panel that shows who is on the other side. These ten shadcn chat blocks cover personal and team messengers, shared support inboxes, an AI agent inbox, an omnichannel CRM chat and two video call screens.
Like the rest of our shadcn blocks, each screen is built with React, TypeScript and Tailwind CSS on top of shadcn ui components such as Avatar, Badge, Dropdown Menu, Input Group, Sheet and Tabs, plus the chat specific Bubble, Message and MessageScroller shadcn components. Every block runs on local state, so selecting a chat clears its unread count, sending adds a message and filters change the list as you click.
Key Elements of a Chat Interface
- Conversation list: avatars, names, a preview of the last message, the time and an unread badge, with search on top.
- Thread header: the contact or group name, presence or member count and actions such as call, video and details.
- Message thread: bubbles grouped by sender, timestamps and read or delivery states that stay scrolled to the newest message.
- Composer: a message field with send, attachment, emoji and voice buttons, or a reply and note switch for support teams.
- Context panel: profile, shared files and links, ticket attributes or CRM data next to the conversation.
Where and Why to Use Chat UI Blocks
A chat screen has many moving parts: the list, the thread, the composer, responsive panes and dozens of small states. Building it from scratch takes weeks, and the details users notice, such as unread counts or a thread that jumps to the latest message, are easy to miss. These blocks give you that structure as shadcn components styled with Tailwind CSS, so you only connect your data and realtime layer.
- Social and community apps: one to one and group chats with media, voice messages and reactions.
- Team collaboration tools: grouped team chats, profiles and shared files inside a workspace.
- Customer support help desks: shared inboxes with views, assignees, statuses and internal notes.
- Sales and social commerce: answer leads from Messenger, WhatsApp, Instagram and web chat in one list.
- AI assisted inboxes: review and approve replies that an AI agent drafts for you.
- Video meetings: call screens with participants, call controls and an in-call chat.
Chat UI Blocks in This Collection
- Chat UI 1: A good base for a consumer messenger where people send more than text. Use it when your app needs to play voice notes, open shared photos and offer file downloads right in the thread.
- Chat UI 2: Fits social or creative communities where the user profile and friends who are online matter as much as the chat itself. Searching inside the open conversation is built in.
- Chat UI 3: Suited to a studio or team workspace that separates team channels from direct messages and wants quick email, call and video actions on the profile.
- Chat UI 4: Built for operations and success teams that triage customer emails together and discuss them in private comments before anyone replies.
- Chat UI 5: A help desk layout for teams that work in tickets, snooze and close conversations and need lead data and recent page views while replying.
- Chat UI 6: Use it when an AI agent writes outgoing emails and a person has to approve each one before it goes out.
- Chat UI 7: A meeting room for reviews and workshops, where you switch between the call and shared session notes with action items.
- Chat UI 8: A good match for busy group chats that need folders, pinning, mentions and searchable history, similar to popular desktop messengers.
- Chat UI 9: Fits meeting products that add AI on top of the call, with noise and subtitle settings and a summary ready to share when the call ends.
- Chat UI 10: Made for online stores and agencies that sell through chat, with lead tags, agent assignment and a way to send product photos to the customer.
Similar Block Categories
- AI Chat: build an assistant conversation with model pickers and prompt inputs next to your human chat.
- Mail App: the same list and reading pane pattern for email instead of chat.
- Sidebar Layouts: wrap the chat screen in your app navigation.
- Empty State: design the first run screen before a user has any conversations.
- Event Calendar: schedule the calls and meetings that start in the chat.
Accessibility
Icon only buttons such as call, video, send, attach and back carry an aria-label, the selected conversation is marked with aria-current, and unread dots and read checks have labels like “Unread” and “Read”. Search fields and composers have aria-labels as well. Call controls in Chat UI 7 and 9 update their labels with the state, for example “Mute microphone” and “Unmute microphone”, and toggles such as star, thread search and reaction chips use aria-pressed. Every sheet has a title and description for screen readers, and in Chat UI 1 and 2 the message actions that appear on hover also appear when they receive keyboard focus.
Pressing Enter sends a message, and in the textarea composers of Chat UI 4, 5, 6 and 10 Shift and Enter adds a new line. In production, consider an aria-live region that announces incoming messages, and respect reduced motion settings for the reaction animation in Chat UI 9 and the jump to latest button.
Chat UI FAQ
autoScroll, so new messages scroll into view. Several blocks also render MessageScrollerButton, a floating button that jumps back to the end after you scroll up. The provider is keyed by the selected conversation, so switching chats starts a fresh thread.@shadcn/react package. Chat UI 1 adds the Attachment component for file cards. All blocks show feedback with sonner toasts, and Chat UI 1 to 4 format times with date-fns.
