Who owns the work a freelancer creates — the freelancer or the client?

By default under U.S. copyright law, the freelancer owns the work they create unless a valid work-for-hire agreement exists or IP rights are explicitly assigned in writing. This surprises many clients who assume that paying for the work means owning it. A written freelance contract with a clear IP assignment clause is the only reliable way to transfer ownership.

What is the difference between work for hire and IP assignment?

Work for hire means the client is legally considered the author from the moment of creation — as if the client created it themselves. IP assignment means the freelancer creates the work as the original owner, then transfers rights to the client. Work-for-hire only applies to specific categories of work (like contributions to collective works) and requires a signed written agreement. For most freelance projects, IP assignment is the correct mechanism.

Can a freelancer reuse work they created for a client?

It depends entirely on the contract. If the contract assigns all IP rights to the client, the freelancer cannot reuse that work — not even in a portfolio. Many freelancers negotiate a license-back clause that lets them display the work in portfolios or reuse non-proprietary components like code frameworks. If the contract is silent on reuse, the answer depends on who owns the IP, which circles back to whether an assignment was made.

Do I need an IP clause for every freelance project?

Yes. Even small projects produce copyrightable work — a logo sketch, a blog post, a few lines of code. Without an IP clause, ownership defaults to the creator (the freelancer), which means the client may not legally own the deliverables they paid for. The cost of adding an IP clause is zero. The cost of a dispute over ownership can be tens of thousands of dollars.

What happens to IP rights if the client never pays?

If your contract ties IP transfer to payment (which it should), unpaid work means the IP rights never transfer. This is one of the most important protections a freelancer can include: a conditional assignment clause that states rights transfer only upon receipt of full payment. Without this clause, a client could receive the deliverables, refuse to pay, and still claim ownership.

Who Owns the Work? IP Ownership Clauses Every Freelance Contract Needs

A freelancer delivers a logo. The client pays the invoice. Six months later, the freelancer uses the same design concept for another client. Is that legal?

A developer builds a custom web application. The client assumes they own the code. A year later, the developer launches a competing product using the same codebase. Can the client stop them?

The answer to both questions depends entirely on one clause in the freelance contract — the IP ownership clause. And in a startling number of freelance agreements, that clause is either missing, vague, or wrong.

The Default Rule That Surprises Everyone

Under U.S. copyright law, the person who creates a work owns it. Not the person who paid for it. Not the person who described what they wanted. The creator.

This means that unless your freelance contract explicitly transfers ownership, the freelancer retains the intellectual property rights to everything they produce — logos, websites, articles, photographs, software, designs. The client receives the deliverable but not the legal right to own, modify, or sublicense it.

Many businesses discover this the hard way: during a rebrand when they want to modify a logo, during a lawsuit when they need to prove ownership, or during due diligence when an investor asks who owns the company's IP assets.

Work for Hire vs. IP Assignment: Know the Difference

There are two legal mechanisms for transferring IP from a freelancer to a client. They are not interchangeable, and using the wrong one can leave your contract unenforceable.

Work for Hire

Under the work-for-hire doctrine, the client is treated as the legal author of the work from the moment of creation. The freelancer never owns the IP — the client does from day one.

But work for hire has strict requirements. For freelancers (as opposed to employees), it only applies when:

The work falls into one of nine specific categories defined by the Copyright Act (contributions to collective works, translations, supplementary works, compilations, instructional texts, tests, test answers, atlases, and parts of motion pictures)
Both parties sign a written agreement stating the work is made for hire

If the work doesn't fit one of those nine categories — and most freelance deliverables don't — a work-for-hire clause alone won't transfer ownership. A standalone logo design, a custom software application, or an original photograph doesn't qualify.

IP Assignment

IP assignment is the more reliable mechanism for most freelance work. The freelancer creates the work as the original owner, then assigns (transfers) all rights to the client in writing.

A properly drafted IP assignment clause covers:

All rights, title, and interest in the deliverables
All forms and media, current and future
Moral rights waiver (where applicable under local law)
Cooperation obligation — the freelancer agrees to sign any additional documents needed to perfect the assignment (like copyright registrations)

The Belt-and-Suspenders Approach

The strongest freelance contracts use both mechanisms together: "The Work shall be considered a work made for hire to the fullest extent permitted by applicable law. To the extent that any Work does not qualify as a work made for hire, Freelancer hereby irrevocably assigns to Client all right, title, and interest in and to the Work."

This covers every scenario. If the work qualifies as work for hire, the client owns it from creation. If it doesn't, the assignment clause transfers ownership. No gaps.

The Five IP Clauses Every Freelance Contract Needs

1. The Assignment Clause

This is the core transfer mechanism. It should:

