Nobody asks you to prove a design is yours on a good day. The question arrives when a client stops paying and keeps using the logo, when a contest host ships a rejected entry under someone else's name, when a platform flags your work as generated, or when a registration is challenged. By then it is too late to start keeping records. Knowing how to prove a design is yours is a filing habit, and the habit has to exist before the dispute does.
The habit is cheap. Most of the evidence is produced by doing the work properly. The task is to stop throwing it away, keep it dated and untouched, and add the two things the tools do not generate: a money trail and a written account of the process.
The short answer. Keep the native file with layers intact, leave version history on, save the sketches and the brief, export dated PDFs at each milestone, attach Content Credentials at export, and file the contract and invoices beside them. Then write a one-page process note. Together they show authorship; the contract alone settles ownership.
The four moments you will be asked to prove it
A client dispute usually turns on ownership rather than authorship. Nobody doubts you drew the thing; the argument is what the payment bought. The contract and the invoices carry it.
A contest host reusing a rejected entry is the opposite. Authorship is the whole fight, and the host will cite terms claiming a licence over every submission. Your defence is a dated native file that predates the entry, plus a copy of the terms as they read that day. The design contests page covers why those terms are the reason to decline.
A platform flagging the work as generated is a blunter problem. Classifiers look at pixels and metadata and cannot see your layers. The remedy is provenance attached to the export itself, which is what Content Credentials for designers carry, plus a process record for a human reviewer.
A challenged registration is the formal case: dated evidence of creation, an account of what a person made and what was generated, and a chain of title.
What each layer of evidence proves
The native working file with layers intact
The .fig, .psd, .ai or .afdesign file with every layer, mask and hidden experiment in place. It is the strongest single piece of evidence you can hold, because it contains the decisions: the three rejected wordmarks on a hidden layer, the grid you built and then broke. Whoever took a flattened export cannot produce this. Keep a copy you never edit.
Version history in the design tool
Figma and the Adobe cloud documents record every save with a timestamp and the account behind it. Figma's documentation explains how version history is captured and how long each plan keeps it, and retention is the catch on a free plan. Name versions at milestones so they survive; version history as the design record has the tool-by-tool detail.
Sketches, the brief and the rejected rounds
Photographs of paper sketches, the brief, the thread where the scope changed, and the directions the client turned down. A thief has a result; you have a sequence.
Exported PDFs with timestamps
Export a PDF at each milestone and leave it untouched. A PDF date on its own is easy to fake, so this layer only works when it agrees with the others. Emailing it to the client plants it on a mail server you do not control, a better timestamp than your own disk.
Commit history, when code is involved
If the design shipped as code, the Git log is a dated, author-attributed record of every change. Commit under your own name and keep the early history.
Content Credentials attached at export
Content Credentials, the C2PA implementation, write a signed manifest into the exported file naming the producing tool, the account, and whether generative features were used. Adobe's help pages set out what Content Credentials record and how to attach them. They attest to the export event. They cannot say who moved the mouse, and most social platforms strip them on upload.
The contract and the invoice trail
The signed agreement, every invoice and receipt, and the delivery email with the final files attached. This is the only layer that speaks to ownership: who commissioned the work, what was paid, and what rights moved when. See the rates, contracts and scope pillar for what the agreement should say.
The written process note
One page, written at delivery, that turns a folder of files into an account a reviewer can follow. The template is below.
How to prove a design is yours: the evidence table
| Evidence | What it proves | How easy to fake | Cost to keep |
|---|---|---|---|
| Native file with layers | Sequence of decisions, authorship | Hard; slower than doing the work | Storage only |
| Tool version history | Dated saves by a named account | Hard, but free-plan retention erases it | Free |
| Sketches, brief, rejected rounds | The work answered a problem over time | Moderate; photo dates are soft | Minutes |
| Milestone PDFs sent by email | A fixed state on a third-party-recorded date | Easy alone, hard when it matches the history | Nothing extra |
| Git commit history | Author, date and content of every code change | Moderate; signed commits cannot be backdated | Free |
| Content Credentials | Producing tool, account, generative use | Hard to forge, easy to strip | Free in supporting tools |
| Contract and invoices | Who commissioned, what was paid, what rights moved | Hard; two parties and a bank | Exists if you invoice |
| Process note | A human account tying the rest together | Easy to write late, so send it dated | Twenty minutes |
| Screenshot or flattened export | An image existed on your machine | Trivial; anyone with the final file can make one | Not worth keeping |
The last row is the one most designers reach for. A screenshot or a JPEG shows you had the finished image, and so does the person who took it from you. Evidence gets stronger the further it sits from the final pixels: the export is what a thief has, and the layers, the timeline and the emails are what only the author has.
Made it versus own it
Authorship is a fact about history: a person did the work on certain dates. The stack above proves it. Ownership is a fact about law: copyright belongs to the author at creation unless the work was made as an employee or assigned in writing. The US Copyright Office's Circular 30 on works made for hire sets out when commissioned work belongs to the commissioner; for freelancers it usually does not, unless the contract says so.
That cuts both ways. If your contract assigns copyright on final payment and the client has not paid, you still own the work, and the invoice trail proves it. If the contract is silent, you own it and the client holds an implied licence of uncertain scope. Write the assignment clause deliberately and pair it with the AI disclosure clause: the Copyright Office's registration guidance on AI-generated material requires applicants to disclose generated content, and a mostly generated design may have no copyright to assign.
The process note template
Write it at delivery and email it to the client with the final files. Sending it is the point: a note on your disk can be written at any time; one sitting in two inboxes cannot.
Process note: [project] for [client], delivered [date]. Brief received [date] from [name]; scope agreed in [contract or email reference]. Work carried out by [your name] between [start] and [end] in [tool and version]. Directions presented: [number] on [dates]; direction [n] selected on [date]. Native file: [filename], version history in [tool or location]. Milestone exports: [list with dates]. Generative tools used: [none, or the step and what was generated]. Stock, fonts and third-party assets: [list with licences]. Copyright: [retained until final payment / assigned on payment received [date] / per clause [n]]. Signed, [name, date].
Use it on every commissioned project, and on any contest you were unwise enough to enter.
Frequently asked questions
Does registering a copyright prove I made the design?
No. Registration creates a public record and, in the United States, is required before suing for infringement, but the office does not verify authorship when it accepts a filing. If the claim is challenged, you fall back on the same stack: native files, version history and the contract.
What if I only have the flattened export?
Then you have what the other party has. Look for indirect evidence: emails where you sent drafts, cloud storage revision logs, the invoice, a colleague who saw the work in progress. From now on, the native file is the deliverable you keep and the export is the one you give away.
Can a client claim my design because they paid for it?
Only if the contract assigns copyright, or the arrangement was employment. Payment alone buys a licence of uncertain scope and transfers authorship in no jurisdiction. If the client believes they own the work outright, the answer is in the signed agreement, so make the clause explicit before the first invoice.
How long should I keep process files?
At least as long as the client is using the design plus the limitation period for contract claims in your jurisdiction, commonly six years. In practice, indefinitely; storage is cheap. Archive the native file, the milestone PDFs and the process note together, and never edit the archive.
What to do on Monday
Open the folder for your current project. If it holds a final export and an invoice, you know how to prove a design is yours in theory and not in practice. Add the native file, name the version history, file the brief and the rejected rounds, and write the process note before you send the finals.
Then read the Proof of Work hub, starting with portfolio provenance, on showing this record publicly so the work is believed before anyone disputes it. The case against spec work has always been that unpaid work is unprotected work. The record protects the paid kind.