Reclaiming space on elementary OS with the built-in disk usage analyzer

Storage pressure on a Linux laptop can creep up quietly, especially for users juggling large media collections, Flatpak installations, and project archives. elementary OS ships with a graphical tool that turns filesystem scanning into an interactive visual map, making it easier to spot oversized folders without dropping into a terminal. For Australians working within the data allowances of NBN plans from providers like Telstra, Optus, or Aussie Broadband, the bottleneck is frequently the local SSD rather than the connection itself. Knowing how to read the analyzer, and what to safely remove, becomes a practical skill for anyone trying to keep Pantheon running smoothly.

The tool appears in the Applications menu under Utilities, labelled simply as Disk Usage, and traces its lineage to the GNOME project where it is also known as Baobab. It can read any mounted filesystem, including external drives and USB sticks formatted as NTFS or exFAT, which is useful for households mixing Windows and Linux machines. Because elementary OS treats the Files manager and system utilities as native citizens of the Pantheon desktop, the analyzer fits the same minimalist aesthetic, with a single window that expands to show either a treemap or a folder list. Users in cities from Sydney to Perth will find that the same workflow applies whether they are working from a home office in Brisbane or a café in Melbourne.

The real value of the tool lies in helping the user answer two questions: which directories have grown the largest, and which individual files can be safely deleted. Unlike commercial cleaning suites that promise one-click optimisation, this analyzer reports facts and leaves the decisions to the operator. That transparency aligns well with Australian Consumer Law, which expects software products to deliver clear and honest representations rather than hidden background processes. Understanding how the tool gathers its data is the first step towards using it effectively.

Launching and configuring the analyzer

The application can be opened from the Slingshot launcher by typing "Disk Usage" or by selecting it from the Utilities folder in the applications grid. Once running, the window offers two tabs at the top, one for the local filesystem and one for any other mounted volumes. Selecting the root of the system drive begins an initial scan that reads inodes and sizes recursively, then presents the results as a treemap of nested rectangles. Each rectangle corresponds to a folder, and the area is proportional to the bytes consumed.

The toolbar above the chart contains a small preferences icon that opens a dialog for adjusting scan depth and excluded paths. Adding patterns such as /proc or /sys prevents the tool from spending time on virtual filesystems that will never be cleaned. Australian users with multi-boot setups that include a Windows partition can exclude /mnt/windows by editing the preferences, ensuring the scanner focuses only on the elementary OS side. The scan can be paused or cancelled at any time, which matters when running on older spinning disks common in refurbished laptops sold by community recyclers.

Configuration extends to the way sizes are displayed. The dropdown in the toolbar toggles between binary units (KiB, MiB, GiB) and decimal units (KB, MB, GB) to match how storage is advertised on retail SSDs. For users comparing the analyzer's output against the advertised capacity of a 512 GB NVMe drive purchased from a JB Hi-Fi catalogue, switching to decimal units will make the numbers line up more closely. The window also remembers its last position and zoom level between sessions, which is helpful when the same folders are checked regularly for growth.

Reading the treemap and folder list

The treemap view offers an at-a-glance impression of where space is going. Large blocks draw the eye first, often revealing that a single subfolder under ~/Downloads or ~/.var/app is responsible for most of the consumption. Clicking on a block drills into that folder, recalculating the layout so the new level of detail fills the window. Right-clicking opens a context menu with options to open the location in the Files application, copy the path, or delete the contents through a confirmation dialog.

Switching to the folder list tab presents a tabular breakdown sorted by size, with columns for the percentage of the parent, the number of items, and the last modification time. This view is useful when tracking down old project archives or forgotten ISO downloads, a common situation for users who have installed several distributions from USB sticks prepared on Windows machines. Hovering over a row reveals the full path in a tooltip, which can be expanded with the small arrow at the left of the row. Both views are updated live when files change, though a manual rescan via the circular arrow icon is sometimes needed after large deletions.

For Australian readers managing media libraries that include downloaded episodes of programs from ABC iview or podcasts from local creators, the folder list makes it easy to identify which series has accumulated the most data. Sorting by the items count column can also highlight directories stuffed with small files, such as thumbnail caches, that individually weigh little but collectively slow down the file manager. The combination of treemap and list covers both the quick survey and the detailed investigation.

Common space hogs on elementary OS

