---
title: "Discussion on \"Making PDFs tamper-evident in the browser with SHA-256 (and why we hash the sealed file, not the original)\" | Hashnode"
description: "Discussion on \"Making PDFs tamper-evident in the browser with SHA-256 (and why we hash the sealed file, not the original)\". Originally published on DEV.\nAI has made it trivial to edit an invoice, a quote or a contract so cleanly that nobody can spot the change by eye. A PDF has no memory: the file name, the date and the la"
url: "https://hashnode.com/posts/making-pdfs-tamper-evident-in-the-browser-with-sha-256-and-why-we-hash-the-sealed-file-not-the-original/6af79a14c4232eb42eab3dd4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Making PDFs tamper-evident in the browser with SHA-256 (and why we hash the sealed file, not the original)](https://trampto.hashnode.dev/making-pdfs-tamper-evident-in-the-browser-with-sha-256-and-why-we-hash-the-sealed-file-not-the-original?utm_source=hashnode&utm_medium=feed)

Originally published on DEV. AI has made it trivial to edit an invoice, a quote or a contract so cleanly that nobody can spot the change by eye. A PDF has no memory: the file name, the date and the la

Nov 13 · 4 min read · trampto.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#security](https://hashnode.com/tag/security)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#pdf](https://hashnode.com/tag/pdf)

## Written by

[TRAMPTO](https://hashnode.com/@trampto)

@trampto

  
[View profile](https://hashnode.com/@trampto)

TRAMPTO seals PDF documents with a SHA-256 fingerprint and gives you a public link anyone can use to verify they haven't changed. Sealing runs in the browser. https://trampto.com

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
