A customizable cross-platform graphical process/system monitor for the terminal.
Supports Linux, macOS, and Windows. Inspired by gtop, gotop, and htop.
](https://github.com/ClementTsang/bottom/actions?query=branch%3Amaster)
[
](https://crates.io/crates/bottom)
[
](https://clementtsang.github.io/bottom/stable)
[
](https://clementtsang.github.io/bottom/nightly)
Demo using the Gruvbox theme (--color gruvbox), along with IBM Plex Mono and Kitty
As (yet another) process/system visualization and management application, bottom supports the typical features:
Graphical visualization widgets for:
with support for zooming in/out the current time interval displayed.
Widgets for displaying info about:
A process widget for displaying, sorting, and searching info about processes, as well as support for:
Cross-platform support for Linux, macOS, and Windows, with more planned in the future.
Customizable behaviour that can be controlled with command-line flags or a config file, such as:
Some other nice stuff, like:
And more!
You can find more details in the documentation.
bottom officially supports the following operating systems and corresponding architectures:
x86_64, aarch64)x86_64, i686, aarch64)x86_64, i686)These platforms are tested to work for the most part and issues on these platforms will be fixed if possible. Furthermore, binaries are expected to be built and tested using the most recent version of stable Rust.
For more details on supported platforms and known problems, check out the documentation.
bottom may work on a number of platforms that aren't officially supported. Note that unsupported platforms:
Note that some unsupported platforms may eventually be officially supported (e.g., FreeBSD).
A non-comprehensive list of some currently unofficially supported platforms that may compile/work include:
x86_64)armv6, armv7, powerpc64le, riscv64gc)For more details on unsupported platforms and known problems, check out the documentation.
Installation via cargo can be done by installing the bottom crate:
```bash
rustup update stable
cargo install bottom --locked
cargo +stable install bottom --locked
cargo +stable install bottom ```
There is an official package that can be installed with pacman:
bash
sudo pacman -S bottom
A .deb file is provided on each stable release and
nightly builds for x86, aarch64, and armv7
(note stable ARM builds are only available for 0.6.8 and later). If you want to install this way, do something like:
```bash
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.9.1/bottom0.9.1amd64.deb sudo dpkg -i bottom0.9.1amd64.deb
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.9.1/bottom0.9.1arm64.deb sudo dpkg -i bottom0.9.1arm64.deb
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.9.1/bottom0.9.1armhf.deb sudo dpkg -i bottom0.9.1armhf.deb ```
bottom is available as a snap:
```bash sudo snap install bottom
sudo snap connect bottom:mount-observe sudo snap connect bottom:hardware-observe sudo snap connect bottom:system-observe sudo snap connect bottom:process-control ```
Available in COPR:
bash
sudo dnf copr enable atim/bottom -y
sudo dnf install bottom
Available in the official Gentoo repo:
bash
sudo emerge --ask sys-process/bottom
bash
nix-env -i bottom
bash
sudo eopkg it bottom
bash
sudo xbps-install bottom
bash
brew install bottom
bash
sudo port selfupdate
sudo port install bottom
bash
scoop install bottom
Chocolatey packages are located here:
bash
choco install bottom
The winget package can be found here:
```bash winget install bottom
winget install Clement.bottom ```
You can uninstall via Control Panel, Options, or winget --uninstall bottom.
You can also manually install bottom as a Windows program by going to the latest release
and installing via the .msi file.
There are a few ways to go about doing this manually. Note that you probably want to do so using the most recent version of stable Rust, which is how the binaries are built:
```bash
rustup update stable
curl -LO https://github.com/ClementTsang/bottom/archive/0.9.1.tar.gz tar -xzvf 0.9.1.tar.gz cargo install --path . --locked
git clone https://github.com/ClementTsang/bottom cd bottom cargo install --path . --locked
cargo install --git https://github.com/ClementTsang/bottom --locked
RUSTFLAGS="-C target-cpu=native" cargo install --path . --locked ```
You can also use the pre-built release binaries manually:
To use, download and extract the binary that matches your system. You can then run by doing:
bash
./btm
or by installing to your system following whatever the procedure is for installing a binary to your system.
The release binaries are packaged with shell auto-completion files for bash, fish, zsh, and Powershell. To install them:
btm.bash to $XDG_CONFIG_HOME/bash_completion or /etc/bash_completion.d/.btm.fish to $HOME/.config/fish/completions/._btm to one of your $fpath directories._btm.ps1 to your PowerShell
profile.The individual auto-completion files are also included in the stable/nightly releases as completion.tar.gz.
You can run bottom using btm.
btm -h for a quick overview or btm --help for more details.? inside bottom or refer to the documentation.You can find more information on usage in the documentation.
bottom accepts a number of command-line arguments to change the behaviour of the application as desired. Additionally, bottom will automatically generate a configuration file on the first launch, which one can change as appropriate.
More details on configuration can be found in the documentation.
If some things aren't working, give the troubleshooting page a look. If things still aren't working, then consider opening a question or filing a bug report.
Whether it's reporting bugs, suggesting features, maintaining packages, or submitting a PR, contribution is always welcome! Please read CONTRIBUTING.md for details on how to contribute to bottom.
Thanks to all contributors:
This project is very much inspired by gotop, gtop, and htop.
This application was written with many, many libraries, and built on the work of many talented people. This application would be impossible without their work. I used to thank them all individually but the list got too large...
And of course, another round of thanks to all the contributors and package maintainers!
