Freelancers: Who Owns the Work You Create?

Is freelance work automatically work made for hire?

Start from the default: under US copyright law, the person who creates a work owns it. For employees, work created within the job belongs to the employer automatically. For freelancers, it does not. A client commissioning work from an independent contractor gets "work made for hire" status only if two things are both true: the work falls into one of nine specific statutory categories (things like contributions to collective works, parts of audiovisual works, translations, compilations), and there is a written agreement signed by both sides saying it is work for hire.

Plenty of common freelance work, a logo, a website, a standalone software application, does not fit those categories at all. That is why well-drafted contracts add a backup assignment clause: "to the extent this is not work made for hire, Contractor hereby assigns…" If a client’s contract is silent on IP, the surprising default is that you still own the copyright and the client has, at most, an implied license to use what they paid for. That ambiguity is bad for both sides, which is your opening to negotiate terms you can live with.

Watch what gets assigned

The danger is scope. An overbroad assignment can sweep in your pre-existing code libraries, design components, templates, and process documents, the reusable toolkit your business runs on, plus every rough concept you sketched and the client rejected. Sign that, and delivering one project quietly transfers assets you built over years.

The clean structure: list your pre-existing materials (often in an exhibit), state that you retain ownership of them, and grant the client a perpetual, non-exclusive license to use them only as embedded in the deliverables. The final deliverables themselves transfer to the client. Unused concepts and drafts stay yours. And make the transfer conditional: ownership passes on payment in full. That single phrase converts an unpaid invoice from a collections problem into a copyright problem for the client, which gets invoices paid remarkably fast.

Protect your portfolio rights

Once you assign the work, showing it off is no longer automatically your right, it is the client’s copyright now. Many contracts are silent on portfolio use, and silence functionally means "ask permission later," from a client who may have been acquired, gone quiet, or changed marketing leads twice.

Add one sentence while you have leverage: "Contractor may display the deliverables in Contractor’s portfolio and identify Client as a client, subject to any written confidentiality restrictions." Clients rarely object when asked before signing; the same request after delivery is a favor. If the project is genuinely confidential, negotiate a delay (for example, portfolio rights after public launch) rather than giving the right up entirely.

Get paid: deposit, kill fee, prompt-pay laws

Three payment terms do most of the protective work. A deposit, 25–50% up front, filters out clients who were never going to pay and funds the early work. A kill fee ensures a canceled project still pays for what you did: keep the deposit plus payment for work completed to the cancellation date. And tie payment to delivery, not to subjective "approval" or "satisfaction," which lets a client withhold payment indefinitely by staying unsatisfied. If the client wants an acceptance process, define it: a fixed review window, written revision requests, and deliverables deemed accepted if no response comes within, say, 10 business days.

The law is also catching up. New York’s Freelance Isn’t Free Act (statewide since 2024) and Illinois’s Freelance Worker Protection Act require written contracts and payment within 30 days of the work, with damages for violations; California added its own version, and several cities have local rules. If your client is in one of those places, a late payment is not just annoying, it is a statutory violation with penalties attached, and saying so tends to move your invoice to the top of the pile.

Work made for hire: the narrow exception

For independent contractors, work is only "made for hire" if it falls into one of nine statutory categories, such as a contribution to a collective work or part of an audiovisual work, and both parties sign a written agreement saying so. Most websites, logos, software and designs do not fit these categories. That is why client contracts usually add an assignment clause as a backup, and why that assignment clause is the one to read closely.

What does federal copyright law say about who owns freelance work?

The ownership rules come from the Copyright Act, Title 17 of the US Code. Under 17 U.S.C. § 201(a), copyright belongs initially to the author of a work, and under § 201(b) the hiring party is treated as the author only when the work is a work made for hire as defined in 17 U.S.C. § 101. Whether you count as an employee for that purpose is decided by general agency law, not by the label in your contract.

The Supreme Court set out that approach in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989). A charity hired a sculptor to make a statue and gave enough direction to make sure it met its specifications. But the sculptor was a skilled professional who used his own tools, worked in his own studio without daily supervision, was hired for a short project, and received no benefits or payroll tax treatment. The Court held he was an independent contractor, and because there was no signed work-for-hire agreement, he kept the copyright. The same factors, such as control over how the work is done, who supplies the tools and how you are paid, are the ones a court would weigh for a freelancer today.

Outside the work-for-hire route, ownership only moves by assignment, and 17 U.S.C. § 204(a) says a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights. A verbal promise to hand over the files is not an assignment. That is why a client who wants ownership needs your signature on a written document, and why the timing words in that document matter so much.

The two routes also differ decades later. Under 17 U.S.C. § 203, an author who assigns or licenses a copyright on or after January 1, 1978 can terminate that grant during a five-year window that generally opens 35 years after the grant, by serving written notice two to ten years in advance. Works made for hire are excluded from this right. So the wording the contract uses can affect what you own long after the project is delivered, not just on the day you are paid.

Tie ownership to payment

The most important protection is making ownership transfer only when you are paid in full. If rights transfer on creation, the client can use the work while your invoice remains unpaid, and you lose your strongest lever. See our guide on clients who want rights before paying.

How do you keep your pre-existing tools out of the assignment?

Assignment clauses often cover "all materials used in the services," which can sweep in your templates, code libraries and design systems. Carve out background IP and grant the client a non-exclusive licence to use it as part of the deliverables. Our guide on protecting your source code and tools has sample wording.

Portfolio rights and moral rights

If you want to show the work, ask for a portfolio right after publication. In the US, moral rights such as attribution apply only to limited categories of visual art, so credit generally depends on the contract.

A worked example

Leo designs a brand identity for $6,000. The contract assigns all rights on creation and includes his font pairings and icon set. The client pays half, launches the brand and disputes the rest. Because rights passed on creation and his icon set was included, Leo has only a contract claim. With ownership on payment and his icon set licensed rather than assigned, he could also have required the client to stop using unpaid work.

Sample wording to ask for

"Upon receipt of full payment, Contractor assigns to Client all rights in the final Deliverables. Contractor retains ownership of its pre-existing materials and grants Client a non-exclusive, perpetual licence to use them as incorporated in the Deliverables. Contractor may display the Deliverables in its portfolio after public release."

Quick checklist

• Does ownership transfer on payment, not creation?
• Is work-for-hire wording used, and is there a backup assignment?
• Are your pre-existing materials carved out?
• Do you keep portfolio rights?
• Does the assignment cover only final deliverables, not drafts and unused concepts?

Which contract terms create misclassification risk?

Contract terms that make you look like an employee create risk for both sides. If a client sets your working hours, demands exclusivity, requires you to work on their equipment at their office, and directs how (not just what) you deliver, the IRS and state agencies may see an employee regardless of the "independent contractor" label, with back taxes and penalties mostly landing on the client, and your own tax treatment thrown into question.

Keep the contract consistent with genuine independence: you control your methods, schedule, and tools; you can take other clients; you are paid by project or invoice rather than a salary-like wage. This is not just legal hygiene. The same facts that support contractor status, control over how you work, are the facts that support you owning your process, your tools, and your business.