CLI tool
zoontek/react-native-bootsplash avatar
zoontek/react-native-bootsplash

react-native-bootsplash: a CLI-generated native splash screen with a paid tier for dark mode

🚀 Show a splash screen during app startup. Hide it when you are ready.

4,305 stars291 forksTypeScriptMIT

At a glance

What is it?
react-native-bootsplash shows a native splash screen at app start and hides it when your app is ready. This analysis covers the generate CLI, the hand edits bare projects need, the Expo plugin that replaces expo-splash-screen, and the license key that gates brand and dark-mode assets.
Who is it for?
Choose it when you want a native splash screen generated from one PNG or SVG, on a bare React Native app or through the Expo plugin. It is a weaker fit if you need dark-mode or brand images without paying, because those generator options require a license key.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • zoontek/react-native-bootsplash4,305 ★ · -3
Star history
Repository2026-09-232026-11-21
zoontek/react-native-bootsplash4.3k4.3k

-3 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Support covers the latest version and two earlier minor series, not every React Native you may still ship

The library follows the React Native releases support policy and states it supports the latest version plus the two previous minor series. That is a narrower window than many apps live in. If your project is pinned to an older React Native, upgrade first or stay on an older release of this library, because support is stated only for versions inside the window.

The package itself is MIT licensed and currently at 7.3.5. Recent versions arrived on 2026-09-14 (7.3.3), 2026-09-30 (7.3.4) and 2026-10-30 (7.3.5), and the last push to the repository was on 2026-10-30, so the code has moved within the past week. Anyone coming from the 6.x line is pointed to MIGRATION.md for the upgrade steps.

The practical check before you install is two lines: find your React Native version, then compare it with the window. The platform badges show Android and iOS, and the generator also accepts web as a target, so a web build with a webpack or public/index.html setup is part of the intended scope.

Installing the npm package is not enough, because native files must be edited by hand

Installation is a package manager command:

bash
$ npm install --save react-native-bootsplash
# --- or ---
$ yarn add react-native-bootsplash

The project then reminds you to go into the `ios` directory and run `pod install`. Run it after installing and after any dependency change that touches native code.

For a bare React Native app the generator creates assets but the entry points are yours to edit. On iOS the target file depends on your React Native version. With 0.88 or newer you edit `ios/YourApp/SceneDelegate.swift`, import RNBootSplash and override `customize(_ rootView: RCTRootView)`. Older versions edit `ios/YourApp/AppDelegate.swift` and place the same override inside `ReactNativeDelegate`. In both, the call is `RNBootSplash.initWithStoryboard("BootSplash", rootView: rootView)`.

On Android you edit `android/app/src/main/java/com/yourapp/MainActivity.kt`. The variant for projects without react-native-screens calls `RNBootSplash.init(this, R.style.BootTheme)` inside `onCreate`, before `super.onCreate(savedInstanceState)`. That ordering matters: the splash theme must be applied before the activity initializes. A mismatch between the file the guide names and what your template contains is where setup time gets lost.

The generate command writes the Android drawable and the iOS storyboard for you

Hand-writing launch screens means a Drawable XML file on Android, a Storyboard file on iOS and several image densities. The bundled CLI does that from one logo. You can inspect it with:

bash
$ npx react-native-bootsplash generate --help
# --- or ---
$ yarn react-native-bootsplash generate --help

