What does a file timestamp show?
A file timestamp creates evidence that the standard SHA-256 of an exact set of file bytes was recorded by a particular time. If the file changes later, its SHA-256 changes and it will no longer match the recorded value.
How HashMyWords creates a file proof
File stays local; SHA-256 is public
The original file and filename are not uploaded to HashMyWords. Your browser calculates the standard SHA-256 locally, then HashMyWords submits that exact digest as public proof data on Hedera HCS.
A SHA-256 can itself be sensitive when underlying material is predictable or already known. Create an H2 file proof only when you are comfortable with the file hash being public and persistent.
What should you keep?
Keep the exact original file. Also keep the HashMyWords receipt or certificate and the secret code. The receipt records useful local metadata and the verification link; the shareable certificate deliberately excludes the secret code.
If the file matters as evidence, preserve surrounding context too: source records, drafts, correspondence, version history or other material that helps explain where it came from and who controlled it.
How do you verify the file later?
Open the verification link saved with the proof. HashMyWords checks the HCS message and recorded SHA-256 against Hedera's public Mirror Node. You can then choose a local file and HashMyWords hashes it again in your browser.
If the locally calculated SHA-256 exactly matches the one recorded in the referenced H2 HCS message, the selected file is an exact byte-for-byte match for the file represented by that proof. Historical H1 proofs remain verifiable using their original format.
Frequently asked questions
Does HashMyWords upload my file?
No. The file itself stays in your browser. For new H2 proofs, HashMyWords receives and publicly records the standard SHA-256 plus the proof data needed for timestamping.
What file types can I timestamp?
The File Proof tool is designed for general digital files such as documents, images, video, archives and other file types.
What happens if I edit the file later?
Even a small byte-level change normally produces a different SHA-256, so the changed file will not match the earlier recorded digest.
Do I need the secret code to prove an exact file match?
The public file-proof verification link checks the Hedera evidence and lets you compare a local file. The secret code is separate proof material that confirms control of the HashMyWords record and should still be kept private.