Freelancers: Who Owns the Work You Create?
You do, by default. Work made for hire is not automatic for an independent contractor: under 17 U.S.C. 101 it applies only to nine enumerated categories and only with a signed written agreement, and most software and design work falls outside them. Without a written assignment under 204(a), the copyright stays with you.
The biggest risks in a freelance contract are IP ownership and payment. A few clauses decide whether you keep your tools, your portfolio rights, and your fee.
Key takeaways
- "Work made for hire" is not automatic for freelancers under US copyright law, ownership transfers only with a written assignment.
- Watch for assignment language that sweeps in your pre-existing tools, templates, and unused concepts.
- Reserve the right to show finished work in your portfolio.
- Ownership should follow payment: you keep the rights until the client has paid in full.
Work-for-hire isn’t automatic
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.
Avoid misclassification traps
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.
Don't guess, check your actual contract
Upload your freelance contract and our AI will flag the risky clauses in plain English, tuned to your state, with a downloadable report and redline.
Frequently asked questions
Do I automatically own the work I create as a freelancer?
Yes, until you assign it. Under the US Copyright Act, work-for-hire is not automatic for independent contractors, so you own the copyright unless the contract contains a written assignment transferring it.
Should IP transfer before I am paid?
No. Tie the transfer of ownership to full payment, so the client only receives the rights once your invoice is settled. Otherwise you can hand over the work and still be chasing the money.
Can I show client work in my portfolio?
Only if the contract allows it. Broad assignment or confidentiality language can bar you from displaying your own work, so ask for an explicit portfolio-use carve-out before you sign.
Related Freelance guides
- Is My Freelance Contract Fair? A Pre-Signing Checklist for Independent WorkersClient contracts are written to protect the client. Here is the checklist our team runs on a freelance agreement before you sign, payment, ownership, scope, and the traps in between.
- What Is a Kill Fee, and Why Every Freelancer Needs OneA kill fee protects you when a client cancels a project partway through. Here is how kill fees work, what is reasonable, and how to get one into your contract.
- Payment "On Approval": The Freelance Clause That Holds Your Invoice HostageA clause that ties your payment to client "approval" or "satisfaction" sounds reasonable but can mean you never get paid. Here is how the trap works and how to fix it before you sign.
- Net 30 vs Net 60 vs Net 90: What Freelance Payment Terms Really Cost YouNet payment terms decide how long you wait for your money, and the difference between Net 30 and Net 90 can be enormous for your cash flow. Here is what each means and how to push back.
This guide is general information from ClauseAudit, not legal advice. Laws vary by state and change, consult a qualified attorney for your situation. Published 2026-05-01; last reviewed 2026-07-01.