Check the file you received

Is this the same file your sender intended? Compare it with their verification link, locally in your browser.

Your file and its reference

One file, up to 20 MiB. File contents stay in this tab.

No file selected.

Received a link? Paste it here. Creating your own? Leave this blank and choose Create a verification link.

Sending work of your own?

Create a link for your next file, or keep scope and client-response notes in a delivery record.

Prepare a delivery record

Check without relying on TDS

The format is public. Keep the link and verify the SHA-256 and byte count using your own software. Our small downloadable verifier runs offline with Node.js.

Need a Bitcoin-backed timestamp?

OpenTimestamps is a separate service and protocol for time proofs. A TDS verification link does not create a Bitcoin timestamp.

Explore OpenTimestamps

Run this check in your workflow

Download a working starter with a known example, an offline runner and an optional GitHub Actions template. No npm dependencies or API keys.

  1. Unzip and run: node tools/run-file-check.mjs. The example must match.
  2. Change the example file while keeping its reference. Run again: the check must fail.
  3. Replace both with your own file and a separately trusted reference.

The scripts never contact TDS. Optional GitHub use uploads files to your repository and prints fingerprints in logs; keep confidential files offline or in an appropriately restricted repository. A match proves only file equality, not delivery or acceptance.

How to verify a file checksum independently

A SHA-256 checksum describes file contents. In TDS, a match requires both the same SHA-256 digest and the same byte count as the sender’s reference. Compare the exact downloaded file, not a screenshot or an exported copy.

Why do two PDFs that look the same have different hashes?

A saved PDF can contain changed metadata, compression or other bytes even when the visible pages look unchanged. For wording changes use Compare PDF text; use a checksum for exact-byte comparison.

Does a matching checksum prove a file is safe?

No. A malicious file can match its own checksum. Obtain the reference through a trusted channel; this tool does not scan for malware, verify identity or certify delivery.

Can I paste any published SHA-256 digest here?

This interface accepts a complete TDS reference link, which also includes the byte count. For a raw digest, use the commands below and compare it manually.

Windows PowerShell

Get-FileHash -LiteralPath 'document.pdf' -Algorithm SHA256
(Get-Item -LiteralPath 'document.pdf').Length

Linux (GNU Coreutils)

sha256sum -- 'document.pdf'
wc -c < 'document.pdf'

Replace document.pdf with your own file path. These commands read the file locally. Compare the digest and byte count with the TDS reference; uppercase and lowercase hexadecimal letters represent the same digest.

A reproducible three-byte example

Create a plain file containing exactly abc with no newline. It has 3 bytes and this SHA-256 digest. Renaming it leaves the digest unchanged; changing its contents or adding a newline changes it. The built-in known example uses these same bytes.

ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

Independent documentation

All tools

Useful to someone else?

Share this page with your team. The link opens the tool or guide, with an empty workspace.

Link to this tool from your website

Select and copy this HTML into a relevant resource page or README. It links to an empty workspace; no files or results are shared. Attribution is optional.