Where Your Files Really Are

"It's in my documents" no longer means one thing. A file can be on the drive, synced to a service, held only in the cloud, inside an application, or on a phone that syncs elsewhere. People lose track of which, and the distinction decides what happens when something goes wrong.

The four places a file can be

Genuinely local

On the drive inside the machine. Present without a connection, gone if the drive fails, and included in a local backup.

Synced

On the drive and on a service, kept identical. Available offline, and changes propagate.

Including deletions, which is the part people do not expect. See cloud storage and backup.

Cloud-only

On the service, with a placeholder locally that looks like a file until you open it.

This is now the default in several sync services, under names like files on-demand or optimised storage. It saves disk space and it means those files are unavailable without a connection.

It also means a local backup captures the placeholder, not the file. Which is how people discover their backup contains nothing.

Inside an application

Notes, messages, photographs in an app's own library, email in a client. Not files in a folder you can browse, and frequently not included in a backup that copies folders.

This is the most commonly missed category.

How to find out which

Look at the folder icons. Sync services mark files with status indicators — a solid tick for local, a cloud outline for cloud-only.

Check the properties. Size on disk against size tells you whether the content is actually there.

Disconnect from the network and try to open it. The definitive test, and it takes ten seconds.

Check what your backup actually contains. Restore something and look. See below.

Why it matters

When the drive fails, you lose the local and synced-local copies. Cloud-only survives.

When you delete something, sync propagates it everywhere within seconds. Version history may save you, for a limited period.

When you cancel a subscription, cloud-only files may become unavailable. Read what the service does when you stop paying.

When you are offline, cloud-only files are not there. This catches people on flights and in areas with poor coverage.

When you back up, cloud-only files may not be captured. This is the failure that costs people everything, because the backup appears to have run successfully.

When you sell or give away a machine, local files remain on the drive until it is wiped properly.

The common confusions

"It's in the cloud so it's backed up." Sync is not backup. A deletion propagates.

"It's on my computer." It may be a placeholder.

"My photos are on my phone." They may be cloud-only, with the phone holding compressed previews.

"I saved it to Documents." Which Documents — the local folder, or the synced one that redirects there? Both major systems can redirect standard folders into a sync service, frequently without the user noticing.

"It's in my email." In a client that downloads it, or on the server and shown to you? Deleting from one may or may not delete from the other.

Getting control of it

Find out which folders are synced. In the sync service settings, and in the system's folder redirection settings.

Decide which files must be available offline and mark them to be kept locally. Most services allow this per folder.

Keep a genuine local copy of the irreplaceable ones, and back that up.

Check what your backup actually captures. Run it, then restore a file from a cloud-only folder and confirm it is the real thing.

Include application data. Photographs in a phone library, notes, messages — export them periodically, or use a backup that understands them.

Know where your phone's photographs are. Whether the original resolution exists anywhere other than the service, and what happens when storage runs out.

A practical arrangement

Working files in a synced folder, kept available offline. Convenient across devices, protected from a drive failure, and with version history against mistakes.

Irreplaceable files — photographs, documents, records — in a genuine local copy, backed up to an external drive that is not always connected, and to a service.

Application data exported periodically.

Test annually. Restore something and confirm it opens.

The question worth asking about every important file

If this machine disappeared today, where else does this exist?

If the answer is "in the cloud", ask what happens if you delete it by mistake, and how long version history keeps it.

If the answer is "nowhere else", that is the finding.

The short version

Four places: local, synced, cloud-only, and inside an application — and people lose track of which.

Cloud-only files may not be captured by your backup, which is how a backup that runs successfully contains nothing.

Disconnect from the network and try to open it. Ten seconds, and it settles the question.

Application data — photographs, notes, messages — is the most commonly missed category.

And ask of every important file: if this machine disappeared today, where else does it exist?

For broader technical standards and computing references, see NIST Information Technology Laboratory.