Master Copy Versus Working Copy

Most households do not lose files in a single dramatic moment. They edit the only copy until the original is gone, and they call the result an improvement. A master copy and a working copy are two jobs, not two brands of folder. The master remembers what you actually captured or received. The working copy is allowed to be cropped, colored, shortened, and revised. When those jobs share one file, every improvement is also a small deletion.

The master is the file you would be sorry to overwrite

A master is the scan before anyone adjusted the contrast, the photo as it came off the camera, the exported mail before someone trimmed the thread, or the audio before the levels were changed for one listening session. It does not have to be beautiful. It has to be intact and left alone. Put it in a folder whose name says original or master, and do not open it in a program that saves changes back to the same file without asking. If you are unsure a program edits in place, assume that it might, and make the working copy first.

The working copy is where taste is allowed

Cropping a photo, cutting a home video, or rewriting a club poster all belong on a copy. Name that copy so nobody confuses it with the master. A date or the word edit in the name is enough if you use it consistently. Working copies can multiply, and that is fine, as long as they do not wander back into the master folder with similar names. The failure mode of a single desktop pile, described in why one archive folder fails, often starts here: an export and an original share a directory and a tired person lets one replace the other.

Decide when the master is allowed to change

Sometimes the master should be replaced, and you should do it on purpose. You rescan a page because the first scan cut off a signature. You receive a better transfer of a tape. In that case, keep the older master in a side folder or give it a name that says it was superseded, until you are sure the new one is complete. Do not let a routine export from editing software become the new master by accident. Appraisal still applies. Choosing what to keep is about significance. The master and working split is about not destroying a significant file while you are improving a view of it.

Small teams need the split written down

In a household or a club, people help, and helpers do not share your private rules. A line in a README that says the masters folder is not for edits will be read more often than a policy nobody stored. If someone must correct a factual error in a document, ask them to save a new file beside the master and to note the reason. Silent replacement feels efficient and leaves no trail. The next volunteer then cannot tell whether the file changed because of an error, an update, or a program that rewrote it on open.

Preservation starts by leaving one file boring

You can keep formats durable, names clear, and spare drives labeled, and still fail if every evening of editing lands on the only copy. Make the boring copy first. Then enjoy the working file. When a project reaches a version you might want again, snapshot that version without disturbing the master. The master stays the earliest faithful file. The snapshots remember what you published or printed. The working folder can stay messy, because mess is allowed there and almost nowhere else in the archive.

Frequently asked questions

Is the master always the largest file? No. A compressed export can be large and still be a working copy. The master is the file you treat as the source, which is a decision you record by where you put it and whether you edit it.

What if I already edited the only copy? Stop editing it further. That file is now the best surviving source. Copy it to a master folder, note that the true original is gone, and do all new edits on a fresh working copy.

Do working copies need a backup too? Keep a second copy of anything you would hate to redo, including a finished edit. The master is not a backup of the working file, and the working file is not a backup of the master.