Who owns the copyright in freelance work?
A client commissions a logo, pays the invoice, and puts the logo on everything. Two years later the client wants to license the mark, sell the company, or stop the freelancer from reusing the design for someone else, and discovers a fact that changes the negotiation entirely: the freelancer still owns the copyright.
This is not an edge case. It is the default outcome under U.S. copyright law, and it survives payment, an invoice marked paid in full, delivery of source files, and a great many contract clauses drafted to prevent exactly this result.
Who owns freelance work by default?
The freelancer. Copyright vests in the author at the moment a work is fixed in tangible form, and an independent contractor is the author of their own work. Ownership moves to the client only through a written assignment or through the work-made-for-hire path, which is narrow.
The rule follows from the structure of the statute rather than from any policy favoring creators. Copyright begins with the person who created the expression. Everything else is a transfer, and transfers of copyright ownership generally require a writing signed by the party conveying the rights.
That writing requirement is the mechanism that defeats most informal arrangements. Emails agreeing on scope and price, purchase orders, and invoices are not assignments. They document a transaction without moving the copyright.
Does the work-for-hire clause in the contract fix it?
Usually not, for commissioned work. Section 101 makes a commissioned work a work made for hire only if it falls within one of nine listed categories and the parties signed a written agreement saying so. The agreement alone is insufficient if the work is outside those categories.
Most freelance deliverables sit outside them. A logo, a standalone photograph, a website, a standalone software module, and an individually commissioned blog post fit none of the nine. For those, the work-for-hire clause is inert, and if the contract contains no separate assignment language, the copyright remains with the creator.
Courts have also rejected retroactive designation. Applying work-for-hire status after a work is complete does not shift ownership, which defeats the common practice of resolving IP terms at the end of an engagement. Work made for hire covers the two statutory paths and the nine categories in full.
Are you actually a contractor?
Not necessarily, and the label in the agreement does not decide it. In Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), the Supreme Court held that employee under section 101 carries its common-law agency meaning, so courts examine the real working relationship.
This cuts both directions. A freelancer treated in practice like an employee, working set hours with the client's equipment on the client's premises under close direction of the manner and means of the work, receiving benefits and W-2 treatment, may be an employee for copyright purposes. Work prepared within the scope of that relationship would be a work made for hire under the first prong, and the client would own it from creation.
Conversely, someone the client calls an employee but who works independently, supplies their own tools, sets their own hours, takes work from multiple clients, and is paid as a contractor may not be one. The factors courts weigh include control over the manner and means of creation, skill required, source of tools, work location, duration of the relationship, whether additional projects can be assigned, control over hours, method of payment, role in hiring assistants, whether the work is part of the hiring party's regular business, provision of benefits, and tax treatment.
What is an implied license and what does it cover?
Where a client commissions work and the freelancer delivers it without a written agreement, courts commonly find the client received an implied license to use the work for the purpose it was created for. The scope is uncertain, generally nonexclusive, and considerably narrower than ownership.
| Ownership | Implied license | |
|---|---|---|
| Who holds the copyright | The client | The freelancer |
| Scope of use | Unlimited | Roughly the purpose the work was commissioned for |
| Exclusivity | Exclusive | Generally nonexclusive |
| Right to modify or make derivatives | Yes | Uncertain, often disputed |
| Right to sublicense or transfer | Yes | Generally no |
| Freelancer's right to reuse the work | None | Retained |
The practical gaps show up at predictable moments. Expanding the use beyond the original purpose. Modifying the work or building derivatives from it. Transferring the asset in a sale of the business, where acquirers conduct diligence and find no chain of title. Trying to stop the freelancer from using the same work elsewhere. An implied license answers none of these cleanly.
What if there is no written agreement at all?
The freelancer owns the copyright and the client holds whatever implied license the circumstances support. Neither party is in a comfortable position, which is usually enough to motivate a retroactive fix.
A retroactive assignment works where retroactive work-for-hire designation does not. Assignment is a transfer of an existing right, and an owner can transfer at any time. So the repair is available: a written, signed assignment executed now, conveying all right, title, and interest in the previously delivered work.
Both sides usually have reasons to sign. The client needs clean title. The freelancer often wants continued goodwill, sometimes negotiates a portfolio-use carve-out, and occasionally negotiates additional payment. That negotiation happens on very different terms than it would have at the outset, which is the cost of leaving it unresolved.
Practical steps for freelancers
Know what you hold. Absent a valid assignment or a qualifying work-for-hire arrangement, you own the copyright in what you made, and that ownership is an asset in any later negotiation.
Read the IP clause before the payment terms. A clause that assigns all right, title, and interest transfers ownership, whatever else the contract says about work made for hire. A clause that only recites work-for-hire language may transfer nothing if the deliverable is outside the nine categories.
Negotiate the carve-outs you need. Portfolio display, reuse of underlying tools and components, and retention of preexisting material you brought to the project are all ordinary requests, and they are far easier to secure before signing.
Practical steps for clients
Use assignment language alongside work-for-hire language. Draft in the alternative: the work is a work made for hire to the extent it qualifies, and to the extent it does not, the creator assigns all right, title, and interest.
Get the signature before work begins, and get it from the individual creator. An agreement with an agency does not automatically bind the subcontractor who actually made the work, and chain-of-title gaps at that layer are common.
Audit before you need to. Ownership problems surface during acquisitions, financings, and enforcement, which are the three worst moments to discover them.
For the mechanics of transferring rights, see copyright assignment versus license. If the question is whether someone else's work can be used rather than who owns yours, start with fair use explained. Recording the claim is a separate step from owning it, set out in how to register a copyright, and work produced by a generative tool raises a prior authorship question covered in who owns AI-generated content.
The U.S. Copyright Office covers ownership and transfers in Circular 1 at copyright.gov, and the statutory text is at 17 U.S.C. sections 101 and 201.
This article explains general legal principles and is not legal advice. Ownership turns on specific facts and contract language. Consult an attorney about your agreements.