Freelance Work-for-Hire Agreement: What It Is and Why You Need One

A client sends you a contract. Buried in the middle is a clause that says "all work product is considered work made for hire." You sign it. You move on.

Three months later, you want to use that project in your portfolio. Or you discover the client has licensed your work to a third party. Or you want to incorporate a technique you developed for that project into a new client's project — and you can't, because you no longer own it.

This is why every freelancer needs to understand work-for-hire before they sign anything.

What Work-for-Hire Actually Means

Under U.S. copyright law, the person who creates a work is the default owner of the copyright. But there are two exceptions — and both are commonly invoked in freelance agreements.

Employee work. If you're an employee (not an independent contractor), anything you create in the scope of your employment is automatically owned by your employer.

Commissioned work-for-hire. This only applies to specific categories of work — including contributions to collective works, compilations, translations, instructional texts, tests, atlases, and a few others. If your work falls into one of these categories AND there's a written agreement calling it work-for-hire, the company you're working for owns the copyright from the moment it's created.

Most design, writing, photography, web development, and software work falls outside the narrow "commissioned work-for-hire" categories under the Copyright Act. That means if a client wants to own the copyright to your work, they need either a work-for-hire agreement (where applicable) or an assignment of rights — a separate clause that transfers the copyright from you to them.

In practice, many clients don't know the legal distinction. They include "work made for hire" language in contracts without realizing it may not actually apply to the type of work you're doing — or that it could be invalidated if you're not an employee.

What Transfers — and What Doesn't

When you sign a work-for-hire agreement:

What transfers: Copyright ownership. The client owns the work as if they created it themselves. They can license it, modify it, sell it, and prevent you from using it.

What doesn't transfer automatically: Your moral rights (to a limited extent under U.S. law), your right to credit (unless explicitly granted), and your ownership of tools, processes, or pre-existing IP you used to create the work.

The key distinction: Work-for-hire transfers copyright. A license (what most freelancers grant) allows the client to use the work but doesn't transfer ownership. If you sell an illustration to a company for their marketing materials, you can grant them an exclusive license for that specific use without giving up the copyright entirely.

Why Freelancers Should Read This Clause Carefully

Work-for-hire language in client contracts often goes further than the legal standard. Some contracts contain language like:

• "All work product, including deliverables and all intermediate versions, is work made for hire."
• "To the extent any work product does not qualify as work made for hire, Contractor hereby assigns all rights, title, and interest..."

That second sentence — the "to the extent" fallback — is actually an assignment clause. Even if the work doesn't legally qualify as work-for-hire, the assignment transfers the copyright anyway.

The practical result: the client ends up owning everything you create for them, including drafts, concept files, and unused versions. You may not be able to show it in your portfolio, use the underlying techniques in future client work (if they were specific to this engagement), or retain any rights at all.

This isn't inherently bad — it's sometimes appropriate and well-compensated. The problem is when freelancers sign it without realizing what they're agreeing to.

Red Flags in Client Contracts

Watch for these patterns:

"All intellectual property created in connection with this agreement..." — This is broader than deliverables. It can include process documents, research, tool configurations, and anything else you produced during the project.

"...is work made for hire, and to the extent it does not qualify, Contractor assigns..." — This is the double-lock. Work-for-hire if applicable; assignment if not. You lose the copyright either way.

No carve-out for pre-existing IP. If you use a proprietary workflow, template, component library, or framework you developed before this engagement, and the contract doesn't exclude it, you may be signing away ownership of work you built independently.

Broad licensing language with no scope limitation. Licensing that's "worldwide, perpetual, irrevocable, and exclusive" is effectively the same as an assignment.

How to Negotiate or Add Carve-Outs

You don't have to accept the contract as written. Here are practical options:

Option 1: Limit the scope of the IP transfer.

Option 2: Request a license instead of a transfer.

Option 3: Negotiate a higher rate for a full transfer.

If the client truly needs to own the copyright — not just license it — that's worth more than a standard project fee. Full IP transfers are commonly priced at a premium of 25–50% or more over the base project rate.

Option 4: Request a portfolio carve-out.

Even if you transfer the copyright, you can retain the right to show the work in your portfolio:

A Sample Work-for-Hire Clause

Here's an example of a balanced work-for-hire clause that protects both sides:

That clause is fair. The client gets ownership of the final product. You keep your pre-existing tools, methods, and the right to show your work.

Protecting Yourself Before You Sign

The best protection is a contract you wrote (or had reviewed), not one handed to you by the client. When you control the contract, you define what transfers, what doesn't, and what rights you retain.

Related reading: How to Ask for a Deposit as a Freelancer | 12 Client Red Flags Every Freelancer Should Know | How to Set Freelance Payment Terms