Compare
Timestamp vs email-to-self vs file metadata: which record helps an architect most?
TimeBinder adds a layer of protection against AI and human fraud and disputes. For architects, it is a dated record of the exact file, which an email to yourself or the file metadata cannot reliably give.
A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. The fingerprint is made in the browser, and the file stays on your device. Your first Pooled TimeBind is free; after that, TimeBinds start from US$5, and an ASAP TimeBind is US$15.
In the TimeBinder app, drag and drop your file. Your browser creates its digital fingerprint. Your file stays on your device—we never receive or see its contents.
Use them together. File metadata is easy to change, an email to yourself shows when a message was sent from an account you control, cloud history helps inside one platform, and a portal receipt records when a submission arrived. A TimeBind adds something none of them does: a fingerprint of the exact file, recorded on the Bitcoin blockchain, that does not depend on your computer clock or your accounts. The files stay on your device. It shows existence no later than a recorded time, not authorship or ownership. For the general comparison, see blockchain timestamping vs emailing yourself, Git dates or a notary.
Last updated . Sources and TimeBinder pricing checked on 10 November 2026.
The five records architects usually rely on
| Record | What it shows | Weak point |
|---|---|---|
| File metadata (date modified, PDF creation date, DWG and RVT properties) | What your software and operating system wrote | Changes when files are copied, synced, re-saved or edited. Can be altered on purpose. See can a file’s date created be changed? |
| Email to yourself | The sending time in the message headers, plus the attachment | The account is yours. Attachment size limits stop large model files. Some systems rewrite or strip attachments |
| Cloud or CDE version history (ACC, SharePoint, Dropbox) | Version order and save times inside that platform | Depends on the provider and your account settings. Other parties may not accept it, and access can end when a project closes |
| Portal or transmittal receipt | When a submission or issue was received by the other party | Does not by itself show what the files contained unless you also keep the exact files |
| TimeBind | That this exact file existed no later than a recorded time and still matches its fingerprint | Does not show who made the file, or when you lodged it. Needs the exact file kept |
Cost, privacy, independence and checking
| Record | Cost | Privacy | Independent of you? | Checkable by someone else? |
|---|---|---|---|---|
| File metadata | Free | Stays on your machine | No. Your software and clock wrote it | Only by trusting the file. Easy to alter |
| Email to yourself | Free (provider limits apply) | The files sit with your mail provider | Partly. The provider’s servers stamp the message, but the account is yours | By the headers, if the other side accepts them. Large files often won’t fit |
| Cloud or CDE history | Part of the platform subscription | Files sit on the platform | Partly. The platform keeps the log | Only inside that platform, and while access lasts |
| Portal or transmittal receipt | Free | Held by the receiving party | Yes, for the lodgement time | By the receiving party. You must keep the exact files |
| TimeBind | First Pooled TimeBind free, then from US$5. ASAP US$15 | The file stays on your device. Only its fingerprint is recorded | Yes. A public ledger holds the time, not your clock or account | Yes. Checking is free. ASAP gets its own transaction that can be checked independently |
How they work together
A realistic record of a tender issue has three parts: the exact files you issued, the portal receipt that shows when they were received, and a TimeBind certificate that gives an independent date for the exact files. If someone later says "that is not what was in the pack", you can hash your archived file, match it to the certificate, and point to the receipt.
Where email-to-self falls short for large drawing sets
Sending yourself a zip is better than nothing, and it is quick for small PDFs. For a BIM export or a render folder it often fails on size, and you still depend on your mail provider and your own account to show the headers. A TimeBind records only a fingerprint, so file size is not a problem, and up to 10 files fit in one record.
Where file metadata falls short
Metadata is useful for working out what happened inside your own practice. Opening, converting, syncing or re-saving a file can change it. A drawing exported to PDF gets a new creation date. For the full list of limits, use the file date and metadata inspector on a sample file and compare the dates it reports.
A simple habit
- Finish the issue set and freeze it.
- Timestamp it. Your first Pooled TimeBind is free.
- Send it through the normal channel (portal, transmittal, email).
- Keep all three records together: files, receipt, certificate.
See also what to timestamp at each client revision round and Revit and BIM versions before issue.
What a TimeBind shows, and what it doesn’t
A TimeBind shows that this exact file existed no later than the recorded time and still matches its fingerprint. It does not show authorship, ownership or copyright, or any court outcome. Whether another party gives it weight is their decision, so keep your contracts and portal records too. This is general information, not legal advice. For the ownership question, see who owns architectural drawings.
What each record can and cannot protect
File metadata can be edited, and an email to yourself depends on systems you do not control. A TimeBind records the fingerprint of the exact file on a public ledger, giving a layer of protection when a date is disputed or a copy has been altered. The three records work together, but only the TimeBind is checkable by someone outside your practice.
FAQ
Is emailing myself useless?
No. It is a record, and it costs nothing. It is just limited: it relies on an account you control and does not travel well for large files.
Can a TimeBind replace cloud version history?
No. Version history helps your team work. A TimeBind gives an independent date for a specific issued file, which can matter when the other party is outside your platform.
Does a TimeBind show when I lodged my tender?
No. The portal receipt shows that. A TimeBind shows the files existed no later than its recorded time, so timestamp before you lodge.
What does it cost?
Your first Pooled TimeBind is free, with no credit card required. After that, from US$5; ASAP is US$15. See plans and pricing
General information, not legal advice. A TimeBind shows that this exact file existed no later than the recorded time and still matches its fingerprint. It does not show authorship, ownership, copyright status or how any court, tribunal, client or insurer will treat it.
Timestamp your next issue set
Add the issued drawings, the model export and the transmittal to one TimeBind (up to 10 files) before you send them. Your first Pooled TimeBind is free.
Make your first TimeBind free → See plans and pricing
Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Your browser makes the fingerprint and the file stays on your device. A TimeBind shows a file existed no later than the recorded time. It doesn’t show who made it.
Keep files, receipt and certificate together
Add the record a third party can check to your issue habit. Send through the normal channel and keep all three records. The Free plan is $0 and includes 1 Token a month.
See plans and pricing