"A file with that name already exists" — and only you can fix it

You type a filename. You press Save. A modal stops everything to tell you that name is taken, and asks whether to replace the existing file.

Your browser has been quietly handling this exact situation since forever. Download something twice and you get report.pdf and report (1).pdf. No prompt. No decision. Nothing lost. You’ve probably never once been annoyed by it, which is the point — a solved problem stays invisible.

One operating system, three different answers

The same conflict — this name is taken — is resolved three separate ways on the same machine:

Nobody chose this. Three teams solved the same problem at different times and the results were never reconciled. But the consequence is that the worst of the three sits in the flow you use most, and the best one is the flow nobody ever thinks about.

Why the modal is the wrong shape

It offers a destructive option and no safe one. Replace overwrites a file — irreversible, and possibly something you’d rather have kept. Cancel throws away the save you were trying to perform. The option a person actually wants — keep both, sort it out later — is the one that isn’t there, even though Finder has that exact button a few menus away.

And it makes you do the work. Declining to overwrite means going back and inventing a name: report-2, report-final, report-new. That’s the machine delegating a naming problem it could solve in one line, and the names people invent under pressure are worse than (1) — they don’t sort, don’t group, and don’t tell you which came first.

The principle

When a safe default exists, take it — don’t hold a meeting about it. A prompt is only justified when the system genuinely can’t infer the better outcome. Here it plainly can: keep both, disambiguate, proceed. The one case that warrants asking — you actually meant to overwrite — is rarer than the case being interrupted, and an undo covers it.

This is case 005’s dialog again, failing differently. That one couldn’t delete a file you were looking at; this one can’t rename a file it’s about to create.

The math

1B people × 8 collisions/yr × 8s = ~30 lifetimes / year

The fix

Save as name (1) and say so quietly. A brief, dismissible note — “Saved as report (1).pdf” — with an inline option to replace instead. Nothing blocks, nothing is lost, and the rare overwrite case is one click away rather than the default.

At minimum: add “Keep Both” to the modal, exactly as Finder already has it. Same OS, same phrase, same behaviour. It has already been designed, written, tested and shipped — just not here.

Difficulty to fix: none

The good behaviour already ships on the same computer, in the flow you use least. Move it to the one you use most.