Beginners Guide for Pstree Command on Linux

Linux TLDR
Last Updated:
Reading time: 4 minutes

The ps and top commands are the most popular and commonly used command-line programs to view the currently running processes on your Linux system.

The pstree is also similar to them, except that it outputs the running process in the form of a tree; if no arguments are passed, then it will list the complete process.

This way of inspecting the running processes in the form of a hierarchy is more convenient and visually appealing, especially for beginners (even if they don’t understand the output).

In this article, you will learn how to use the pstree command and how to use the different available options with it (with practical examples).

Tutorial Details

Difficulty LevelLow
Root or Sudo PrivilegesNo
OS CompatibilityUbuntu, Manjaro, Fedora, etc.
Internet RequiredNo

Syntax of the Pstree Command

The pstree command takes two arguments: one is the option, and the other is the pid or username; both of these arguments are optional.

$ pstree [OPTION] [PID or USERNAME]

If you specify the PID along with the command, the hierarchy will start from the referenced PID; otherwise, it will start from PID 1 (which is your init process) as the default.

And if you specify the username, then the pstree will display the running process under the referenced username, but note that the pstree only accepts one argument, and that argument can be either username or pid.

The following is a list of known options:

-aDisplay the command-line arguments for the running processes.
-cDisplay the identical branches separately.
-HHighlight the referenced process in the tree.
-hHighlight the parent process for each running process in the tree.
-gDisplay the GID along with each process in the tree.
-lDon’t truncate long lines.
-nSort output based on PID.
-pDisplay the PID along with processes.
-uDisplay the owner/user of each process.
-sShow the parent process for the referenced process.
-THide threads in the process tree.

Displaying the Running Process in Hierarchy

When you run the following command without any options or arguments, it will return a long list of processes that are currently running on your system in the form of a hierarchy.

$ pstree


Displaying the running processes in the form of a tree

As you can see from the above output, without any arguments, this command will list all the processes starting from your first process, which is systemd in this case.

One thing you should note is that when you pass the pstree command without any options, it merges the identical branches by putting them in square brackets and prefixing them based on their repetition.

For example, the following branch:

udisksd -+- {udisksd}
               | -{udisksd}
               | -{udisksd}
               | -{udisksd}

Will becomes:


Although, you can easily separate the identical branches by following the next section,

Displaying the Identical Branches Separately

Use the β€œ-c” flag to display the identical branches separately without merging them together.

$ pstree -c


Displaying the running processes without merging the identical ones

As you are avoiding merging the identical processes together, which indirectly affects the size of this command output, although you can use the less or more command to conveniently view the output.

Displaying the Command-line Arguments for the Running Processes in the Tree

By default, the pstree does not show you the command-line argument that started the process in the first place.

However, you can use the β€œ-a” flag to view the command-line arguments for all the running processes in the tree.

$ pstree -a


Displaying the command-line argument for each running process in the tree

Displaying the PID for Each Process in the Tree

The most important information you might be looking for from the pstree output is the process ID (or PID) to perform various tasks like killing the process.

Using the β€œ-p” flag will list all the running processes along with their PIDs in the tree.

$ pstree -p


Displaying the individual processes with their PIDs

Sorting the Output Based on PIDs

By default, the output is sorted based on the parent process name, although you can sort the output based on the process PIDs by using the β€œ-n” flag along with the β€œ-p” flag.

$ pstree -pn


Sorting the process based on numeric PIDs

Displaying the PGIDs for Each Process in the Tree

The β€œ-g” flag will display the process with the process group ID or PGID of the first member of the process group.

$ pstree -g


Displaying each process along with its PGID

Highlight the Parent Process for Each Running Process in the Tree

The β€œ-h” flag will highlight the parent process for each running process from the output to make it more convenient for you to spot the parent process.

$ pstree -h


Highlight the parent process for each running processes

Highlight the Referenced Process in Tree

In the previous section, you learned how to highlight all parent processes; however, to highlight a specific process, you can use the β€œ-H” flag with the process ID (or PID) as an argument.

$ pstree -pH 885 


Highlight the specific process in the tree

Hiding the Thread in the Process Tree

The β€œ-T” flag will hide the thread from the process tree to make the output a bit shorter and simpler.

$ pstree -T


Hiding the thread from the process tree

Display the Specific Process Tree in the Output

Once you found the PID for any particular process, you can use that PID to only output the tree for that specific process.

$ pstree -a 910

The β€œ-a” flag is used to expand the process branches.

Output Specific Process Tree

That was the last example for the pstree command.


Although, this command-line tool is great and makes it easier for beginners to understand the structure of running processes in Linux in the form of a simple tree.

If you have any more tools similar to this in your hands, then let me know in the comment section.

Till then, peace!

Join The Conversation

Users are always welcome to leave comments about the articles, whether they are questions, comments, constructive criticism, old information, or notices of typos. Please keep in mind that all comments are moderated according to our comment policy.