CARGO-CLEAN(1) General Commands Manual CARGO-CLEAN(1)

cargo-clean — Remove generated artifacts

cargo clean [options]

Remove artifacts from the target directory that Cargo has generated in the past.

With no options, cargo clean will delete the entire target directory.

When no packages are selected, all packages and all dependencies in the workspace are cleaned.

-p spec…, --package spec

Clean only the specified packages. This flag may be specified multiple times. See cargo-pkgid(1) for the SPEC format.


Displays a summary of what would be deleted without deleting anything. Use with --verbose to display the actual files that would be deleted.


This option will cause cargo clean to remove only the doc directory in the target directory.


Remove all artifacts in the release directory.

--profile name

Remove all artifacts in the directory with the given profile name.

--target-dir directory

Directory for all generated artifacts and intermediate files. May also be specified with the CARGO_TARGET_DIR environment variable, or the config value Defaults to target in the root of the workspace.

--target triple

Clean for the given architecture. The default is the host architecture. The general format of the triple is <arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for a list of supported targets. This flag may be specified multiple times.

This may also be specified with the config value

Note that specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.

-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

--manifest-path path

Path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory.

--frozen, --locked

Either of these flags requires that the Cargo.lock file is up-to-date. If the lock file is missing, or it needs to be updated, Cargo will exit with an error. The --frozen flag also prevents Cargo from attempting to access the network to determine if it is out-of-date.

These may be used in environments where you want to assert that the Cargo.lock file is up-to-date (such as a CI build) or want to avoid network access.


Prevents Cargo from accessing the network for any reason. Without this flag, Cargo will stop with an error if it needs to access the network and the network is not available. With this flag, Cargo will attempt to proceed without the network if possible.

Beware that this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if there might be a newer version as indicated in the local copy of the index. See the cargo-fetch(1) command to download dependencies before going offline.

May also be specified with the net.offline 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.Remove the entire target directory:
cargo clean
2.Remove only the release artifacts:
cargo clean --release

cargo(1), cargo-build(1)