A few predictable locations tend to dominate the chart. The first is ~/.cache, where applications store thumbnails, recently opened files, and temporary downloads. elementary OS's own Files application writes thumbnails here, and over time the cache can climb into the multi-gigabyte range, particularly after browsing through large photo libraries imported from a phone backup. Clearing the cache is safe, since applications will regenerate thumbnails on the next launch.

Another major contributor is the Flatpak directory at ~/.var/app and the system-wide Flatpak pool under /var/lib/flatpak. Each Flatpak bundles its own runtime, and a system with several sandboxed applications can quietly consume ten or twenty gigabytes. The analyzer's treemap highlights these runtimes as separate blocks, making it obvious which apps are the heaviest. Uninstalling a Flatpak through AppCenter removes both the application and its data, but unused runtimes can linger; these are cleaned with the command flatpak uninstall --unused from a terminal, a step that the analyzer helps justify by showing the precise size savings. AppImage and Snap packages also leave footprints, though elementary OS does not ship with Snap support enabled by default.

System logs under /var/log, old kernel images in /boot, and the contents of /tmp round out the usual suspects. Australian users who travel between states and rely on tethering from a phone plan such as those from Aldi Mobile or Belong may find that system logs grow quickly when the network drops in and out. Inspecting these folders through the analyzer confirms what can be pruned without affecting the running system. For laptops that have been upgraded over time, a folder named lost+found on ext4 partitions may also appear, holding files recovered after an unexpected shutdown.

Safe cleanup strategies

Before deleting anything, it is worth confirming that the folder shown in the analyzer is not actively in use by a running application. Closing the Files manager, pausing sync clients, and quitting browser sessions prevents the deletion of files that are locked or that will simply be recreated. The analyzer itself never modifies the filesystem during a scan, so it can remain open while cleanup takes place in another window. A useful workflow is to let the scan finish, identify the top offenders, then open each path in a separate Files window so deletions happen with full visual context.

For caches and logs, deletion is straightforward and low risk. The Trash in elementary OS retains deleted files until emptied, which provides a safety net if a folder is removed by mistake. Selecting items in the Files manager and pressing the delete key moves them to the Trash, and the analyzer's reported size will shrink on the next rescan. For system-level paths that require elevated permissions, the terminal is the better tool, and sudo rm -rf should be used only when the exact folder has been verified. Australian readers who back up to external drives formatted in exFAT for compatibility with smart TVs or media players should remember that exFAT does not support Unix permissions, and files removed from such drives bypass the Trash.

A regular quarterly cleanup, scheduled around daylight changes or the start of a new financial year, is a habit that keeps the system responsive. Many Australian households use the April end of financial year as a prompt for digital housekeeping, and the disk analyzer fits neatly into that routine. Documenting which folders were pruned and why makes it easier to repeat the process or to teach the workflow to a family member. After cleanup, the analyzer can be used to verify the results, confirming that the freed space matches expectations.

Comparing the analyzer with command-line alternatives

For users comfortable in the terminal, the analyzer complements rather than replaces utilities such as du, ncdu, and Filelight. Each tool has strengths that make it suitable for different tasks. The summary below shows how the graphical analyzer stacks up against these alternatives for typical elementary OS scenarios.

The graphical analyzer wins for users who prefer a visual summary and who rarely need to script the output. ncdu is faster on remote servers or very large filesystems where rendering a treemap would slow the scan, and it can be installed from the elementary OS AppCenter. du remains the foundation of most reporting scripts and can be combined with sort and head to produce the same insights from a single shell pipeline. Filelight, the KDE equivalent, offers a similar treemap experience for those who also run Plasma in a virtual machine.

Choosing between them depends on context. A Melbourne-based developer working over a slow link to a remote build server may keep ncdu handy for that host while preferring the Pantheon-native analyzer for the laptop in front of them. For Australian small businesses running elementary OS on point-of-sale terminals, the GUI tool provides a clear record for staff who may not have terminal access. Keeping at least two of these tools available covers the gap when the desktop environment fails to start and a live USB session is needed for triage.

What to keep in mind

The built-in disk usage analyzer is a dependable way to map storage on elementary OS without installing extra software, and it follows the same minimalist philosophy that defines the Pantheon desktop. Reading the treemap and the folder list together turns a vague sense that the drive is full into a precise list of folders responsible for the growth. Combining the analyzer with safe cleanup habits, periodic reviews of Flatpak runtimes, and a healthy respect for the Trash provides a sustainable approach to storage management. For Australian readers juggling NBN data caps, multi-state travel, and a mix of Windows and Linux hardware, the tool is a practical ally in keeping the system lean and predictable.