Who owns the copyright to freelance work by default?

Under US copyright law the creator owns the copyright automatically, so by default the freelancer owns commissioned work until a contract transfers those rights. Most client contracts include language to move ownership to the client, which is why the IP clause matters.

What is the difference between a license and an assignment?

A license grants the client permission to use the work while you keep ownership and can sometimes reuse or relicense it. An assignment transfers ownership outright, so after a valid written assignment the client owns the copyright and you generally cannot reuse the work.

Does calling a freelance contract 'work for hire' actually transfer ownership?

Not always. In US copyright law, work made for hire applies only to employees within their employment or to specially commissioned works in a limited set of categories with a signed agreement. Much contractor work does not qualify, so good contracts add a fallback copyright assignment tied to payment. This is general information, not legal advice.

Should I transfer IP before getting paid?

No. Tie any transfer of rights to receipt of payment in full so you are not handing over ownership while waiting Net 30 or Net 60. Until full payment, the contract should state that you retain all rights.

Who Owns the Work? Work-for-Hire vs. License vs. Assignment in Freelance Contracts

Short answer: As an independent contractor, you usually own the copyright in what you create the moment you create it—unless your contract transfers it. Most client contracts do exactly that, using one of three mechanisms: a work-for-hire clause, a copyright assignment, or a license. They are not interchangeable, and the wrong one can cost you your portfolio rights, your reusable tools, and future income.

This guide explains the three models in plain English, the IP traps to watch for, and the exact language you can propose before you sign.

Key takeaways

By default, the freelancer—not the client—owns the copyright in commissioned work.
A license lets the client use the work while you keep ownership. An assignment transfers ownership outright. "Work made for hire" is a specific legal status that, for contractors, often does not apply the way clients assume.
Tie any transfer of rights to final payment, and carve out your background IP (tools, libraries, templates) and your portfolio rights.
Pair IP terms with payment timing and liability—handing over IP before you are paid is one of the biggest contract red flags.

The Default: You Own What You Make

Under US copyright law, the person who creates an original work is the author and owns the copyright automatically—no registration required. For a freelancer, that means the logo, the code, the article, or the design is yours until a contract says otherwise.

Clients know this, which is why their contracts almost always include language to move those rights to them. Your job is to make sure that transfer is fair, paid for, and scoped correctly.

The Three Models, Explained

1. License (you keep ownership)

A license grants the client permission to use the work while you retain the copyright. Licenses can be:

Non-exclusive — you can license the same or similar work to others.
Exclusive — only the client may use it, but you still own it.
Limited — restricted by time, territory, medium, or purpose (e.g., "web use only, 2 years").

Licensing is often the freelancer-friendly option: the client gets what they need, and you keep an asset you can reuse or relicense.

2. Copyright Assignment (you transfer ownership)

An assignment is an outright transfer of ownership to the client. After a valid written assignment, the client owns the copyright and you generally cannot reuse the work. Many "work for hire" contracts are, legally, assignments in disguise—and that is usually fine, if it is paid for and scoped.

3. Work Made for Hire (a specific legal status)

"Work made for hire" has a precise meaning in US copyright law. A work is made for hire only when it is either:

created by an employee within the scope of their employment, or
specially commissioned for one of a limited set of categories and both parties sign a written agreement saying it is a work made for hire.

The catch for freelancers: a lot of independent contractor work does not fall into those special categories. So a contract can call your work "work for hire," but if it does not legally qualify, the clause may not transfer ownership on its own. That is why well-drafted contracts include a fallback assignment ("and if the work does not qualify as a work made for hire, Contractor hereby assigns…"). Laws differ by country and situation, so treat this as general information, not legal advice.

IP Red Flags to Watch For

1. IP Transfers Before You Are Paid

What it looks like: "All intellectual property rights transfer to Client upon creation/delivery."

Why it's dangerous: With Net 30 or Net 60 terms, you could hand over ownership and then wait months—or never get paid—with little leverage.

