Why macOS Lets You Use '/' in File Names (And What It Means)

On Windows and Linux a slash / cannot appear in a file name, but on macOS Finder you can rename a file to a/b.png or create a folder c/d without error.

When the same directory is listed in Terminal, the slash is displayed as a colon: a:b.png c:d. Creating a file with touch e/f.txt fails ( touch: e/f.txt: No such file or directory), while touch e:f.txt succeeds, and Finder shows the file as e/f.txt again, swapping the colon back to a slash.

The reason lies in the history of Apple’s file systems. In 1985 Apple introduced HFS (Hierarchical File System) and chose the colon : as the path separator because the slash / was already common in user‑visible names (e.g., To_Be/Not_To_Be). In Unix, however, the slash has been the standard separator since the 1970s, and the colon is an ordinary character.

When Steve Jobs returned to Apple after founding NeXT, the NeXTSTEP operating system (built on BSD Unix) used the slash as its separator. After Apple’s 1996 acquisition of NeXT, the two conflicting conventions had to coexist. Engineers added a translation layer that swaps / and : when files cross the UI‑kernel boundary. This makes a file appear as a/b in Finder but as a:b in the shell, a phenomenon Apple engineers called “user‑visible schizophrenia” in a 2000 USENIX paper titled *The Challenges of Integrating the Unix and Mac OS Environments*.

Even after Apple replaced HFS with APFS in 2017—adding modern features like snapshots, encryption, and space sharing—the translation layer remained unchanged, so the dual identity persists in every Mac today.