btop: A Resource Monitor That Puts Terminal UX First
A monitor of resources
At a glance
- What is it?
- btop is a C++ terminal resource monitor for Linux, macOS, and the BSDs. It offers CPU and GPU monitoring boxes in one TUI, with themes, keybindings, and a configurability section.
- Who is it for?
- Adopt btop if you live in a terminal and want a single, visually rich view of CPU, memory, disks, network, and GPUs without leaving the shell. It is a strong fit for Linux users on current distros, and for macOS and BSD users willing to compile from source.
- Can I use it commercially?
- Yes. Apache-2.0 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 C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- aristocratos/btop35,414 ★ · +1,341
| Repository | 2026-08-18 | 2026-11-15 |
|---|---|---|
| aristocratos/btop | 34.1k | 35.4k |
1,341 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What btop Solves and Who Needs It
System administrators and developers often juggle multiple terminal tools: one for CPU, another for memory, a third for disk I/O. btop consolidates those into a single TUI with a unified keyboard-driven interface. The README describes it as a monitor of resources, and its README covers CPU and GPU monitoring boxes among other views. It targets people who prefer the terminal over GUI system monitors like GNOME System Monitor or Windows Task Manager. The intended audience is clear from the platform list: Linux, macOS, FreeBSD, NetBSD, and OpenBSD. If you manage servers over SSH or work on a headless workstation, btop replaces a handful of separate utilities with one consistent view.
The Architecture: C++ Core, GPU via Dynamic Libraries
btop is written in C++, which matters for performance. A resource monitor redraws constantly, so a low-level language keeps overhead low. The README notes that GPU support relies on loading dynamic GPU libraries at runtime. That design choice has a direct consequence: GPU support will not work when static linking is used. The release binaries, as stated in the news section, do not have GPU support enabled. Only a custom compile with the right flags and libraries enables it. The project also has a separate Windows port, btop4win, which is a different codebase. Platform support was added incrementally: macOS in v1.1.0, FreeBSD in v1.2.0, OpenBSD in v1.3.0, NetBSD in v1.4.0.
Getting It Running: Packages, Binaries, and Compilation
The simplest path is a distro package. The README links to Repology, which tracks package availability across many distributions. For Linux, the project provides statically compiled binaries in each release for a range of architectures. That is a practical fallback if your distro lacks a package or you need a newer version. For macOS, Homebrew and MacPorts are mentioned as dependency sources, and releases include both x86 and ARM64 binaries. Compilation requires GCC 11 or later. The README's 2021 news entry gives explicit clone-and-gmake commands for the macOS and FreeBSD development branches, and it has separate compilation sections per platform. A snap package also exists (the README has an Installing the snap section), which offers an alternative install route on Linux distributions that support snap.
GPU Monitoring: A Feature With Strings Attached
GPU support is one of btop's headline features, but it is not turnkey. The news entry from November 2023 explains that GPU monitoring was added for Linux, with keys 5, 6, 7, and 0 to toggle GPU boxes. It also notes that GPU stats can be embedded in the CPU box, though less verbosely. The catch: release binaries and continuous builds do not include GPU support. You must compile from source with dynamic library loading enabled, and static linking breaks it. Intel GPU support, added in v1.4.0, only exposes utilization, power usage, and clock speed. That is a genuine limitation. If you need GPU metrics and do not want to compile, btop is the wrong tool. The documentation is honest about this, which is refreshing, but it means the feature is for tinkerers, not casual users.
Theming and Configurability: Where btop Shines
The README has a dedicated Themes section, and the project ships with multiple themes. Theming is not cosmetic; it affects readability on different terminal backgrounds and color schemes. The keybindings are extensive, with a help menu accessible in the interface. The README has a Configurability section, and you can toggle the GPU boxes with keys 5, 6, 7 and 0 and adjust the CPU box's GPU display through the cpu options menu.
Cross-Platform Reality: Not All Ports Are Equal
Platform support is a double-edged sword. The README lists Linux, macOS, FreeBSD, NetBSD, and OpenBSD, plus a separate Windows port. But the maturity varies. The news entry from 2021 mentions memory leaks on the macOS branch and issues with process CPU usage calculation on both macOS and FreeBSD. Those notes date from 2021 development of the ports. NetBSD support was added in v1.4.0, and OpenBSD in v1.3.0, but the README does not state whether release binaries exist for those platforms. The README links a continuous-build-macos workflow, but source shows no continuous builds for the BSDs. If you are on a niche BSD, expect to compile. The project's maintainer has been honest about gaps, such as the note that no release binaries for FreeBSD were provided as of v1.2.0.
Maintenance, License, and Contribution Rules
The project is actively maintained. The last push was October 28, 2026, and the latest release is v1.4.8 (October 25, 2026). The release cadence shows regular updates: v1.4.6 in December 2025, v1.4.7 in May 2026, and v1.4.8 in October 2026. The license is Apache-2.0, which is permissive for commercial use and modification, though it is not legal advice. The contribution guidelines, updated in March 2026, are notable: AI-generated code must be marked, and 'vibe coded' pull requests where the author does not understand the code will be dismissed. This is a direct stance on a current issue in open source. It means if you plan to contribute, you must disclose AI assistance and be able to explain your code. That is a maintenance cost for contributors, but it protects the codebase quality.
Alternatives and the Right Tool for the Job
The most obvious alternative is htop, which is written in C and available in most distro package managers. If you need a minimal monitor on a low-resource server, htop's smaller footprint may win. On a modern desktop, btop's visual density and GPU support make it a better choice. The README's mention of btop4win shows the project is not limited to Unix-like systems, but that port is a separate effort. For Windows users, the native Task Manager might be simpler than installing a third-party TUI.
Editorial conclusion
Adopt btop if you live in a terminal and want a single, visually rich view of CPU, memory, disks, network, and GPUs without leaving the shell. It is a strong fit for Linux users on current distros, and for macOS and BSD users willing to compile from source. Avoid it if you need a zero-config tool for ancient hardware or if your workflow depends on GPU metrics from release binaries, since those lack GPU support. Before adopting, verify that your platform has a packaged build or that you can meet the GCC 11 requirement, and check the GPU compatibility section for your specific hardware. The project is actively maintained, with v1.4.8 released in October 2026, so the risk of stagnation is low.
Frequently asked questions
What is btop used for?
btop is described as a monitor of resources, written in C++ and licensed Apache-2.0, and the README has sections for features, themes, keybindings, prerequisites and configurability. On Linux it adds GPU monitoring boxes that are toggled with the keys 5, 6, 7 and 0, where 5 is GPU 1 and 6 is GPU 2.
Can you get Btop for Windows?
Windows support is a separate project. The page points to a first release of btop4win at github.com/aristocratos/btop4win, dated 28 August 2022. This repository's build instructions target Unix-like systems and the README says GCC 11 is required for compilation.
What are the key differences between Btop and bpytop?
btop++ is the C++ monitor in this repository, with themes, configurability and keybindings; per-release detail is in CHANGELOG.md and the news entries, which go back to the first Linux release in September 2021.
How does Btop monitor GPU usage?
GPU stats and graphs appear in per-device boxes toggled with keys 5, 6, 7 and 0, and can also be shown in the Cpu box in a less verbose form configured through the cpu options menu. For Intel GPUs only utilization, power usage and clock speed are available, and the release binaries and continuous builds do not have GPU support enabled because it requires dynamic GPU libraries.
Official sources
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.
[](https://hysenlabs.com/projects/aristocratos-btop)Star history chart for your README
[](https://hysenlabs.com/projects/aristocratos-btop)Was this useful?