This is the story of the hidden folder—from its origins in Unix philosophy to its role in modern malware, and why, after decades, we’re still arguing about whether that checkbox should be on by default. To understand hidden folders, you have to go back to 1971. Ken Thompson and Dennis Ritchie, working on the first version of Unix at Bell Labs, needed a way to hide certain files from the default ls command. The solution was elegant and almost accidental: any file or directory whose name began with a period ( . ) would simply not appear unless you explicitly asked for it with ls -a .

Security experts are split. Some argue that hidden folders create a false sense of safety. Malware can trivially check if the user has “show hidden” enabled and adapt. Ransomware doesn’t care if a folder is hidden; it will encrypt anything it can write to. Hiding files stops only the most casual of meddlers—the same users who shouldn’t be digging around in the first place.

On a smaller scale, countless users have lost hours of work because they forgot that .git or .svn was hidden. “Where did my version control go?” They toggle the checkbox, and the folder reappears like a magician’s rabbit. The relief is palpable. Will hidden folders survive another decade? Possibly, but they’re under pressure. Modern operating systems are moving toward sandboxed apps and per-user containers (Flatpak, Windows AppX, macOS bundles) where configuration is stored in standardized, non-hidden databases or plists. The need for dot-file hacks is diminishing.

Why the dot? The lore suggests it was a quick hack. Thompson and Ritchie wanted to hide the . and .. directory entries (current and parent directory) from listings to reduce clutter. Someone—accounts vary—realized that if the code skipped anything starting with a dot, they could create hidden files like .profile for user configuration. No special attribute flags. No complex permissions. Just a naming convention.

Apple has already made the ~/Library folder hidden by default in macOS (since Lion in 2011). But they also added that Cmd+Shift+. shortcut—an acknowledgment that power users still need access. Microsoft continues to treat hidden files as a second-class citizen, often excluding them from search results unless forced.

The dot-file wasn't designed for security. It was designed for tidiness. But that distinction—hiding vs. protecting—would become crucial. Microsoft’s approach has always been more… bureaucratic. In MS-DOS and early Windows, files had attributes: Read-only, Archive, System, and Hidden. The attrib +h command would make a file disappear from DIR listings and File Manager. No dot required. The hidden attribute was a binary flag stored in the file system’s metadata.