Who Owns the Work? Freelance IP Assignment Clauses Explained
A plain-English guide to intellectual property assignment in freelance contracts — what you keep, what the client owns, and how to protect your reusable work.
When a client pays you to create something, it is reasonable that they own the final deliverable. The problem is how broadly contracts write that ownership. A sloppy IP clause can claim not just the project, but the reusable assets you brought to it — your code libraries, design systems, templates, and internal tools.
The two phrases that matter
"Work made for hire" means the client owns the work from the moment it is created, as if they made it themselves. "Assignment" means you create it and then transfer ownership. Both can be fine — the danger is in the scope, not the label.
The phrase to hunt for
"All work, materials, and intellectual property created in connection with the project." Read literally, "in connection with" can include the reusable tools and pre-existing IP you used to do the job — not just what you built for this client.
What you should keep
- Pre-existing IP: anything you owned before the project started.
- Reusable components: frameworks, libraries, boilerplate, and design systems you reuse across clients.
- Internal tools: scripts and utilities that help you work, not deliverables themselves.
- Your general skills and know-how — which no contract can legitimately take.
Worried your contract has this clause? fynPrint flags it in plain English in about 60 seconds — your first analysis is free.
Analyze free →The carve-out that fixes it
You rarely need to fight the whole clause. You need one sentence: the client owns the specific deliverables, and you grant them a license to any of your pre-existing or reusable materials embedded in those deliverables, while retaining ownership of those materials yourself. That gives the client everything they actually need without signing away your toolkit.
Get paid before you transfer
Watch the timing. IP should transfer on full payment, not on delivery. If ownership passes the moment you hand over the work, a client can use it while withholding your fee. Tie the assignment to "upon receipt of full payment."
fynPrint reads IP clauses specifically for these problems — overbroad scope, missing carve-outs, and transfer-before-payment — and suggests the exact wording to propose.
Frequently asked questions
Is "work for hire" bad for freelancers?
Not inherently. It is common and often acceptable for the deliverables themselves. The risk is when "work for hire" is paired with overbroad scope that pulls in your reusable, pre-existing assets.
How do I keep ownership of my templates and reusable code?
Add a carve-out stating that your pre-existing and reusable materials remain yours, and grant the client a license to use them within the deliverables rather than assigning ownership.
When should IP ownership transfer to the client?
On full payment. Tying the transfer to "upon receipt of full payment" prevents a client from using the work while withholding your fee.
Related reading
Check your own contract in about 60 seconds
fynPrint flags risky clauses in plain English and drafts a professional negotiation email. Your first analysis is free.
fynPrint is not a law firm. AI-generated analysis is legal information, not legal advice.