cargo-uninstall — Remove a Rust binary

cargo uninstall [options] [spec…]

This command removes a package installed with cargo-install(1). The spec argument is a package ID specification of the package to remove (see cargo-pkgid(1)).

By default all binaries are removed for a crate but the --bin and --example flags can be used to only remove particular binaries.

The installation root is determined, in order of precedence:

--root option
CARGO_INSTALL_ROOT environment variable
CARGO_HOME environment variable

-p, --package spec

Package to uninstall.

--bin name

Only uninstall the binary name.

--root dir

Directory to uninstall packages from.

-v, --verbose

Use verbose output. May be specified twice for “very verbose” output which includes extra output such as dependency warnings and build script output. May also be specified with the term.verbose config value

-q, --quiet

Do not print cargo log messages. May also be specified with the term.quiet config value

--color when

Control when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the terminal.
always: Always display colors.
never: Never display colors.

May also be specified with the term.color config value


If Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). See the rustup documentation for more information about how toolchain overrides work.

--config KEY=VALUE or PATH

Overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times. See the command-line overrides section for more information.


Changes the current working directory before executing any specified operations. This affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. This option must appear before the command name, for example cargo -C path/to/my-project build.

This option is only available on the nightly channel and requires the -Z unstable-options flag to enable (see #10098

-h, --help

Prints help information.

-Z flag

Unstable (nightly-only) flags to Cargo. Run cargo -Z help for details.

See the reference for details on environment variables that Cargo reads.

0: Cargo succeeded.
101: Cargo failed to complete.

1.Uninstall a previously installed package.
cargo uninstall ripgrep

cargo(1), cargo-install(1)