What to negotiate: Tie transfer to payment: "All rights transfer to Client upon Contractor's receipt of payment in full."

2. Grabbing Your Background IP

What it looks like: "Client owns all materials, tools, and code used to produce the deliverables."

Why it's dangerous: This can sweep up your reusable libraries, brushes, templates, frameworks, and internal tools—things you need for every other client.

What to negotiate: Carve out background IP and grant a license to it instead: "Contractor retains ownership of pre-existing and general-purpose tools, libraries, and know-how, and grants Client a non-exclusive license to use them as embedded in the deliverables."

3. No Portfolio Rights

What it looks like: Silence on whether you can show the work, or an outright ban on doing so.

Why it's dangerous: Your portfolio is your marketing. Losing the right to show work—especially under a broad NDA—can quietly hurt your pipeline.

What to negotiate: Reserve a display right: "Contractor may display the deliverables in its portfolio and marketing after public release, excluding any Client confidential information." For sensitive work, ask for a delay or anonymized rights rather than a blanket ban.

4. Moral Rights and Credit Waivers

What it looks like: "Contractor waives all moral rights, including the right to attribution."

Why it's dangerous: You may lose the right to be credited as the creator. That matters more in some fields (and some countries) than others.

What to negotiate: Where credit matters to you, request attribution or narrow the waiver to specific uses.

5. "Work for Hire" With No Fallback Assignment

What it looks like: A bare "this is a work made for hire" line with nothing else.

Why it's dangerous: If the work does not legally qualify (see above), ownership may not transfer cleanly, creating disputes later for both sides.

What to negotiate: Ensure there is a fallback assignment tied to payment, and that the scope of what transfers is clearly listed.

Negotiation Language You Can Reuse

Payment-gated transfer (assignment):

"Upon Contractor's receipt of payment in full, Contractor assigns to Client all right, title, and interest in the final deliverables created specifically for Client under this Agreement. Until full payment, Contractor retains all rights."

Background IP carve-out:

"'Background IP' means materials, tools, libraries, and know-how owned or developed by Contractor independently of this Agreement. Contractor retains all Background IP and grants Client a perpetual, non-exclusive license to use it as incorporated into the deliverables."

License instead of assignment (when you can keep ownership):

"Contractor grants Client an exclusive, worldwide license to use the deliverables for [purpose]. Contractor retains copyright ownership and the right to reuse underlying techniques and non-client-specific components."

Portfolio rights:

"Contractor may reference and display the deliverables for self-promotion after public launch, excluding Client confidential information."

License or Assignment: Which Should You Push For?

There is no single right answer—it depends on leverage, price, and how reusable the work is:

Lean toward a license when the work is reusable (templates, components, stock-style assets) or the fee is modest. You keep an asset.
An assignment is reasonable for bespoke, client-specific work—if the price reflects that you are selling the asset outright and it is gated on payment.
Always protect background IP and portfolio rights regardless of model.

If a client demands full assignment for a small fee, treat ownership as a line item: full IP transfer should cost more than a license.

When to Walk Away

Consider declining or re-scoping if:

The client wants ownership of your reusable tools and refuses any carve-out.
IP transfers before payment and they will not gate it on payment.
A broad NDA plus an IP grab leaves you unable to show any of your work.
The fee does not reflect that you are selling an asset, not renting it.

How ClearTerm Helps

IP terms are scattered across "Ownership," "Deliverables," "Confidentiality," and "Definitions"—and the load-bearing word is often a single phrase like "work made for hire" or "all materials." ClearTerm reads the whole contract and surfaces:

Who owns the deliverables and whether transfer is gated on payment
Background-IP grabs that sweep up your reusable tools
Missing portfolio rights and broad moral-rights waivers
"Work for hire" clauses with no fallback assignment

You get plain-English explanations and negotiation language you can paste into redlines. Comparing a revised contract? Diff Mode flags whether IP terms got worse before you sign.

See How It Works, compare plans on Pricing, and run your next agreement before you hand over your rights. Try ClearTerm free →