
Quick answer: for most React Native apps, react-native-toast-message is the safe default: a simple imperative API, keyboard awareness, custom layouts and a release in September 2026. Pick sonner-native if you want the Sonner API with promise toasts, action buttons and swipe to dismiss, and you already use Reanimated. @backpackapp-io/react-native-toast suits teams who like the react-hot-toast API and want several toasts at once. Burnt gives you real native iOS and Android toasts in Expo dev builds. If you already use React Native Paper, its Snackbar is enough. For a plain Android-style message, the built-in ToastAndroid or react-native-simple-toast will do. Release dates below come from each package's npm entry, checked in November 2026.
| Library | Best for | License | Notable features | Maintained (latest npm release) |
|---|---|---|---|---|
| react-native-toast-message | A dependable default | MIT | Imperative API, keyboard-aware, custom layouts | 2.5.2, Sep 8, 2026 |
| sonner-native | The Sonner API on mobile | MIT | Promise, success, error and custom variants, action button, swipe to dismiss | 0.27.0, Aug 15, 2026 |
| @backpackapp-io/react-native-toast | Many toasts at once | MIT | react-hot-toast style API, corner positions, promise toasts, web | 0.15.1, Nov 2, 2025 |
| burnt | Native iOS and Android toasts | MIT | Wraps native iOS components and ToastAndroid, alerts, web via Sonner | 0.13.0, Mar 10, 2025 |
| react-native-root-toast | A pure JavaScript toast with simple options | MIT | Call by API or render as a component | 4.0.1, Mar 25, 2025 |
| React Native Paper Snackbar | Apps already on Paper | MIT | Material Design snackbar with an action | 5.15.4, Nov 2, 2026 |
| ToastAndroid and react-native-simple-toast | Plain system-style messages | Built in / MIT | Fire-and-forget show() call | Built in; 3.3.2, Jan 3, 2025 |
| PLG OS Toast (our product) | Toasts you edit without a release | ISC (SDK) | Remote configuration, data into Customer 360 | 2.1.2, Oct 16, 2024 |
Who it is for: most apps that need success, error and info messages without extra native setup.
Install: npm install --save react-native-toast-message
How it works: render the Toast component once, as the last child in your app's root view, then call Toast.show() from anywhere, even outside React components, for example Toast.show({ type: 'success', text1: 'Saved' }).
Strengths: an imperative API, keyboard awareness, customizable layouts and flexible config. Its docs cover the common pain points: showing a toast inside a Modal, rendering it alongside a navigation library and mocking it in Jest tests. It has no peer dependencies beyond React and React Native.
Limits: the built-in types are success, error and info, so a branded design or extra types mean writing a custom layout. Its API has show() and hide() but no promise or loading toast, which sonner-native and @backpackapp-io/react-native-toast include.
Who it is for: teams who use Sonner on the web and want the same API in their mobile app.
Install: npx expo install sonner-native, plus its peer dependencies.
How it works: add the Toaster component at your app's entry point (in the root layout file with Expo Router), then call toast('Hello, World!').
Strengths: its README says the API fully matches Sonner. It has success, error, warning, custom and promise variants, a promise toast with a built-in loading state, title and description, an action button with a callback, custom icons, top, bottom or center positions, swipe to dismiss, built-in dark mode and NativeWind support. It works with Expo.
Limits: it needs several peer dependencies: Reanimated, Gesture Handler, Safe Area Context, SVG, Screens and Worklets. It is still on a 0.x version, and its README recommends the original Sonner, not sonner-native, for the web.
Who it is for: apps that need several toasts on screen at once, in different positions.
Install: npm i @backpackapp-io/react-native-toast, plus Reanimated, Safe Area Context and Gesture Handler.
How it works: wrap the app in GestureHandlerRootView and SafeAreaProvider, add the Toasts component at the root, then call toast('My Toast Message').
Strengths: it is built on the react-hot-toast API, so toast.success(), toast.error(), toast.loading() and toast.promise() will feel familiar. It supports multiple toasts, keyboard handling on iOS and Android, swipe to dismiss, six positions including the corners, custom components, native modals and onPress, onShow and onHide callbacks. It also runs on the web.
Limits: the last release was in November 2025, about a year ago, and it is on a 0.x version.
Who it is for: apps that want toasts that look and behave like the platform's own.
Install: npx expo install burnt, then rebuild your dev client. Plain React Native projects run pod install.
How it works: call Burnt.toast({ title: 'Saved', preset: 'done' }) with no provider component. On iOS it wraps native indicator and alert libraries, on Android it wraps ToastAndroid, and on the web it wraps Sonner.
Strengths: native rendering rather than JavaScript UI, animated icons, App Store style alert popups, haptics and toasts that appear over native iOS modals, which the README calls out as a long-standing React Native problem. It works with both the old and new architectures.
Limits: it does not work in Expo Go, so you need a dev build. On Android, Burnt.alert() falls back to a plain toast. The latest release is from March 2025.
Who it is for: teams who want a pure JavaScript toast with almost no setup.
Install: npm install react-native-root-toast
How it works: wrap your root component in RootSiblingParent (needed on React Native 0.62 and later), then call Toast.show('This is a message', { duration: Toast.durations.LONG }), or render the Toast component and control its visible prop.
Strengths: a long list of options for duration, position, shadow, colors, opacity, delay and hide-on-press, plus callbacks for each stage of the show and hide animation. Preset durations are 2,000 ms (SHORT) and 3,500 ms (LONG).
Limits: it is a simple message bar, without built-in success or error variants or promise toasts, and it lists react-native-safe-area-context as a peer dependency. The latest release is from March 2025.
Who it is for: apps already built on React Native Paper, the Material Design component library.
Install: npm install react-native-paper (you likely have it already).
How it works: render a Snackbar with a visible prop and an onDismiss callback, and add an optional action button. Paper's source describes snackbars as brief feedback about an operation, shown at the bottom of the container they are wrapped in.
Strengths: it matches the rest of a Paper app, it is part of a library that was updated in November 2026, and it supports an action such as Undo.
Limits: it is a controlled component, so you manage visible state yourself instead of calling a global show() function. It follows Material Design, which may not suit an iOS-first design.
Who it is for: apps that only need the short system-style message Android users know.
Install: ToastAndroid ships with React Native, so there is nothing to install. For iOS too, use npm install react-native-simple-toast, then run pod install.
How it works: call ToastAndroid.show('Saved', ToastAndroid.SHORT). react-native-simple-toast copies that API (Toast.show(message, duration)) and uses a native toast library on iOS.
Strengths: the smallest possible setup. react-native-simple-toast also renders on top of Modals and Alerts, avoids the keyboard and supports the new architecture from React Native 0.71.
Limits: ToastAndroid is Android only, and the React Native docs note that from Android 11, setting the gravity has no effect on text toasts. Styling options are minimal on both.
Some packages still appear in search results but have not had a release in a long time. react-native-toast-notifications (3.4.0) and react-native-flash-message (0.4.2) were last published in August 2023, and react-native-notifier (2.0.0) in July 2024. They may still work, but check open issues against your React Native version before you build on them.
PLG OS is our own product, so weigh this entry with that in mind. It is a different kind of option: a hosted component rather than a UI library.
The React Native Toast component is set up in three steps: run npm i @questlabs/react-native-sdk, deploy the Toast component in the PLG OS platform, then paste the generated code into your project. You can change the toast's text and features from the no-code PLG OS dashboard without shipping a new build, toast data is added to Customer 360, and you can send that data to your CRM or other tools. The same component is available for the web as a React toast and for Flutter.
Limits: it adds a hosted service and pricing (a free plan with 100 MTUs and 1 component, Starter at $49 a month with 1,000 MTUs and 2 components). Its React Native SDK's latest npm release is 2.1.2 from October 2024 and lists React 18 as a peer dependency, so check compatibility with your app first. If you just need a local success message, a library above is simpler.
For most apps, react-native-toast-message: it is MIT licensed, needs no extra native dependencies and had a release in September 2026. Choose sonner-native if you want the Sonner API, or Burnt for native toasts.
On Android you can call the built-in ToastAndroid.show(message, ToastAndroid.SHORT). For iOS and Android, install a library such as react-native-toast-message, render its Toast component at the root and call Toast.show().
No. React Native's built-in ToastAndroid only works on Android. On iOS you need a library, such as react-native-toast-message, Burnt or react-native-simple-toast.
Yes. Its README says it works with Expo and installs with npx expo install sonner-native, alongside Reanimated, Gesture Handler and its other peer dependencies. Burnt also supports Expo, but not in Expo Go.
Burnt and react-native-simple-toast render over modals, and @backpackapp-io/react-native-toast supports native modals. react-native-toast-message has a docs page that shows how to render its toast inside a Modal.