Here’s something that trips up freelancers, side-hustlers, and even professional web developers constantly: just because someone pays you to build something doesn’t mean they own it.
Under U.S. copyright law, copyright ownership automatically goes to the creator — the person who actually made the thing. So if you design and build a website for a client, you’re the creator. Which means, by default, you hold the copyright. Not the person who hired you. Not the person who paid you. You.
The exception to this is something called the “work-for-hire” doctrine. If a valid work-for-hire agreement is in place, it can shift copyright ownership to the client or employer instead. But here’s the catch — that agreement has to exist. In writing. A handshake doesn’t count. A Venmo payment doesn’t count. Even a text saying “yeah go ahead and build it” doesn’t count.
Important nuance: under U.S. copyright law, “work for hire” works differently depending on whether you’re an employee or an independent contractor. If you’re a freelancer (i.e., not a full-time employee), a written work-for-hire clause alone may not be enough to transfer ownership — because the law only recognizes work-for-hire for independent contractors in a specific, limited list of work categories, and general website design and code are not clearly on that list. This means that even if your contract says “work for hire,” a court might not honor it for freelance web projects. The more reliable approach for freelancers and clients is a written copyright assignment — language in the contract that explicitly transfers copyright from the creator to the client. Talk to a lawyer about which approach is right for your situation.
No written agreement addressing copyright? The creator very likely keeps the copyright. Full stop.
This matters in a really practical way. Say you built a small business website for your neighbor’s restaurant last summer. They paid you $500. You two had a casual verbal agreement and called it a day. Legally, you likely still own the copyright to that website’s design and code. They paid for your time — but not necessarily for the rights to the work itself.
Now, does this mean you should go demand money from your neighbor? Probably not. But it does mean that if you’re doing any kind of freelance web work, you and your client need to get crystal clear on who owns what — before the work starts. A written contract that specifically addresses copyright ownership protects both of you. The client knows they actually own what they’re paying for. You know exactly what rights you’re handing over.
And if you’re the client — someone paying a developer to build your website — don’t assume you own it just because you wrote the check. The standard rule gives copyright to the creator, and transferring that ownership is the exception, not the default. Get it in writing — and make sure the language actually holds up legally.