Knowledge
Digital fingerprint & byte-exact original
"Byte-exact original", "checksum", "fingerprint" — these terms appear on several of our pages. Here they are in plain words, with no technical background needed: what they mean and why they make the difference in quality management.
In one sentence
A digital fingerprint is a short code computed from a file's content. The same file always yields the same code — change even a single character and the code looks completely different. That's why it can prove a document is exactly the original.
Like a fingerprint for files
The comparison fits well: just as a fingerprint uniquely identifies a person, this code identifies a file. Two identical files share the same fingerprint; two files that differ by a single comma have completely different ones. And it's a one-way street: the file produces the fingerprint, but the fingerprint can't be turned back into the file. It reveals nothing about the content — it only shows whether something changed. The technical name for this code is a checksum or hash; easo uses the established SHA-256 method.
What "byte-exact" means
A byte is the smallest unit of information in a file. "Byte-exact" means not a single one was altered — the document is the original bit for bit, not a re-saved copy that merely looks the same. When you adopt an existing document into easo, the original is pinned byte-exact and even named by its own fingerprint — so the storage itself is already proof that nothing was touched.
Why it matters in a QMS
A quality management system lives on being able to trust released documents. The fingerprint makes that provable rather than asserted: easo recomputes it at every verification. If it no longer matches — an edited word, a swapped image — easo detects it at once and refuses to export the document as unchanged evidence. A release's signature is placed over exactly this fingerprint (fingerprint = "unchanged", signature = "released by whom"), and the Git history of your QMS is itself an unbroken chain of such fingerprints. That's how revision-safe records arise — without anyone keeping a log by hand.
In short
A digital fingerprint is the difference between "this looks like the original" and "this is provably the same document, not a byte changed". That's exactly what easo builds its evidence on. How easo proves compliance →
Common questions about the digital fingerprint
What is a digital fingerprint?
A short code computed from a file's content — also called a checksum or hash. The same file always yields the same code; change even a single character and the code is completely different. That's how you can prove a file is unchanged.
What does "byte-exact" mean?
A byte is the smallest unit of information in a file. "Byte-exact" means not a single one was altered — the document is the original bit for bit, not a re-saved copy that merely looks the same.
Can the file be reconstructed from the fingerprint?
No. A fingerprint is a one-way street: the file produces the code, but the code cannot rebuild the file. It reveals nothing about the content — it only proves whether it has changed.
How does easo notice when a document was changed?
easo recomputes the fingerprint at verification and compares it. If it doesn't match — an edited word, a swapped image — easo flags the document as changed and refuses to export it as unchanged evidence.
What method does easo use?
SHA-256, an established, globally used standard. easo even names attachments by their own fingerprint, so the reference itself is already the proof.
Is a fingerprint the same as a signature?
No, they complement each other. The fingerprint proves the content hasn't changed; the signature proves who released it. In easo the signature is placed over the fingerprint — the two together make a verifiable proof.
Stay in the loop
easo is available for macOS — the Windows version is coming soon. Leave us a note and we'll reach out the moment it lands.