Files you chose to download

Some things you save on purpose: a public key, a picture from a listing, a document, a receipt. Saving is the moment a page stops being a view and becomes a thing.

This card is the counterpart to what lands on the disk. That one was about retention nobody asked for. This one is about the files you meant to create, which are usually a much larger and much more legible record than the accidental scraps, precisely because you selected them for being useful.

They tend to be the same handful of categories. Key material, because you need it again. Images from listings, because the picture matters. Documents, because they were worth keeping. Receipts and confirmations, because a record of a transaction feels prudent. Every one of those answers a question about you.

What a saved file discloses

Its own attributes

The file system records a name, a size, a type, a creation time, a modification time and often a last access time. Those are properties of the file rather than of its contents. The name deserves a mention: a file called something obvious answers a question before anybody opens it, and default names from a website are often descriptive.

Many systems also attach a marker to files that arrived from the internet, originally so the system could warn you before running something downloaded. That marker says this came from outside, and on some systems it records where from.

Authoring information inside the format

Some file formats carry a block of their own information, quite separate from what the file system knows. Office documents commonly record an author name, an organisation, a creation date, a last modified date, a total editing time and sometimes a revision list. Portable document files record the producing application and dates. Images from a camera record the metadata described on screenshots and photos.

The important part is that this information is inside the file. Renaming the file does not change it. Copying it to a different machine does not change it. Attaching it to a message carries it along, because it is part of what is being sent.

The download as an event

The browser knows it downloaded something and, in a browser designed not to persist, that knowledge does not outlive the session. The system underneath may note it independently: a completed download can appear in a recent items list, be picked up by a search index, trigger a security scanner to inspect the new file, or be captured by a sync client watching that folder. The last one is backups and sync, and it is the one that moves the file off the machine. The scanner case belongs to the rest of the software.

What a saved file does not disclose

A downloaded file does not carry the page it came from, unless the format or an attribute happens to record a source. There is no general mechanism by which a picture knows which listing it was on, and no way to read a browsing session out of a folder of images.

It does not carry your identity. A file has an owner in the file system sense, which is the account on that machine, and that is a local username rather than a person. Nothing in an ordinary download links it to you personally except the fact that it is on your machine, which is a fact about the machine.

It also does not update itself. A saved page is a photograph of a moment. If the thing it was copied from changes afterwards, the file does not know. That is exactly why people save things, and it is also why a downloaded copy is an assertion about the past rather than about now.

The file that is not there

The honest reverse of this whole card: a file you never saved is a file that is not there. There is no shadow copy of a download you did not perform, no cache entry for an image you looked at and closed, no record in a backup of a document you read in a window and never wrote out.

This matters because it is the one place in the section where the reader has complete control before the fact and none afterwards. Every other observer in this catalogue acts on you. This one waits for a decision. Not saving something is not a trick and not evasion, and it produces no artefact to reason about at all.

The obvious cost is that you lose the record. That cost is real. A record you might genuinely need for opening a dispute is worth having, and this card is not an argument for keeping nothing. It is an argument for the file existing because you wanted it to, rather than because a button was there.

What changes the answer

4 things change how much this action gives away. None of them takes it to zero, and none of them is a promise.

1. Choose the destination deliberatelyA browser will suggest a default folder, and the default may be inside a synced or backed up location. Picking the destination for anything that matters turns an automatic outcome into a chosen one. It does nothing about where copies already went.
2. Rename on the way inDefault filenames from a website are frequently descriptive, and a folder listing is read by anyone who opens the folder. Renaming changes what the listing says. It does not touch anything recorded inside the file.
3. Know that formats carry their own recordDocuments and images can hold an author, an organisation and dates independently of the file system. Knowing which formats do this is the difference between sending a file and sending a file plus a history. Most tools will show you the properties if you ask.
4. Ask whether the file is needed at allThe strongest option on this page is not creating the object. It is available only before the download and never after, and it has an obvious cost when the record turns out to be the thing that settles an argument.

What this card is not

This card is about what a saved file carries and where it goes. It is not guidance on destroying files, and it does not suggest that keeping records is unwise.