Btop vs Top Command: 6 Easy Tests and Mistakes to Avoid

The top command has shown Linux processes in a terminal for decades, and btop is one of the most popular modern replacements: it draws CPU, memory, disk, network and process boxes with graphs, mouse support and menus. The first version of this article praised btop in general terms and got several facts wrong, for example that btop "requires root privileges" and that it can "add custom metrics". This rewrite installs btop on four distributions, runs it as a normal user inside tmux, and copies the real screen with tmux capture-pane, so every screen below is what btop actually drew.

Lab note: the tests ran in podman containers on 7 November 2026 (Debian 13, Ubuntu 24.04, Fedora 43, Rocky Linux 9). A container sees the host's CPUs and memory, so the numbers are from the lab machine. Only the process box is shown, to keep host details out of the screenshots. Arch Linux was not tested.

Install btop next to the top command: versions differ

The btop README lists sudo apt install btop for Ubuntu/Debian, sudo dnf install btop for Fedora and EPEL first for RHEL, Rocky and AlmaLinux 8+. The version you get depends on the distribution:

== docker.io/library/debian:13: apt install btop
$ btop --version
btop version: 1.3.2

== docker.io/library/ubuntu:24.04: apt install btop
$ btop --version
btop version: 1.3.0

== fedora:43: dnf install btop
$ btop --version
btop version: 1.4.7

On Rocky Linux 9 the old post's dnf install btop fails until EPEL is enabled:

$ dnf install -y btop
No match for argument: btop
Error: Unable to find a match: btop
$ dnf install -y epel-release; dnf install -y btop
btop version: 1.4.7

The latest upstream release on GitHub was v1.4.8 (25 October 2026) when this was written. The README also points to a PPA for an up-to-date btop on Ubuntu 22.04 and newer. The version matters because the options changed between 1.3 and 1.4.

Options: 1.3.2 and 1.4.7 are not the same

Debian 13's btop 1.3.2 prints this help:

usage: btop [-h] [-v] [-/+t] [-p <id>] [-u <ms>] [--utf-force] [--debug]

optional arguments:
  -h, --help            show this help message and exit
  -v, --version         show version info and exit
  -lc, --low-color      disable truecolor, converts 24-bit colors to 256-color
  -t, --tty_on          force (ON) tty mode, max 16 colors and tty friendly graph symbols
  +t, --tty_off         force (OFF) tty mode
  -p, --preset <id>     start with preset, integer value between 0-9
  -u, --update <ms>     set the program update rate in milliseconds
  --utf-force           force start even if no UTF-8 locale was detected

Fedora's 1.4.7 has a new layout and new options, among them a start-up process filter and a config path:

  -c, --config <file>     Path to a config file
  -d, --debug             Start in debug mode with additional logs and metrics
  -f, --filter <filter>   Set an initial process filter
      --force-utf         Override automatic UTF locale detection
  -l, --low-color         Disable true color, 256 colors only
  -p, --preset <id>       Start with a preset (0-9)
  -t, --tty               Force tty mode with ANSI graph symbols and 16 colors only

So btop -f nginx works on 1.4.x but not on Debian 13, and --utf-force became --force-utf. Check btop --help on your own system before you copy a command from a blog; the top command options, by contrast, have hardly changed.

The first error: no UTF-8 locale

The README says btop needs a UTF-8 locale. In a minimal container or an SSH session without LANG, btop refuses to start:

ERROR: No UTF-8 locale detected!
Use --utf-force argument to force start if you're sure your terminal can handle it.
exit=1

Set a UTF-8 locale for the session (here LANG=C.UTF-8) and it starts normally. The plain top command has no such requirement, which is one reason it is still the safer choice on rescue systems.

Btop vs the top command as a normal user

The old FAQ said btop "typically requires root privileges". It does not. In the lab, root started sleep 1000, the normal user demo started a busy yes > /dev/null, and demo ran btop -p 0 -u 1000. The process box listed every process, including root's, sorted by CPU:

btop process box as a normal user, a modern top command alternative
btop 1.3.2 run by a normal user: root's processes are listed too.
│    Pid: Program:         Command:        Threads: User:       MemB       Cpu%  │
│     834 yes              yes                    1 demo        1.3M ⣀⣀⣀⣀⣀  4.9  │
│     840 tmux: server     tmux new-session -d    1 demo        4.3M ⣀⣀⣀⣀⣀  0.0  │
│     842 btop             btop -p 0 -u 1000      2 demo        5.6M ⣀⣀⣀⣀⣀  0.0  │
│       1 bash             bash -c 00             1 root        2.9M ⣀⣀⣀⣀⣀  0.0  │
│     830 sleep            sleep 1000             1 root        1.4M ⣀⣀⣀⣀⣀  0.0  │

