Follow the file.
See what changed.
Choose two versions. See what happened to your file, wherever it was edited.
Your files stay on this device. Nothing is uploaded: the comparison runs in your browser. How to check
Original: Choose a file
Edited: Choose a file
Loading the local document engine…
Verify a saved signature
A downloaded proof can be verified in a fresh browser session. Verification checks the signed layer and signature policy; it does not establish the signer’s real-world identity or independently verify the source files.
Full proof verification result
How to check that your files stay on this device
- Open your browser’s developer tools and Network panel. Wait for the engine to say “Ready”, then clear the request list. Drop two files, compare, sign or verify a saved proof: no requests appear.
- Or wait for “Ready”, turn the network off in developer tools, and compare two files. It still works.
- Reload with the network on. In Network, select the page request and inspect its response headers for
Content-Security-Policy.
The page loads its scripts, document engine and images from this site before it is ready. Its Content Security Policy blocks fetch, XHR, WebSockets, beacons and form submissions. File operations run locally.
What this browser edition covers · local files, no uploads
DOCX, XLSX and PPTX, using Milleleaf’s existing format adapters and loss inventory. All apps are treated equally: compare the file, whoever made the software.
ODF conversion needs a LibreOffice subprocess and is not in this browser build. Native BoringSSL and PDF writers are also omitted because they cannot run in this WebAssembly build. This page compares files; it does not render document pages or export a replacement document.
Large or complex files can take longer or exceed browser memory. Signature verification proves the integrity of the signed layer, not that the inventory detected every possible change.