Tool Supply is a place where I will be storing tools (and tips) for myself, and for anybody who stumbles upon this sub-website. I hope it will grow into a tool supply for everybody in the future.
md5
Shasum -a 256
Sometimes you need to double click or click anywhere on the background to make the QuickCopy funtion work
First of all, this is not a deep dive into checksums as a thing, but rather about their usage for digital media-based art and design – specifically in the context of institutional acquisitions and archives. There are two (and probably more) great ways of using checksums that I’ve discovered so far. The first case is for archiving, and the second is for duplicates.
A checksum is a way of generating a unique number for an individual file. This unique number helps anyone validate a file. The checksum can help determine if the file you have is indeed the file it’s supposed to be, or if something is wrong when the numbers don’t match. Did something happen during the internet-transfer-sea-road? Or has bit rot started to occur on your 20-year-old hard drive? When sending any file, either for archiving or playback, the receiver can check the checksum to ensure it matches the original checksum, confirming that the file is correct and ready for playback (so other playback issues can occur... BrightSign, am I right!). In other words, a checksum is a useful way to know if the file is indeed an “original” – ensuring they are one-to-one. For example:
Master: | ff88c59b30b9c602f678e63236145412 |
Receiver: | ff88c59b30b9c602f678e63236145412 |
Everything is in order (#^.^#)
Master: | ff88c59b30b9c602f678e63236145412 |
Receiver: | c24429b7ccb7d9446511ed202a98d5d2 |
Something happened along the way (ー_ー)
For this ToolSupply “sticky note” #1, we are looking at video files as an example. The final file is finished – like in _final_final_final.mov – and you are preparing it for storage or acquisition. By the way, this is Mac-only (working on the Windows version). Open up Terminal and copy one of the checksums above. Either use md5 it’s the fastest and generates a “shorter” number, though it’s considered less secure compared to SHA-2 – (but that's for another topic). Some institutions/collectors prefer one over the other.
Terminal → | md5 / shasum -a 256 |
[Master] Name: Artist: md5 checksum: SHA-256 algorithm: Container format: Resolution: Data size: Over all bit rate: Video format: Audio Format: Encoded FPS: Duration: Loop: Color Primaries: Construction: Text file updated:
[Exhibition copy] Name: Artist: md5 checksum: Container format: Resolution: Data size: Over all bit rate: Video format: Audio Format: Encoded FPS: Color Primaries: Exhibition Copy Notes:
The second use case is something I started doing for myself. Sometimes I find myself questioning whether the
two files I have in front of me are the same file. They might have the same name, and look the same when I
inspect them, but I’m not sure if I can delete one of them. Checksums are great for solving that. Run
Terminal, and if you get the same sum, they are identical, so you can do whatever you want with the extra
copy. This has saved me time when reviewing video files, instead of having to watch a full feature film to
check if it's the same or different. Checksums also work on other files than video, so give it a go.
However, it doesn’t work on folders, since they’re not a single file.
I plan to write more about encoders (444 / 422 / h264 / h265 / etc.), the differences between file compressors, and why it might be good to try more than one. Personally, I can go through at least four when preparing exhibition files, to get the best outcome (depending on the content) and a reasonable size for playback.
Thanks for reading
ᯓ✦ (=^・^=)
© Claes Storm, 2025