Document Integrity
Document Integrity is a local checksum tool. Use it before you send a contract, after a download, or when you want to prove two copies are byte-for-byte the same. Hashes never leave this tab.
Privacy and offline checks
Document processing runs locally in supported PDFForge workflows. This panel is a diagnostic view; it cannot prove that no data left the device.
Observed resource activity
0 observations in this page session · 0 need inspection
Resource timing is unavailable in this browser. Use the independent checks below.
Page timing and the active service worker report different surfaces and may observe the same request. Worker activity can be incomplete; WebSockets, request bodies and extensions are outside this view. The latest 60 sanitized observations stay in memory only. URLs, filenames, query strings, document content and byte counts are not recorded here.
Verify independently in DevTools
- Use a clean browser profile and synthetic documents. Open Network in DevTools and enable Preserve log.
- Prepare offline below. Switch Network to Offline, then reload the saved workspace and select a new file.
- Inspect, redact, run output checks and download. Inspect failed requests and request payloads, including worker requests. A same-site request can still transmit data.
- Inspect Application or Storage. Cache Storage should contain public app assets and setup records only. Document recovery and content telemetry are disabled; recipe settings are saved only after opt-in.
Offline readiness
Full workspace not prepared for offline use
English OCR not prepared for offline use
Prepare while connected to save the workspace, tools, fonts and workers. English OCR is optional. Only public app assets are saved; documents, outputs and passwords are excluded. Browser storage can be cleared or evicted. Check saved assets before disconnecting and prepare again after an app update.
Checking saved app assets…
Open saved workspaceReady for local work · One heavy job at a time in this tab
Fingerprint · Compare · Tamper detection · Verify — 100% local
All hashing runs locally in your browser. No files are uploaded. No data is sent to any server.
Private by design. Document processing runs in this browser. PDFForge has no document upload API.
How it works
How Document Integrity works
Document Integrity is a local checksum tool. Use it before you send a contract, after a download, or when you want to prove two copies are byte-for-byte the same. Hashes never leave this tab.
Guided steps
How to use Document Integrity
- 1Choose Fingerprint, Compare, or Verify Hash.
- 2Drop a file (or two files to compare). Any type is allowed.
- 3Read the SHA-256 or SHA-512 hex digest computed in this browser.
- 4Copy the hash or paste an expected value to confirm a match.
In this tab
What stays in this browser
The file stays in this tab.
- What this tool reads
- The file bytes, hashed as SHA-256 or SHA-512.
- What the download contains
- A fingerprint on this page. The file on disk is unchanged.
Questions
Document Integrity FAQs
Does hashing upload my file?
No. Web Crypto runs in this tab. There is no hash API and no server-side store.
What does Compare tell me?
If two hashes match, every byte is the same. If they differ, the files are not identical. That is tamper detection, not a legal signature.
Which hash should I paste to Verify?
A 64-character hex string is treated as SHA-256. A 128-character hex string is treated as SHA-512. Spaces and 0x prefixes are ignored.
Continue locally
Related tools
Stay in the browser with these nearby PDFForge tools.