The 40 Years Old Default No One Cares

The 40-year-old default no one cares

Why “New Folder/Untitled Folder” still wins”

Count the untitled folders or New Folders on your computer. In most setups they outnumber the ones you actually use. I am looking at 4 of them on my desktop right now and cannot say which is which. They have been sitting there long enough to feel like unclaimed children.

40 years ago, the command line never had this problem. Point mkdir at no name and it returns an error on the spot, clean and decisive. The GUI made this problem for itself: the Mac Finder and Windows 1.0 turned “create new” into a click you never think about, and a folder shows up. A folder needs a name to exist, so the system mumbles out a placeholder and puts it in your hands. Untitled Folder. Empty Folder. New Folder. Forty-odd years on, those words have barely budged, fossils forgotten in some corner of the system.

It is not a taste argument. The answer is clear, and nobody has bothered to spend the effort on it.

The system already knows

There is no convincing to do, because the same system already does timestamps somewhere else. A screenshot on macOS arrives as Screenshot 2026-09-05 at 14.32.07.png, a clean timestamp standing on its own. Windows is the funnier case. Win+PrtScn writes straight to disk as the counter, Screenshot (N).png. Save the same picture from the Snipping Tool and the default name carries a date instead. One company, one operating system, two different defaults, both fine.

So “it can’t be done” can go. If some constraint underneath really forced the counter, the timestamp path would not exist in the same system. What actually happened is that each component picked its own default off the cuff, behind closed doors, and nobody ever sat down to ask whether they should agree. Every corner is just lazy by itself.

The cost of doing nothing is higher

Someone always says a change like this takes work and investment. The status quo is not the cheap one, though. Behind New Folder (5) or untitled folder 5 the system has to remember how many you have made in this directory and what number the next one gets. A name that is unique by itself needs none of that bookkeeping. Switching to a timestamp trades the heavier scheme for the lighter one, which flips the cost argument.

The format itself has no defect. folder 20251126_1 has no slashes and no colons, so it avoids the reserved path characters and none of those system reserved names. It runs a few characters past “New Folder” or “untitled folder” at most, far from long enough to truncate a tab label.

This is a folder problem

Fair enough, the argument does not reach everywhere. Extend it to images and video and it gets shaky. Photos and videos carry their own EXIF, and the creation time is already in there, so the filename does not need to repeat it. The iOS camera has used bare counters like IMG_0001 for years, and nobody has suffered for it.

Folders are different. A folder is entirely bare: no EXIF, no embedded fallback of any kind. Its creation time sits alone in the filesystem attributes, and the moment you zip it, upload it, or send it out over email or a chat app, that piece of information is gone. The recipient unzips the archive and finds a folder called New Folder, as if it had crawled out from between two rocks. The filename is the only metadata that travels with a file, and the folder depends on that channel the most while getting the least out of it.

The scope is a single action: you right-click manually in a GUI and create a new folder. It causes no bugs, touches no other process, and it will never rise on anyone’s to-do list. It just sits there.

The one rebuttal worth taking

People make the case that Untitled is ugly on purpose, a loud reminder that you have not named the thing yet, meant to shame you into changing it. Swap in a timestamp that looks respectable, they continue, and you will just let it slide.

That lands when you actually had the chance to rename and did not. Creating a folder is the opposite case. The instant you make one in Finder or Explorer, the cursor is already sitting in rename mode, and the default name was never meant to stick. The files that genuinely miss a rename are the Untitled, Untitled 2 autosaves an application makes for you. They are silent from the moment they exist, and you may not even know one is waiting there. The friction argument works for those. For new folders, it has boarded the wrong bus.

“untitled folder 5” carries no information

Put the question to it: does untitled folder 5 tell you more than a bare timestamp, or less? The answer stings a bit. The only fact it reports is that the naming has already collided four times running in this directory. A counter of the mechanism’s own failures, with nothing to do with what is inside the folder, purely self-talk. A timestamp at least records one true thing about the world, namely when this was made.

It is not the best option, only a decent fallback. The order that makes sense: derive the name from content when there is content (Google Docs and Notion both default the title to the first line of the body), fall back to context when the provenance is clear (which app made it, which directory it sits in), then reach for a timestamp, with Untitled at the bottom. A folder is created with no content yet, which is exactly the tier where a timestamp is the defensible answer, not the tallest among dwarves.

Why nobody has fixed it in forty years

The fix was never hard. It survived because it is small, pitifully small. No bugs, no crash log entries, no wobble on any conversion curve. No team gets called out over it, and no dashboard goes red. The cost is spread across billions of unremarkable clicks, so any single one is light enough to ignore, and the pile adds up to a default that a few lines of code could have fixed. It has instead lived on for forty years, safe and sound, unattended.

The catch is that any company could fix this in an afternoon, and no company will. It was never one switch at the system layer. The choice is scattered across every corner of the GUI, each governing itself, and because it is scattered, no single change settles it once and for all. Nobody sticks their neck out for a thing that touches one task and will never make a priority list.

Forty years ago this was a placeholder somebody picked in a hurry. Forty years later it is still that placeholder, for the same old reason: nobody takes it seriously.

The 40 Years Old Default No One Cares was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.