Free tool: runs in your browser
File handover log builderfor files you receive and pass on
TimeBinder adds a layer of protection against AI and human fraud and disputes. Choose the files and your browser makes a SHA-256 fingerprint of each. Add who gave it to you and who you passed it to, then copy or save the log.
Your files are read in this browser tab and are not uploaded. The log records what you type and the fingerprints your browser makes. It does not show where a file came from, that it is genuine, or that handling met any legal standard. It is not legal advice.
Fingerprint the files and log who held them
Choose the files, add who gave each one to you and who you passed it to, and build the log. Check a file against the log later. Your files are not uploaded.
Your files are read in this browser tab to make fingerprints, and are not uploaded. What you type stays on this page.
Fingerprint each file and log who gave it to you and who you passed it to
Choose the files, and your browser makes a SHA-256 fingerprint of each one. Add who gave it to you, when, and who you passed it to. You get a log you can copy or save as a spreadsheet file, and you can check a file against the log later. The files are not uploaded.
How do I keep a record of who handled a file? The short answer
Fingerprint each file as you receive it, before you open it in a program that may save changes, and write down who gave it to you, when, and who you passed it to. A SHA-256 fingerprint changes if even one byte of the file changes, so you can later check that the copy in front of you matches the one you logged. Keep the original received file apart from any working copy.
This tool builds that log in your browser. A TimeBind of a file you already hold can show that exact file existed no later than a recorded time and still matches. It does not show where a file came from or that it is genuine.
Why this came up in November 2026
Questions about trusting digital files are reaching courts and the people who advise them. Demand for this topic is smaller than for creators’ topics, and this page says so. Counts below were read on 13 November 2026 (Australia/Brisbane) unless the text says another date. An X post by @Udntnonutn from 15 October 2026 about representatives of OpenAI and Meta warning federal judges about convincing AI-generated video had 2,036 impressions and 111 likes on 12 November. A post by @Mr_jay_pee the same day, predicting that video evidence in court will not be enough once anyone can claim it is AI-generated, had 6,379 impressions and 34 likes. A post by @htTweets on 25 October 2026 about a man reported to have used an AI-generated image to fake a death in court had 3,895 impressions. These are demand signals and opinions, not legal findings.
The tool fills a practical gap for lawyers and paralegals: a plain log of fingerprints, names and dates that anyone can read, and a quick way to check a file against it. It makes no claim about what a court will accept. For records on a deepfake dispute, see the deepfake evidence authentication record checklist.
Sources: @Udntnonutn, X, @Mr_jay_pee, X and @htTweets, X.
What this tool does and does not do
The honest job of this page is to keep a plain log and make one check easy. See also the bulk SHA-256 hash manifest and the glossary entries for SHA-256 and fingerprint.
| Part | What it does | What it does not do |
|---|---|---|
| Fingerprints | Makes a SHA-256 fingerprint of each file in your browser. The file is not uploaded. | Show where a file came from or that it is genuine. |
| The log | Records the names, dates and notes you type next to each fingerprint, with a note that the clock is your own device clock. | Check what you type, or certify handling. |
| The check | Compares a file you choose with the fingerprints in the log. | Explain a mismatch. A re-save can change a fingerprint. |
| A TimeBind of a file you already hold | Records that an exact file existed no later than a recorded time and still matches, using a SHA-256 fingerprint made in your browser. The file stays on your device. | Show where a file came from, that it is genuine, or that handling met any legal standard. |
If the log is something you may need to show later
After you build the log:
- Save the received files unchanged, and keep working copies separate.
- Make a TimeBind of each exact file you already hold. The fingerprint is made in your browser and the file stays on your device. You can later download a Proof of Time Certificate.
- Store the files, the log and the certificate together, with the date you received each file.
A TimeBind shows the exact file existed no later than the recorded time and still matches. The page clock is your own device clock, so a TimeBind gives a time you did not set yourself.
First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.
What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.
File handover log builder: FAQ
Are my files uploaded?
No. Each file is read in your browser tab to make a SHA-256 fingerprint. The file stays on your device. The names and notes you type stay on the page.
Does the log make a file reliable?
No. It records what you typed and the fingerprints your browser made. It does not show where a file came from or that it is genuine.
Why would a re-saved file not match?
A SHA-256 fingerprint changes if even one byte changes. Some programs change a file when they save it. That is why you fingerprint a file as received, before you open and save it.
Is the date in the log reliable?
It comes from your own device clock, which nobody has checked. A TimeBind of the same file records that the exact file existed no later than a recorded time, set outside your device.
Can this be used as chain of custody?
This page does not claim to meet any legal standard for handling. It gives you a plain log you can adapt. Ask a qualified adviser what your court or matter requires.
Is anything I type or tick sent to TimeBinder?
No. This page runs in your browser. What you type stays on the page.
Related guides and tools
- Deepfake evidence authentication record checklistRecords for a deepfake dispute
- Bulk SHA-256 hash manifestFingerprint a whole folder
- AI filing court order response record checklistRecords after an AI filing order
- Copy dispute timeline builderPut events in order
- GlossaryPlain definitions of fingerprint, SHA-256 and existed no later than
- All free toolsPrivate, in-browser tools
Date the exact files you already hold
Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of each file as you received it.
- Open the app and sign in with email or Google.
- Add your files. They stay on your computer.
- Seal them and download your Proof of Time certificates.
First Pooled TimeBind free, no card, then from US$5. See pricing.
Related glossary entries: litigation hold and spoliation of evidence.