Skip to content
PickZeal
    Text and code tools

    Document Timestamp

    Prove a PDF or Word file existed on a date. Its SHA-256 hash is recorded in the public Sigstore Rekor log. Free, and the file never leaves your device.

    • Runs in your browser
    • Nothing is uploaded
    • Free, no sign-up

    Your file stays on your device. Only its SHA-256 hash, a signature and a one-time public key go to the public Sigstore Rekor log. The entry is public and permanent: it cannot be deleted.

    This free document timestamp tool gives you proof that a PDF or Word file existed at a point in time, without uploading it. Your browser calculates the file's SHA-256 hash and records it in Rekor, the public transparency log run by the open-source Sigstore project. You get back the Rekor entry UUID, the log index and the SHA-256 hash, plus a receipt you can keep with the file.

    How to timestamp a document for free

    1. Add your PDF, .docx or .doc file above. Its SHA-256 hash appears straight away.
    2. Click Timestamp in Rekor. Your browser creates a one-time key, signs the file, and sends the hash, signature and public key to Rekor.
    3. Rekor adds the entry to its log and returns the time it was recorded.
    4. Click Download receipt (.json) and store it next to the original, untouched file.

    The one-time private key is never saved. It is only there because Rekor requires every entry to be signed, and it is thrown away as soon as the entry is created.

    What you get back

    ValueWhat it means
    SHA-256 hashThe 64-character fingerprint of your exact file. Change one byte and it changes completely.
    Log indexThe entry's position in the Rekor log. The easiest value to share and look up.
    Entry UUIDThe long ID of the entry: log shard ID plus the hash of the entry itself.
    Logged atRekor's integrated time, the moment the log accepted the entry, in UTC.

    How to prove a document existed on a date

    Months or years later, anyone can check the timestamp without PickZeal. First hash the original file:

    sha256sum contract.pdf            # Linux
    shasum -a 256 contract.pdf        # Mac
    Get-FileHash contract.pdf         # Windows PowerShell

    Then look up the entry by its log index on search.sigstore.dev, or ask the Rekor API directly, and check that it holds the same hash:

    curl "https://rekor.sigstore.dev/api/v1/log/entries?logIndex=YOUR_LOG_INDEX"

    If the hash in the entry matches the hash of the file, that exact file existed when Rekor recorded the entry. You can also search Rekor by hash with the official rekor-cli tool: rekor-cli search --sha sha256:YOUR_HASH.

    How to verify a document has not been changed

    A SHA-256 hash works like a fingerprint for the exact bytes of a file. If even one character, space or hidden setting changes, the hash is completely different. So when the hash of the file you have today matches the hash in the Rekor entry, the file has not been changed since it was timestamped.

    This also means harmless actions break the match. Opening a .docx and saving it again, re-exporting a PDF, adding a signature, or letting a cloud drive convert the file all create new bytes. Timestamp the final version, then keep that copy read-only.

    Rekor vs OpenTimestamps vs RFC 3161 timestamps

    MethodTime to proofCostHow it is checked
    Sigstore Rekor (this tool)SecondsFreePublic log, search by hash or index
    OpenTimestamps (Bitcoin)Hours, until a block confirmsFreeNeeds the .ots proof file
    RFC 3161 timestamp authoritySecondsFree to paidSigned token from one company
    Qualified eIDAS timestampSecondsPaidLegal presumption in the EU

    Rekor gives a result in seconds, can be searched by anyone, and does not depend on keeping a separate proof file. OpenTimestamps anchors hashes in the Bitcoin blockchain, which takes longer to confirm; you can create one with the free Bitcoin Timestamp tool. An RFC 3161 timestamp is a signed token from a single timestamp authority. A qualified timestamp under the EU eIDAS rules is the one with a built-in legal presumption, and it is a paid service. For every method side by side, see our guide on how to prove a file existed on a date.

    What a Rekor timestamp does not prove

    • Who wrote the file. The one-time key is not linked to your name or email, so the entry proves when, not who.
    • That the file did not exist earlier. It proves the file existed no later than the logged time.
    • What the file says. Rekor stores only the hash, never the content.

    Your document stays private

    The document never leaves your device, and PickZeal does not receive the file or its hash. What goes into Rekor is public and permanent: the SHA-256 hash, the signature and the one-time public key. A hash cannot be turned back into a document, but someone who already has a copy of the exact same file could hash it and find your entry. If the fact that a file exists is itself confidential, do not timestamp it in a public log.

    Need a fingerprint of a piece of text instead of a file? Try the Text to MD5 Hash Generator, or see all free in-browser tools.

    Frequently asked questions

    How do I prove a document existed on a certain date?

    Record a fingerprint of the file somewhere you cannot change later and that others trust. This tool records the SHA-256 hash of your PDF or Word file in the public Sigstore Rekor log, which stamps it with the time it was added. Later, anyone can hash the same file, find the matching Rekor entry and see that the file existed at that time.

    Is my document uploaded?

    No. The file is read, hashed and signed in your browser on your own device. Only three things are sent to Rekor: the SHA-256 hash, a signature and a one-time public key. None of them can be turned back into the document. PickZeal never receives the file or the hash.

    What happens if I timestamp the same file twice?

    The SHA-256 hash is the same both times, because the file is the same. Each run uses a new one-time key, so Rekor creates a separate entry with its own UUID, log index and time. The first entry is never replaced, so the earliest one remains your proof of when the file first existed.

    Why does my file no longer match its timestamp?

    The hash only matches the exact same bytes. Opening a Word file and saving it again, exporting a new PDF, or a cloud drive converting the file all change the bytes and give a completely different hash, even if the text looks the same. Keep an untouched copy of the original file next to its receipt.

    Can a Rekor entry be deleted or changed?

    No. Rekor is an append-only transparency log. Each entry is part of a Merkle tree whose signed root is published and watched by independent monitors, so removing or editing an entry would be detected. That is what makes it useful as evidence, and also why you should only timestamp files whose hash you are happy to make public.

    What is the difference between the Rekor UUID and the log index?

    The log index is the entry's position in the log, a plain number that is easy to share and look up. The UUID is a longer hex identifier that combines the log shard ID with the hash of the entry itself. Either one finds the entry. The receipt saves both, plus the SHA-256 hash of your file.

    Do I need the receipt to verify the timestamp later?

    Not strictly. Anyone can search the Rekor log by the file's SHA-256 hash or by the log index. The receipt is still worth keeping because it holds the log index, UUID, time, signature, public key and the inclusion proof in one file, so you do not have to search for them.

    Is a Rekor timestamp legally valid?

    It is strong technical evidence that a file existed at a point in time, recorded by an independent public log. It is not a qualified electronic timestamp under the EU eIDAS rules and it does not prove who wrote the file. For contracts or court cases, ask a lawyer whether you also need a qualified timestamp or a notary.

    Is this free, and who runs Rekor?

    Yes, it is free. Rekor is part of Sigstore, an open-source project of the Open Source Security Foundation (OpenSSF) under the Linux Foundation. The public Rekor instance at rekor.sigstore.dev is a free public-good service, mostly used to log signatures of open-source software.

    Topic

    More on File Timestamping

    See the full File Timestamping guide

    More text and code tools

    View all tools