How to clear Zsh history and free up space in the terminal

Is your terminal running slowly? Learn how to manage and compress your .zsh_history file to optimize shell performance and remove duplicate commands.

Marcio Cunha•3 min

Also available in:Português Español

Summary

The .zsh_history file accumulates unnecessary commands that can impact terminal startup time.
Removing duplicates improves history readability and simplifies the search for frequently used commands.
Setting size limits via environment variables prevents the file from growing indefinitely.
The use of sort and uniq commands allows for a deep cleanup of redundant or invalid entries.
Routine history maintenance is equivalent to cleaning temporary files, such as when you clean Docker cache .

Why is your Zsh history weighing down your system?

The Zsh (Z Shell) is one of the most powerful tools for Linux or macOS users, but it has a hoarding habit: saving every command you type into the .zsh_history file. Over months, this file grows silently. When it reaches tens of megabytes, the shell might show slight delays when opening a new tab or performing quick searches with Ctrl+R, which degrades the user experience.

In practice, this means your shell needs to load that entire list into memory every time you start a session. If you have ever felt your terminal taking a few extra milliseconds to respond, it is a clear sign that history management has been neglected. Just as we perform maintenance on Docker resources, taking care of your history is a vital step to maintain the performance of your development environment.

How to identify and diagnose file size

Before deleting anything, we need to measure the impact. The history file is located in the root of your home directory. You can quickly check its actual size through the terminal. Use the ls -lh command to view the size in a human-readable format.

Open your terminal and execute the following command to see how many commands are currently stored:

wc -l ~/.zsh_history

If this number is in the thousands, you likely have entries you no longer need. Additionally, repeated commands take up unnecessary space, decreasing the efficiency of quick-search tools that read this file.

Removing duplicates and optimizing .zsh_history

Clearing history does not necessarily mean deleting everything. We can use standard Unix utilities to organize and filter what is important. The sort command organizes lines and uniq removes sequential repetitions. However, to effectively remove all duplicates across the entire file, we need a more robust approach.

To clear your history, follow these steps carefully:

Create a backup of your current history:
```
cp ~/.zsh_history ~/.zsh_history_backup
```
Clean the original file by filtering only for unique entries:
```
sort -u ~/.zsh_history -o ~/.zsh_history
```
Reload your Zsh configuration file to apply the changes:
```
source ~/.zshrc
```

After this process, your file will be much leaner and better organized, allowing for smoother navigation through your command history.

How to prevent infinite growth in the future

The best way to manage history is to configure Zsh to handle the size automatically. In your ~/.zshrc file, you can define variables that limit the number of saved commands and how they are written. This is crucial, just as we learn to structure data correctly in the terminal before processing it.

Add or edit the following lines in your ~/.zshrc:

HISTSIZE=10000SAVEHIST=10000setopt HIST_IGNORE_ALL_DUPSsetopt HIST_SAVE_NO_DUPS

The HISTSIZE controls how many commands stay in memory during the session, while SAVEHIST defines the limit saved to disk. The HIST_IGNORE_ALL_DUPS and HIST_SAVE_NO_DUPS options ensure that even if you type the same command multiple times, only the last occurrence will be kept in the history file.

Final Considerations

Keeping the .zsh_history file under control is not just about freeing up a few kilobytes of storage, but about ensuring your main work tool is fast and efficient. By applying duplicate filters and configuring history limits, you reduce your system's I/O (input/output) load and improve your productivity.

Remember that an optimized development environment consists of constant small adjustments. Whether you are clearing your shell history or performing hardware tests on electronic components, the focus should always be on maintaining the stability and performance of your personal setup.