The yes process keeps one core busy, yet shows 4.9%: the header says per-core is off, so the value is a share of all CPUs. The top command counts per CPU by default (its "Irix mode" in the top(1) man page), so check this setting before you compare the two tools.

As with the top command, root matters only for actions on other users' processes. The README describes an optional setuid install for that; it is not needed to look at the system.

Filter and kill a process in btop instead of the top command

Press f, type text, and press Enter (the top command uses o for a similar filter). The filter matches the command line, not only the program name, so a filter of sleep also kept the root bash whose command line contains the word:

╭─┐⁴proc┌┐f sleep del┌───────────────────┐per-core┌┐reverse┌┐tree┌┐< cpu lazy >┌─╮
│    Pid: Program:         Command:        Threads: User:       MemB       Cpu%  │
│       1 bash             bash -c                1 root        2.9M ⣀⣀⣀⣀⣀  0.0  │
│     830 sleep            sleep 1000             1 root        1.4M ⣀⣀⣀⣀⣀  0.0  │

Then Down selects the first row, and k opens the kill dialog. In btop 1.3.2 the key sends SIGKILL, not the gentle SIGTERM; the box at the bottom also offers terminate and signals:

   Send signal: 9 (SIGKILL)
       To PID: 1 (bash)

Confirming as the normal user on a root process fails, as it should:

           Failure:
    Insufficient permissions to send signal!

The same steps on demo's own yes process (filter yes, Down, k, Enter) worked:

   Send signal: 9 (SIGKILL)
       To PID: 834 (yes)

$ pgrep -a -x yes
(no yes process)

So btop does save the old top command routine of "find the PID, then run kill", but it uses SIGKILL by default, which gives the program no chance to clean up. For a database or a service, use terminate (SIGTERM) or systemctl stop instead.

Configuration and what btop cannot do that the top command can

On the first run btop writes its config file, a log and a themes folder for the user:

$ ls -l ~demo/.config/btop/
total 16
-rw-rw-r--. 1 demo demo 9344 Nov  7 05:40 btop.conf
-rw-rw-r--. 1 demo demo  303 Nov  7 05:40 btop.log
drwxrwxr-x. 1 demo demo    0 Nov  7 05:39 themes
$ grep -E "^(update_ms|proc_sorting|proc_tree|color_theme|shown_boxes) " ~demo/.config/btop/btop.conf
color_theme = "Default"
shown_boxes = "cpu mem net proc"
update_ms = 1000
proc_sorting = "cpu lazy"
proc_tree = False

Everything in this file can also be changed from the built-in menu (the README lists a "UI menu for changing all config file options"), plus themes and layout presets. What the README does not list is custom metrics, so that claim from the old article is removed. btop also has no batch mode for scripts. When you need numbers in a file or a cron job, the top command is still the tool, because -b prints plain text (see the top(1) man page):

$ top -b -n 1 -o %CPU | head -12
top - 05:40:32 up  1:35,  0 users,  load average: 2.52, 2.63, 2.58
Tasks:   4 total,   1 running,   3 sleeping,   0 stopped,   0 zombie

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
      1 root      20   0    4064   3168   2872 S   0.0   0.0   0:00.03 bash
    830 root      20   0    2588   1640   1536 S   0.0   0.0   0:00.00 sleep

When to use btop and when the top command

TaskBetter toolWhy (from the lab)
Quick visual check of CPU, memory, disks, networkbtopall boxes on one screen, graphs, mouse
Find and stop a runaway processbtopfilter, select, signal in one place (watch out: k = SIGKILL)
Minimal system, no UTF-8 locale, serial consoletopbtop exits with "No UTF-8 locale detected!"
Logging, scripts, crontoptop -b -n 1 prints plain text; btop has no batch mode
Comparing CPU % between toolscheck settingsbtop showed 4.9% for one busy core, per-core off

For more everyday commands, see 9 essential bash commands for Linux and 15 "useless" Linux commands, which covers ps and kill.

Conclusion

btop is a real improvement over the top command for interactive monitoring: it runs fine as a normal user, shows everything on one screen, and lets you filter and signal processes without typing a PID. Know its limits: install it from EPEL on RHEL-type systems, expect different options on 1.3.x and 1.4.x, give it a UTF-8 locale, remember that k sends SIGKILL, and keep the top command for scripts and minimal systems.

Comments

Popular posts from this blog

How to Play Minecraft Bedrock Edition on Linux: A Comprehensive Guide for Tech Professionals

Linux desktop frozen? My 5 go-to tricks to try - before forcing a hard reboot

The Ultimate Guide: How to Set Up DXVK in Wine on Linux for Enhanced Gaming Performance