The command takes a logo path (PNG or SVG) and these options: `--platforms` (default android,ios,web), `--background` as a hexadecimal color (default #fff), `--logo-width` at @1x in dp (default 100, with roughly 100 recommended) and `--assets-output` (default assets/bootsplash). It also updates config files, per the project. The full example shown in the project passes two more options, `--flavor=main` and `--html=public/index.html`, so those settings exist in addition to the four listed options.

The consequence is that the generator changes files in your repository. Run it on a clean git state so the diff shows exactly what it touched, and rerun it whenever the logo or background changes.

Brand images and dark mode require a purchased license key

The free CLI covers the logo and a single background color. The options `--brand`, `--brand-width` and every `--dark-*` option only work if you also pass `--license-key`. With a key, the generator can output more than 50 files, including logo and brand images in all pixel densities and dark-mode versions, which the project says saves time both at creation and at each later adjustment.

The key is sold through a Gumroad page and, per the project, grants unlimited and unrestricted usage of the generator for the buyer's purposes, so you can run the generation as often as you want. The example in the project uses `--dark-background=00090A` for a dark background.

The consequence for your decision is direct. If your design requires a dark splash that follows system appearance, or a second brand image beneath the logo, the free tier will not produce it through the CLI, and you either buy the key or build those assets by hand. If a single logo on a light color is enough, nothing is gated.

On Expo, the plugin replaces expo-splash-screen and does not run beside it

For Expo projects the setup has two steps. First uninstall the built-in package:

bash
$ npm uninstall expo-splash-screen
# --- or ---
$ yarn remove expo-splash-screen

Then delete the `expo-splash-screen` entry (the one with `image`, `imageWidth`, `resizeMode` and `backgroundColor`) from your plugins, and add this library's plugin. In `app.config.js` or `app.config.ts` you import `bootsplash from "react-native-bootsplash/expo"`, using `require` in the JavaScript file. In `app.json` you list `react-native-bootsplash` as a plugin with an options object.

Two details are easy to miss. The `platforms` array must be explicit, for example android, ios and web. And a license key is passed through the `BOOTSPLASH_LICENSE_KEY` environment variable rather than an option.

The plugin options mirror the CLI: `logo` (required), `background`, `logoWidth`, `assetsOutput`, plus `brand` and `brandWidth` as addon options and an `android.darkContentBarsStyle` flag to enforce system bar style. Because it replaces the Expo package, the Expo path is a swap, and you cannot run both packages side by side.

The npm package ships native sources, an Expo entry, a CLI binary and leaves the addon out

The package.json shows how the install is assembled. The main entry is `./dist/commonjs/index.js` with an ES module build under `./dist/module/`, and the exports map has separate import and require conditions with type declarations for each. A second export, `./expo`, points at the Expo plugin code, and `./app.plugin.js` is exported so Expo can find the plugin by convention. The `bin` field maps to `./cli.js`, which is why `npx react-native-bootsplash` works.

The published files include dist, android, ios, src, RNBootSplash.podspec, cli.js and app.plugin.js, while excluding android/build, android/.cxx, android/.gradle, ios/build and `src/extras/addon`. That last exclusion means the addon source is not part of what npm delivers.

The repository also includes an example app with its own Gemfile, Android and iOS projects, a webpack config and svgs, which is the place to compare your edits against a working setup. Linting uses oxlint and formatting uses prettier.

What you hand over when you adopt it: native edits, a generated asset folder and a possible paid step

Adopting this library moves the splash screen from a placeholder into something your repository owns. You commit the generated assets, usually under assets/bootsplash, plus the Drawable, Storyboard and config changes the generator makes. You also commit the hand edits to SceneDelegate or AppDelegate and to MainActivity.

The tool's one-line promise is to show a splash screen during startup and hide it when you are ready. The hide call itself is not shown in the setup steps covered here, so check the package's own documentation for the exact function before wiring it into your startup code.

For teams, the practical split is clear. A mobile developer owns the native edits and the pod install. A designer or lead decides whether the dark-mode and brand options justify a license key. Everyone should agree on a React Native version that sits inside the support window before the first merge.

Editorial conclusion

Choose it when you want a native splash screen generated from one PNG or SVG, on a bare React Native app or through the Expo plugin. It is a weaker fit if you need dark-mode or brand images without paying, because those generator options require a license key. Before adopting, check your React Native version against the support window and decide who in your team will own the native edits.

Frequently asked questions

What is the purpose of a splash screen in react-native-bootsplash?

It shows a native screen while the app starts, and you hide it when the app is ready. The library generates the Android drawable and iOS storyboard from a PNG or SVG logo.

How to use react-native-bootsplash?

Install it with npm install --save react-native-bootsplash or yarn add, run pod install in the ios directory, then generate assets with the CLI. Bare projects also edit SceneDelegate or AppDelegate and MainActivity.kt, and Expo projects use the plugin.

Is there a react-native-bootsplash alternative inside Expo?

Expo's expo-splash-screen is the package this plugin replaces. Its setup tells you to uninstall expo-splash-screen and remove its plugin entry before adding react-native-bootsplash.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. zoontek/react-native-bootsplash on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zoontek-react-native-bootsplash.svg)](https://hysenlabs.com/projects/zoontek-react-native-bootsplash)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zoontek-react-native-bootsplash.svg)](https://hysenlabs.com/projects/zoontek-react-native-bootsplash)

Was this useful?