Proof of ownership before a dispute is worth something. Proof of ownership created after a dispute starts is worth much less, and sometimes nothing at all. This week's stories about a 1.5 billion dollar AI copyright settlement made that point loudly, but the same math plays out on a much smaller scale every week: a freelancer's script gets copied, a founder's pitch deck turns up in a competitor's deck, a photographer's image shows up on someone else's site with the watermark cropped out. In every one of those cases, the question that decides what happens next is not who actually made this first, it's who can show it. This post is about the five minutes that answer that question before you ever need to ask it.
Why proof made after the fact is worth less
Once a dispute starts, anything you produce is suspect by default, not because anyone thinks you're lying, but because the other side has every reason to assume you might be, and a judge or a licensing negotiator has no way to tell the difference between a file created last year and a file that was edited last night to look older. A document's metadata can be changed. A file's date created field can be changed. An email you send yourself with an attachment proves you sent an email, not that the attachment existed on that date in that exact form. None of that is a flaw in the legal system, it's just what happens when the only evidence available was generated by the person who has an interest in the outcome. Proof that shows up only after a conflict has already gone sideways will always look like exactly that: proof someone assembled once they had a reason to.
What a few minutes actually creates
Sealing a file, in practical terms, means running it through a process that produces two things: a cryptographic hash of the exact file, a fingerprint that changes completely if a single character changes, and a qualified timestamp attesting that this specific hash existed at this specific moment. Under the eIDAS regulation in the EU and ZertES in Switzerland, a qualified timestamp carries legal weight specifically because it comes from a regulated, audited source rather than from your own computer's clock. That combination, hash plus qualified timestamp, is what turns "I made this" into "here is evidence this exact file existed on this exact date, from a source neither party controls." It doesn't require you to explain your creative process or hand over the file itself for public inspection. It takes a few minutes because the file never leaves your control in any way that matters, it's the fingerprint and the moment that get sealed and certified, not the content getting published somewhere.
Identity is what makes a claim yours
A sealed file with no verified person behind it is still just an anonymous claim, no different in weight from a Post-it note that says "I was here first." What turns a timestamp into evidence that supports your specific claim is tying it to an identity that has actually been checked, not just typed into a form. This is the part people skip, because it feels like the least interesting step, but it's the one that answers the second question any dispute raises: not just did this exist on this date, but who is claiming it, and can you show that's really them. A timestamp with a verified identity behind it is a statement two independent parties can stand behind. A timestamp with an unverified name typed next to it is a statement only you are making, which is exactly the position you're already in without any of this.
A habit, not a project
None of this is a guarantee that you'll win a future dispute, no timestamp decides that, and anyone who tells you otherwise is overselling. What it does is put you in a materially stronger position if a dispute ever happens, and it costs almost nothing to do it now, while it costs everything to try to manufacture it later. The trick is treating it like a habit attached to your existing workflow rather than a project you'll get to eventually: the day you finish a draft, a design, a dataset, a contract, a piece of research, that's the day it gets sealed, not the day someone challenges you on it. Most files people care about protecting sit finished on a hard drive for months before anyone thinks to do anything with them. The fix isn't complicated, it's just a few minutes spent before instead of after. If you want to see what that looks like, start by sealing a file and see how the process actually works.
