Habits from the machine you work on · habit 35 of 40

Wherever it saves by default

This is the habit with the widest gap between what people believe happened and what happened. The belief is that a file went onto a disk. Quite often it went onto a disk and then somewhere else.

What it does everywhere else

Defaults like this are one of the better ideas in personal computing. Everything lands in one predictable place, which makes it findable later, backed up without effort and available on the phone in a waiting room. Not having to choose a folder every time is a small mercy repeated thousands of times.

What it does on this one

On this one, the predictable place is often not local. Documents and Desktop are redirected into cloud storage on a lot of modern setups, sometimes by an administrator and sometimes by a checkbox agreed to at first sign in. The file uploads within seconds of appearing, under whichever account owns that storage.

The habit

You press save, accept the folder the dialog offers, and think of the file as being on your computer.

Why it is automatic

The dialog is not really asking a question. It opens on the last place it was used, the name is already filled in, and the button is already focused, so the whole interaction is one press of Enter. Nobody experiences that as choosing a storage location, because in practice it is not one.

The folder names reinforce the belief. Documents and Desktop are the two most local sounding words in the system. They were local for twenty years and the icons have barely changed, so the language has not caught up with an arrangement where those names point at a service.

The arrangement is also popular for excellent reasons. Files survive a dead laptop. They appear on a second device without being emailed anywhere. People who have lost work once never want to think about it again, and this is what stops them having to.

What it actually does here

Folder redirection is invisible by design. The path shown in the title bar and in the save dialog still says Documents, and underneath it points into a synced folder. The upload starts as soon as the file is written, without a prompt, because a prompt would defeat the purpose of the feature.

A synced file becomes several copies rather than one. There is the local one, the one on the server, the previous versions kept as history, and a copy on every other device signed into the same account. Deleting the local file queues a deletion that propagates, usually leaving the item in an online recycle bin and leaving version history alone.

Where the account is a work account, the storage belongs to the organisation. That is the ordinary basis on which company storage is provided, and it means an administrator can reach the contents through normal tooling. The device side of the same arrangement is on a device somebody else administers.

Downloads are caught by the same mechanism more often than people expect. A browser saves to the downloads folder, and where the home folders have been redirected that folder can sit inside the synced tree as well. Nothing about the browser changed. The floor underneath it did.

The path in the title bar is not the whole address

The habit worth building is reading the full path rather than the folder name. A save dialog will show it if asked, and file properties will show it afterwards. What you are looking for is whether the path passes through a folder named after a storage provider, or whether the file carries a small cloud or tick marker beside it.

Those markers are a status display: available on this device, available when online, always keep on this device. They are the interface saying honestly that the file is not simply sitting on a disk.

Deleting is also a sync event

Dragging a file to the bin feels final because it used to be. In a synced folder it is an instruction sent to a service, and the service acts on it as configured, which normally means moving the item to an online recycle bin for a set retention period.

Version history is separate again and often survives deletion of the current file. That is a feature people are grateful for on the day they need it. It also means a file that existed for two minutes in a synced folder has more of an afterlife than the same file on a plain disk.

What to do instead

The fix is not to abandon cloud storage. It is to stop treating the save dialog as a formality and to know which folders are actually local.

Find out once whether Documents, Desktop and Downloads are redirected on your machine. The sync client settings pane states it plainly.
Set the browser download folder explicitly to a folder you created yourself, outside any synced tree, and remember its name.
Read the full path in the save dialog rather than the folder name at the top of it.
Prefer not saving anything. Read the page, write the one line you need by hand, and close it. That leaves nothing to relocate later.
If something was saved into a synced folder, remember that removing it means the local copy, the online recycle bin and the version history.
Keep this separate from anything with money attached, which is dealt with on paying.

How to notice you did it anyway

This is one of the few habits where a single screen gives an honest and complete answer within seconds.

The sync client recent activity list, which shows what it uploaded and when, in plain language.
The web view of the storage account, and specifically its recent files section.
The phone. A file appearing there that you never sent to it is the clearest possible signal.
The online recycle bin, which holds deleted items for a retention period set by somebody else.
File properties, which show the full path rather than the friendly folder name.

What readers ask about this habit

How do I tell if my Documents folder is synced

The sync client settings pane lists which folders it manages, and file listings usually show a cloud or tick marker beside each item. The full path in file properties will pass through a folder named after the provider.

I deleted the file straight away, is that enough

It removes the local copy and queues the deletion. On most services the item then sits in an online recycle bin for a retention period, and version history is separate again.

Does turning off sync afterwards undo it

No. It stops future uploads and leaves everything already uploaded where it is. Turning sync off is worth doing before a session rather than after one, and habits lists the other settings worth looking at in advance.