Adult learning / 30-minute practical workshop
Same file.
Different name?
Learn what a checksum can tell you, what invisible text changes look like, and why finding a duplicate is only the start of a decision.
Eight tiny fictional text files plus printable HTML materials. No signup, personal files, coding or installation required. Extract the ZIP before selecting files. The ZIP is not an app installer.
What you will learn
- Separate a filename from the bytes stored inside it.
- Compare a full SHA-256 checksum and explain a mismatch.
- Spot the effect of line endings and a final newline.
- Review exact duplicates without deleting anything.
- Explain why a matching checksum is not proof of origin or safety.
Prepare the room
Use an up-to-date desktop or laptop browser, a network connection to open the two tools, and permission to download and select the supplied files. A facilitator can demonstrate if downloads are restricted. Do not change security settings to run this workshop.
Print the worksheet using your browser’s Print menu if useful. Keep the instructor answers separate until discussion. Use only the supplied fictional files; personal documents are unnecessary.
The tools process selected file contents in the browser. TwinTrail is read-only: it never deletes or modifies files. Leave optional measurement off. Do not infer “safe to delete” from matching bytes; copies may serve different backup or record-keeping purposes.
The 30-minute session
- 0–5 min · Predict. Read the worksheet and guess which files contain identical bytes.
- 5–13 min · Inspect. Open DigestBench. Hash individual files and compare full checksums.
- 13–22 min · Review. Open TwinTrail. Select the eight fixtures once, keep byte confirmation enabled and inspect the groups.
- 22–27 min · Challenge. A changed file and a changed checksum can agree. Discuss what is still unknown.
- 27–30 min · Explain. Answer the five exit questions and compare reasoning with the instructor key.
Useful beyond this exercise
A checksum can help compare a download against a trusted reference or notice changes since a recorded baseline. Preserve the reference and its context. It does not tell you which change occurred, who made the file or whether its content is safe. These tools do not replace backup management, malware checking or signature verification.
Two focused tools are enough for this lesson. For other tasks, explore the 30-tool First Fold collection.
References and verification
- NIST: Hash functions explains fixed-length digests and collision resistance.
- Digital Preservation Coalition: Fixity and checksums explains checking whether stored content has changed.
- NIST: Digital signatures distinguishes authenticity-related signature functions.
Sources checked October 12, 2026. The supplied reference hashes describe these exact fixtures. SHA-256 collisions are theoretically possible; the duplicate exercise uses byte confirmation as well.