Monday morning, another “final” file arrived
Last Wednesday afternoon, I put a client’s logo into our shared drive in Hangzhou, resized it, and overwrote the original. The next day, their designer replied: “Why did the color change?” I stared at two files with the same name for ages. Only then did I realize our team’s problem was rarely a lack of powerful tools. We simply hadn’t confirmed whether files had changed. I also treated “Save” as a safety net, never considering that overwriting, renaming, or transferring a file could alter it.
No new software needed—just give every file a “fingerprint”
This method is called file integrity verification: a tool reads a file’s contents and generates a short code. Run the check again later, and if the code matches, the contents are unchanged. If it doesn’t, the tool flags a possible modification. It isn’t encryption or hacker protection; the point is to catch accidental changes. Chen Yuqing, an independent illustrator in Shenzhen, attaches a file fingerprint to her quote when delivering illustrations for the local zine Weekend Walks, then verifies it again after the work is finished. She told me this saved her from repeatedly saying, “I didn’t change it,” while also showing clients which version should be treated as authoritative. There’s no urgency to try it today—two unimportant files are enough to start.
Try it today: $0, about 20 minutes, almost no technical barrier
Cost: basic verification tools can be free. Time: roughly 20 minutes for your first setup. Technical barrier: knowing how to copy and paste a command and where your files are stored. First step: copy a test image into a separate folder, open your computer’s Terminal, enter the built-in checksum command, and copy the output code. If Terminal feels intimidating, use an existing graphical tool and start with one image. The code is like a file’s ID card; understanding the underlying principle isn’t necessary. Before every delivery from now on, recalculate the checksum and compare it with the previous code. If it differs, find a backup. And remember: don’t keep an important file in only one place. Preserve the original first.
Build around my current workflow—there’s no need to do everything at once
When I’m just starting out and files live mainly on my own computer, I’d check only quotes, contracts, and delivery assets, running the verification once at the end of each day without setting up another system. With one or two long-term clients, I’d keep a separate “delivery checklist” for each client, preserving the original, approved version, and fingerprint so there are no arguments about which version was agreed on. If I’m scaling and the team has more than two people, I’d add the verification steps to shared-drive naming conventions and handover checklists, spot-check weekly, then consider automated alerts. Not everyone needs a tool; for a solo business with only a few files, manually keeping two backups may be simpler. Am I more worried about files being altered, or too many versions to track?