I've shipped in-app chat three times in React Native — once the hard way with a hand-rolled WebSocket layer, twice with libraries — and the difference in time-to-ship is weeks. The catch is that the "top chat libraries" lists floating around are often years stale: they still recommend services that shut down and list the same library under two different names. This guide is the corrected, 2026-current version: what actually exists, what it costs you in money and control, and which one fits your app.
Quick answer: For a hosted, production-ready chat feature, Stream Chat is the strongest React Native SDK in 2026, with CometChat and Sendbird as close alternatives. If you'd rather own the stack, react-native-gifted-chat gives you a free, battle-tested chat UI you wire to your own backend — typically Firebase, Supabase, or a Socket.IO server you build yourself.
First: the three ways to add chat to a React Native app
Every option below falls into one of three buckets, and knowing your bucket matters more than any feature grid:
1. Hosted chat platforms (Stream, CometChat, Sendbird) — the vendor runs the servers, sync, push notifications and moderation; you drop in their SDK and pay monthly. Fastest to production, monthly bill scales with usage.
2. UI-only libraries (react-native-gifted-chat) — free open-source components that render messages, typing indicators and avatars, but with no backend at all. You bring the server.
3. DIY infrastructure (Firebase, Supabase, Socket.IO) — general-purpose real-time backends you assemble into a chat system yourself. Maximum control, maximum work.
1. Stream Chat — the safest commercial default
Stream's React Native SDK is the most polished of the commercial options: pre-built UI components that genuinely look native on iOS and Android, offline support, message threads, reactions, typing indicators, and first-class push notifications. The underlying infrastructure handles delivery across flaky mobile networks, which is the hard part nobody appreciates until they've built it themselves.
Where Stream earns its price is the total package — moderation tooling, analytics, and documentation that's actually current. The free tier lets you prototype with real limits (roughly $0 with modest monthly active users), and paid tiers start around a few hundred dollars a month as you scale. Check their pricing page — it shifts regularly.
If you want to see the component quality before committing, their React Native chat SDK page links live demos for both platforms.
2. react-native-gifted-chat — the free UI workhorse
One correction to older versions of this article (including ours): "Gifted Chat" and "React Native Gifted Chat" are the same library — react-native-gifted-chat on GitHub — not two options. It's been the default open-source chat UI for React Native for years, with message bubbles, avatars, typing indicators, read receipts, pagination, and a props-driven API you can theme to match your app in an afternoon.
The honest 2026 assessment: it's still the best free chat UI, and it's maintained, but development pace is slow and you should skim the issue tracker before betting a deadline on it. It renders the chat; it does not send, sync, or store anything. The standard pairing is Gifted Chat for the interface plus Firebase or Supabase for the plumbing — which is exactly why the next two entries matter.
3. Firebase — the DIY backend most teams already have
Firebase isn't a chat library; it's Google's app platform whose Firestore database happens to be very good at the hard parts of chat: real-time listeners that push new messages to every device, offline caching with automatic sync, and authentication with Google, Apple, phone and social providers built in. For a team already inside the Firebase ecosystem (most React Native apps are), adding Firestore collections for channels and messages is the fastest free route to working chat.
Costs need watching: Firestore bills per read and write, and chatty features generate both aggressively. A small app sits comfortably in the free Spark tier; a group-chat app at scale can produce a surprisingly large invoice. Storage (for images and video attachments) bills separately.
4. Supabase — the open-source Firebase alternative
Supabase wraps Postgres with real-time subscriptions, auth, and storage, and it has become the pragmatic choice for teams who want Firebase's workflow without lock-in. Postgres row-level security gives you fine-grained "who can read which channel" rules in SQL, the realtime layer pushes new messages as they're inserted, and you can query your own chat data with ordinary SQL instead of Firestore's constraints — a genuine advantage when you eventually need analytics or admin tooling.
The free tier covers development and small apps; paid tiers start around $25/month per project. If your team knows relational data modelling, Supabase is the less frustrating DIY path.
5. CometChat — hosted chat with built-in calls
CometChat's pitch is breadth: text, media and location sharing, typing indicators, read receipts, threads and reactions — plus the differentiator, native voice and video calling APIs that drop into the same chat UI. If your product roadmap includes "and then users can call each other," evaluating CometChat against Stream with calls in mind is worthwhile. SDKs cover React Native properly, with UI kits you can theme. Pricing is per-monthly-active-user with a free tier for getting started; like all platforms here, confirm current numbers on their site.
6. Sendbird — the enterprise-heavy alternative
Sendbird is the other big hosted platform, common in marketplaces, on-demand apps and social products that need chat at serious scale with compliance features. Its React Native UI kit ships the standard set — channels, threads, reactions, moderation, push — and its moderation and analytics tooling runs deeper than most. It's frequently the answer for regulated industries and large teams with procurement requirements. Pricing sits at the premium end; a free tier exists for development.
7. Socket.IO — when you roll the transport yourself
Socket.IO isn't chat-specific: it's the widely used real-time layer that keeps a WebSocket connection alive between your React Native app and your own Node server, with automatic reconnection and fallbacks. Building chat directly on it means writing everything else — persistence, history pagination, delivery receipts, push notifications, offline queueing — yourself. I did it once and wouldn't again for a typical product; it's the right call only when you have unusual requirements (heavy custom business logic in the message path, self-hosting mandates, or extreme cost sensitivity at scale).
What happened to the libraries in older versions of this list
Two entries deserve explicit retirements, because they're still being recommended by stale listicles:
- Gifted Messenger — the predecessor of react-native-gifted-chat, unmaintained since around 2017. Use react-native-gifted-chat instead.
- Pusher Chatkit — a hosted chat service that Pusher shut down back in 2020. If you see it recommended anywhere, the list is pre-2020 and every other entry is suspect too.
How to choose in one pass
- Need chat shipped this month with zero infrastructure? Stream (or CometChat/Sendbird).
- Want a free, customizable chat UI and already have a backend? react-native-gifted-chat.
- Greenfield app, small team, cost-sensitive? Firebase or Supabase, paired with Gifted Chat.
- Unusual requirements and a strong backend team? Socket.IO and a lot of planning.
Whichever you pick, keep your chat layer behind an interface in your codebase — swapping Stream for Supabase later is painful enough without it being tangled through every screen. And since chat is only one moving part of a mobile product, our guides on secure API integration practices and the pros and cons of Flutter for mobile development cover the neighbouring decisions.
Frequently asked questions
Is react-native-gifted-chat still maintained in 2026?
Yes, but slowly — it's a mature open-source project with an enormous install base, and maintenance is closer to caretaking than active development. That's fine for what it does: rendering chat UI. Check the GitHub issue tracker for React Native core compatibility on your target versions before you build on it, and budget a little time for patches if a new RN release breaks something.
How much does Stream Chat cost for a React Native app?
Stream has a free tier suitable for prototypes and very small apps, with paid plans that scale by monthly active users — entry tiers historically start in the low hundreds of dollars per month. CometChat and Sendbird use similar MAU-based models. All three change pricing regularly, so treat any number you read (including here) as an estimate and confirm on their pricing pages before committing.
Can I build chat with Firebase for free?
Yes, up to a point. Firestore's free tier includes generous daily read/write quotas and a small amount of storage, which comfortably runs a development app and a modest user base. The trap is scale: a busy group-chat feature multiplies read operations fast, and a viral spike can jump you into paid tiers within a billing cycle. Set budget alerts before launch — it's the one Firebase mistake everyone makes once.
What replaced Pusher Chatkit for React Native?
Pusher shut Chatkit down in 2020 and never shipped a successor. Current equivalents are Stream, CometChat or Sendbird if you want hosted infrastructure, or Firebase/Supabase if you want to assemble your own. If a tutorial or listicle recommends Chatkit, it predates 2020 — assume every other recommendation on that page is equally outdated.
Do I still need a server if I use Firebase or Supabase?
Not for basic chat — both handle real-time message delivery, auth and storage without any server you manage, via security rules and client SDKs. You'll want lightweight server functions (Cloud Functions / Edge Functions) for things like push notification fan-out, message moderation hooks, or integrating an AI assistant. That's still dramatically less infrastructure than running your own WebSocket backend.
Which option is fastest to get to a working prototype?
Stream and CometChat, almost tie: their UI kits render a full chat experience in an afternoon because servers, sync and push are included. Gifted Chat plus Firebase takes a day or two more but leaves you owing nothing monthly. DIY on raw Socket.IO takes weeks — don't choose it for speed.
Related reading
- How much does it cost to build a React Native app?
- Best practices for secure API integration in 2026
- Pros and cons of Flutter for mobile app development
I've lived the Stream-vs-DIY decision on real products — if you tell me your app's user count and budget in the comments, I'll tell you which bucket I'd put it in.
