BUNDLE-BINSTUBS(1) General Commands Manual BUNDLE-BINSTUBS(1)

# [NAME](#NAME)

**bundle-binstubs** - Install the binstubs of the listed gems

# [SYNOPSIS](#SYNOPSIS)

**bundle binstubs** *GEM\_NAME* \[--force] \[--standalone] \[--all-platforms]

# [DESCRIPTION](#DESCRIPTION)

Binstubs are scripts that wrap around executables. Bundler creates a small Ruby file (a binstub) that loads Bundler, runs the command, and puts it into **bin/**. Binstubs are a shortcut-or alternative- to always using **bundle exec**. This gives you a file that can be run directly, and one that will always run the correct gem version used by the application.

For example, if you run **bundle binstubs rspec-core**, Bundler will create the file **bin/rspec**. That file will contain enough code to load Bundler, tell it to load the bundled gems, and then run rspec.

This command generates binstubs for executables in **GEM\_NAME**. Binstubs are put into **bin**, or the directory specified by **bin** setting if it has been configured. Calling binstubs with \[GEM \[GEM]] will create binstubs for all given gems.

# [OPTIONS](#OPTIONS)

[**--force**](#force)

Overwrite existing binstubs if they exist.

[**--standalone**](#standalone)

Makes binstubs that can work without depending on Rubygems or Bundler at runtime.

[**--shebang=SHEBANG**](#shebang=SHEBANG)

Specify a different shebang executable name than the default (default 'ruby')

[**--all**](#all)

Create binstubs for all gems in the bundle.

[**--all-platforms**](#all~2)

Install binstubs for all platforms.

April 2026

---

Document: bundle-binstubs(1) from ruby4.0-bundler 4.0.23-r0 (Chainguard OS)
Source: https://github.com/rubygems/rubygems