Use the belt-and-suspenders language above
Cover all deliverables defined in the scope of work
Include "in perpetuity, worldwide, in all media now known or hereafter invented"
State that the assignment is irrevocable

What goes wrong without it: The client pays for a website redesign but legally doesn't own the design files, the code, or even the right to modify the site without the freelancer's permission.

2. The Payment-Contingent Trigger

IP rights should transfer only when the freelancer is paid in full. This is the freelancer's most powerful protection against non-payment.

"All intellectual property rights in the Deliverables shall vest in Client upon receipt of full payment. Until such payment is received, all IP rights remain with Freelancer."

What goes wrong without it: The client receives the deliverables, ghosts on the invoice, and uses the work anyway — and the freelancer has no leverage because they already transferred the IP.

3. The Pre-Existing IP Carve-Out

Freelancers bring tools, frameworks, templates, and libraries to every project. A developer doesn't build a React application from scratch — they use their existing component library. A designer doesn't create every icon from nothing — they use their established design system.

The contract must distinguish between:

Project IP — created specifically for this project, owned by the client after payment
Pre-existing IP — tools and materials the freelancer brought to the project, owned by the freelancer with a license granted to the client

"Freelancer retains all rights in Pre-Existing Materials. Client is granted a non-exclusive, perpetual, royalty-free license to use Pre-Existing Materials solely as incorporated in the Deliverables."

What goes wrong without it: The client claims ownership of the freelancer's entire component library because it was "used in the project." Or the freelancer can't use their own tools on future projects because the client's contract claimed everything.

4. The Portfolio License-Back

Most freelancers need to display their work to attract new clients. Without a license-back, showing client work in a portfolio could be IP infringement.

"Client grants Freelancer a non-exclusive, worldwide license to display the Deliverables in Freelancer's portfolio, website, and marketing materials for the purpose of showcasing Freelancer's professional capabilities."

Consider adding conditions:

A waiting period (e.g., not until 90 days after delivery or public launch)
Exclusion of confidential information visible in the deliverables
Client right to request removal with reasonable notice

What goes wrong without it: Freelancers either violate the contract by showing the work, or lose their most effective marketing tool. Neither outcome is good for the working relationship.

5. The Moral Rights Waiver

In many jurisdictions, creators have "moral rights" — the right to be identified as the author and to object to modifications that could harm their reputation. Even after assigning copyright, moral rights can persist.

"To the extent permitted by applicable law, Freelancer waives all moral rights in the Deliverables, including the right of attribution and the right of integrity."

What goes wrong without it: The freelancer objects to the client modifying the delivered design or demands credit on every use — even after full IP assignment and payment.

Common IP Mistakes in Freelance Contracts

Using "work for hire" alone. If the work doesn't fall into one of the nine statutory categories, the work-for-hire clause fails and no IP transfers. Always pair it with an assignment clause.

Assigning IP before defining deliverables. If the scope of work is vague, the IP clause inherits that vagueness. "All work produced under this agreement" could mean anything — or nothing — in a dispute. Define what will be created before assigning who owns it.

Forgetting about derivative works. The client receives a logo. Later, they want to animate it, turn it into a 3D render, or adapt it for merchandise. Does the IP clause cover derivatives? If it assigns "all rights, title, and interest in all forms and media," it does. If it only assigns "the logo design," it might not.

No clause at all. The most common mistake. Many freelance contracts focus entirely on payment terms and deadlines without addressing IP ownership. Both parties assume the "obvious" answer — and discover during a dispute that their assumptions were opposite.

IP Ownership Across Different Freelance Work

The stakes and specifics vary by discipline:

Software development: Code ownership is especially complex. The developer's pre-existing libraries, open-source dependencies, and custom code all have different ownership implications. The contract should address each layer and include a technology inventory.

Graphic design: Includes logos, brand assets, illustrations, and marketing materials. Source files (like .psd or .ai files) should be explicitly included in the deliverables — or explicitly excluded if the freelancer retains them.

Writing and content: Articles, website copy, social media content, and whitepapers are all copyrightable. If a client hires a freelance writer, the default is that the writer owns every word unless the contract says otherwise.

Photography and video: Raw files, edited outputs, and outtakes each have separate ownership considerations. Many photographers license usage rights rather than assigning ownership — which is fine if the contract makes that clear.

Build Your Freelance Contract with IP Protection

A freelance contract without IP clauses is a dispute waiting to happen. Whether you're the freelancer or the client, clear IP ownership terms protect both sides.

Create your freelance contract on Contract.DIY — with IP assignment, pre-existing IP carve-outs, payment-contingent transfer, and all the clauses covered in this guide. Jurisdiction-aware and ready to sign.