Most capable Mac storage tools, VolumeLens included, offer both a visual map and a sortable list of the same underlying scan. They're not redundant — each view answers a different kind of question faster, and knowing which one to reach for saves real time.
What a visual map is actually good at
A treemap's core strength is proportional pattern recognition. Human vision is very fast at spotting "that one block is way bigger than everything around it" without reading a single number — it's a perceptual judgment, not an arithmetic one. That makes a map the right tool specifically for the "I have no idea where the space went" starting point, where you don't yet have a hypothesis to test and need the data to suggest one to you.
A map is weaker once you're past that stage and know roughly what you're looking for. If a folder contains forty items of broadly similar size, the rectangles become similarly sized too, and reading precise rank order from similarly-sized shapes is slower than reading a sorted number column. Maps are also weaker for text-based tasks — finding every file with a specific extension, say — since that's not something proportional area naturally encodes.
What a list view is actually good at
A sortable list — name, size, date, path, sorted by any column — is the right tool once you have a specific question with a text or numeric answer. "What are the twenty largest files on this drive." "What hasn't been touched in two years." "Which of these files match a specific name pattern." Sorting and filtering handle all of these more precisely than a visual map does, because the underlying question is really about rank and matching, not about spatial proportion.
Lists are also generally easier to scan for absolute values — if you need to read exact sizes rather than relative ones, text is more precise than eyeballing rectangle area, especially once rectangles get small.
The workflow difference: mouse versus keyboard
Treemaps are inherently a pointing-device interaction: you look at the whole picture, then click into the region that catches your eye. This maps naturally to a mouse or trackpad and less naturally to a keyboard, since there's no obvious linear order to arrow-key through irregularly sized rectangles.
Lists map naturally to both. A mouse can click a column header to sort or a row to select, but a list also supports keyboard navigation cleanly — arrow keys to move between rows, a letter key to jump to a name, Enter to open a selection — because rows have an inherent linear order that a treemap's rectangles don't.
This matters beyond a general keyboard-shortcuts preference. Anyone who relies on keyboard navigation because a trackpad or mouse is difficult or unavailable to them will find a list view meaningfully more usable than a map for the same underlying task, independent of which view is conceptually faster for a sighted mouse user.
Accessibility considerations specifically
Beyond keyboard navigation, screen reader compatibility is a real differentiator between the two view types. A list view built with standard table or list UI elements can expose row content — name, size, path — to a screen reader in a straightforward, linear way, because that's exactly what those UI elements are designed to communicate.
A treemap is fundamentally a custom visual layout: rectangles positioned and sized according to a layout algorithm, coloured to distinguish categories. Making that genuinely accessible to a screen reader user requires deliberate additional work — exposing each rectangle's underlying data (name, size, path) through accessibility APIs in a sensible reading order, not just rendering pixels. A tool that only offers a treemap, with no equivalent list-based way to reach the same information, has a real accessibility gap for anyone using assistive technology, regardless of how good the visual design is for sighted mouse users.
This is one of the stronger arguments for a tool offering both views of the same scan rather than committing to just one: it's not just a convenience feature, it's what makes the same underlying data usable across different input methods and assistive technology.
Combining both in a single workflow
The most effective way to use a tool that offers both views isn't to pick one and stick with it, but to move between them as the question you're asking changes within a single session. A typical effective sequence starts with the map: open it, scan the whole disk or home folder, and let your eye find the largest block. Once you've drilled into that region and it's narrowed to a folder with a few dozen similarly-sized items, switching to the list view for that same folder lets you sort by date or name to finish the job — separating, say, recent project files from a genuinely stale one you forgot about, which the map's proportional view alone wouldn't distinguish.
Treating the two views as complementary stages of the same investigation, rather than as competing options to choose between once, gets you to an answer faster than trying to force either view to do the whole job on its own.
Search as a third path
Beyond the map-versus-list choice, a text search field cuts across both — typing a partial file name, extension, or path fragment and getting results regardless of where they sit in the hierarchy. This matters when you already know the specific thing you're looking for by name (a particular video file, a specific project folder) but don't know where it currently lives. Search isn't a replacement for either view; it's a third, independent way into the same underlying scan data, useful precisely when neither browsing by proportion nor sorting by size and date is the fastest path to a known target.
A quick decision guide
| Situation | Better view |
|---|---|
| No idea where the space went | Visual map |
| Know roughly what you're looking for (extension, date, name) | List, sorted or filtered |
| Using a keyboard rather than a pointing device | List |
| Using a screen reader | List (assuming the tool exposes one) |
| Comparing overall proportion across a whole disk at a glance | Visual map |
| Need to read exact sizes precisely | List |
Where VolumeLens fits
VolumeLens offers both a visual map and a sortable list against the same scan, so you can start wherever the question you're asking actually points — a map when you're starting cold, a list when you already have a specific target in mind or when a mouse isn't your primary input method. Cleanup review, in either view, always shows the itemised list before anything moves to Trash. You can try both views for yourself on the features page or download VolumeLens and switch between them on your own disk to see which one answers your particular question faster.