Running out of HDD or SSD space? Find large files and clean them up

It is normal for this to be confusing at first: suddenly your website stops loading or email stops arriving, and the real reason turns out to be a full disk. In many cases, you do not need a larger plan immediately. The problem is often old backups, oversized logs, or temporary files that can be cleaned safely.

Here is how to recover control of your storage on both Linux and Windows.

On Linux (VPS or dedicated servers)

If you manage your own server through SSH, finding what is consuming the disk is straightforward.

1. Open a privileged shell

To inspect files across the whole system, start with:

sudo -i

2. Locate the 10 largest files

Use this command to scan the disk. It may take a little time if the server stores a lot of data:

find / -type f -exec du -ah {} + | sort -rh | head -n 10

3. What can you usually delete?

You will see a list of file paths. The items that are often safe to remove include:

.tar.gz or .zip files: old backups you no longer need.
.log files: error logs that have grown too much.
tmp folders: temporary files left behind by old processes.

To delete a specific file, use:

rm file_name

On Windows

In Windows environments, space often disappears because of forgotten downloads, installer files, or temporary system update files.

Use a visual tool: TreeSize Free is light, free, and easy to understand.
Scan the drive: after opening it, choose the disk such as C: and review which folders are consuming the most space.
Clean carefully: you can usually remove old installers and user files, but do not touch the Windows system folder unless you know exactly what you are doing.

Bacan pro tip

Before deleting a very large log file, consider using truncate -s 0 file.log instead. This empties the file while keeping it in place. Some Linux services behave badly if a log file disappears suddenly while they are still writing to it.

Key reminders

Identify before deleting: make sure the file is not part of a database or another critical service.
Check the logs: if a log file is huge, it often means your website is repeating the same error thousands of times.
Prevention matters: keep at least 10% of the disk free so cache and system services can continue working correctly.