Who Owns Website Source Code? Copyright, Design and Domain Explained

We are Talha Aslan and team, and this question comes up in almost every redesign we see. In this guide we split a website into its parts: design, code, content, images, domain name and hosting account. Each part follows different rules. We also give you a contract checklist and a handover list.

Note: This article is general information, not legal advice. Talk to a qualified attorney about your own contract.

Why does "I paid for it, so I own it" fail so often?

Because payment and ownership are two separate things, the invoice alone settles nothing. An invoice proves that you bought a service. However, it does not prove that the copyright moved to you. Under US law, a transfer of copyright ownership generally has to be in writing and signed by the owner.

Here is an example scenario. A company pays a freelancer to build its site and uses it for years. Then it hires a new team for a redesign. The original developer says the code is still theirs and refuses to allow changes. If the company only holds invoices, its position is weak.

In short, the goal is simple. Put the ownership of every part in writing before work starts. The legal language can look complex. Still, the logic is easy: a right that nobody wrote down usually stays with the creator.

What does "work made for hire" mean for a website?

The US Copyright Office explains the rule in its circular on works made for hire. According to the circular, a work made for hire exists in two situations. First, an employee creates it within the scope of employment. Second, someone specially orders or commissions it, and it fits one of nine listed categories.

For commissioned work, therefore, all four conditions must hold. The work fits a listed category. There is a written agreement. The agreement expressly says it is a work made for hire. Finally, all parties sign it. If any condition fails, it is not a work made for hire.

The nine categories include contributions to collective works, parts of audiovisual works, translations, compilations and a few others. Custom website code does not clearly fit any of them. As a result, a "work made for hire" label alone may not protect you when an outside agency builds your site.

Who owns website source code: your employee or an outside agency?

It depends on the relationship, and the difference matters a lot. When your own employee writes code as part of the job, the work made for hire rule usually makes your company the author. That is the first category in the Copyright Office circular.

On the other hand, an outside agency or freelancer is usually not your employee. The circular notes that courts look at factors such as who controls the work, who provides the tools, how the creator gets paid and whether they run their own business. Most agencies clearly run their own business.

That is why agency contracts need a written assignment clause. Also, remember that agencies often use subcontractors. The agency can only assign rights it actually holds. So ask for a clause in which the agency confirms that it secured all rights from its subcontractors.

Who owns each part of a website?

In practice, a website is not one single work. It is a stack of parts, and each part has its own ownership logic. The table below compares the typical default with the setup you should aim for. It shows general patterns, and your contract decides the final answer.

Should you take an assignment or a license for custom code?

Both options are legitimate, so the choice comes down to your plans. The key is to know which one you are getting. With an assignment, the copyright moves to you, and you can hire anyone to extend the code. With a license, the developer keeps the copyright, and you use the code within the agreed scope.

In addition, most agencies reuse their own internal libraries across projects. They cannot hand those over completely, because they need them for other clients. A fair solution looks like this: the project specific code transfers to you, and the shared pieces come with a perpetual, irrevocable license.

If you accept a license, answer these questions in the contract:

• Is the license perpetual or limited in time?
• Can another team modify and extend the code?
• Does the license survive the end of the contract?
• Is it exclusive, or can the developer license the same work to others?

How do WordPress, themes and plugins affect ownership?

On an open source platform like WordPress, nobody owns the core code in the usual sense. WordPress uses the GPL, as its official license page explains. Anyone may use, modify and share it under the license terms.

However, premium themes and plugins work a little differently. The code license and the right to updates and support often sit in separate accounts. If the agency bought the license under its own account, you may lose updates when you part ways. Therefore ask for premium licenses in an account that uses your company email address.

If you are still choosing a platform, our comparison of WordPress vs a custom website covers the tradeoffs. In practice, the parts you can own on WordPress are your custom theme code, your content and your database.

Who keeps the design files and original graphics?

Like code, interface designs, icons and custom illustrations are creative works of the designer. Without an assignment, you mainly get to use the final result on your site. Your right to the editable source files may stay unclear. So list the source files as a separate deliverable.

Stock photos, however, never become yours. You only get a license, and that license can limit how you use the image. For example, print or advertising use may follow different terms. At handover, ask for the license documents and a simple list that shows which image uses which license.

Fonts also come with licenses. We covered the privacy side of self-hosted fonts in our guide to Google Fonts, GDPR and self-hosting. On the ownership side, add the font license terms to your handover documents.

Who owns the written content, product copy and blog posts?

If your own team wrote the content, the answer is easy. Those rights are already yours as employer work. However, if the agency also wrote copy for you, that copy is a creative work too. You need it in the written assignment.

Still, many companies skip this part, because text feels less important than code. Yet over the years you build up hundreds of product descriptions and articles. That content supports your search visibility. So add a clause such as "all delivered copy transfers to the client upon payment" to content contracts as well.

Ownership of AI assisted text can also be unclear, and the rules keep evolving. We do not give a firm rule here. Instead, ask the agency which tools it uses and check the provider's terms of use. That is a sensible first step.

Is the domain name or hosting account part of copyright?

No. In fact, domains and hosting are service and registration relationships, not copyright. Specifically, a domain belongs to the registrant listed with the registrar. A hosting account belongs to whoever opened it. So even if you own the code, a domain registered to the agency can make a move difficult.

Follow these steps from day one:

1. Register the domain in your company name with a company email address.
2. Keep the registrar login yourself.
3. Open hosting in your company name, or get full admin access if the agency hosts it.
4. Make sure renewal notices and invoices reach you.

If those steps never happened, our guide on how to take back your website and domain from an agency walks you through recovery. Also remember that company email often depends on the same domain.

Who owns website source code in your project, and how do you settle it early?

The best moment is the proposal stage, because that is when you still have the most leverage. When you compare proposals, look past the price and ask about the ownership model. Will the code transfer to you, or will you get a license? That answer often explains the real gap between two quotes. Also ask whether the transfer is part of the fee.

If you want a team that plans ownership, platform and handover terms with you from the start, our web design services page explains how we work. The technical handover list is the part most owners struggle to check alone. Meanwhile, your attorney should always review the legal wording.

Next, ask two more questions in the first call. Will subcontractors work on the project? Which paid licenses will sit in whose account? A vague answer is an early warning sign. On the other hand, a good team explains its ownership model without being asked.

Which ownership clauses belong in a web design contract?

We cover the full contract structure in our guide on what to include in a web design contract. Here we list only the clauses that deal with copyright and ownership:

• A clear assignment of copyright in the custom code, design and copy.
• The scope of the transfer, such as worldwide and perpetual.
• The moment rights transfer, for example on final payment.
• A separate perpetual, irrevocable license for shared libraries.
• The list of third party themes, plugins, fonts and images with their licenses.
• A promise that the agency secured rights from its subcontractors.
• The format of the code and design file delivery.
• Limits on how the agency may show the site in its portfolio.

This list is a starting point. For example, a membership system or a custom integration may need its own clause. Your attorney can adapt the list to your project.

When should the transfer of rights happen?

In practice, many contracts use two steps. First, the main agreement states that rights will transfer and under which conditions. Then, at delivery and final payment, both sides sign a short handover and assignment document.

We recommend this approach to our clients because it creates a clear record. The handover document lists the exact version, the files and the rights that moved. It also shows which delivery the final payment covers. As a result, nobody has to guess later which code changed hands.

Whether this structure works for you depends on the whole contract. Still, it gives a concrete answer to the question "what exactly did we receive?" and that alone prevents many disputes. Keep a signed copy in a place your whole team can find.

Which files and access should you request at handover?

However, ownership on paper means little if the files are not in your hands. These are the items that matter most for ownership:

1. The complete source code, ideally with access to the version control repository.
2. A database backup and setup notes.
3. Editable design source files.
4. License keys and account details for premium themes, plugins and fonts.
5. License documents for images.
6. Admin access for the domain, hosting and email.
7. The signed handover and assignment document.

Also ask for social sharing images, logo variants and favicon files. These often come from a separate design task. For example, when a shared link shows no image, the cause is usually the Open Graph tags; our guide on a link preview image not showing explains that fix.

Why does the version control repository matter for ownership?

Put simply, a version control repository stores every change to the code along with its history. Git based repositories are the most common example. If the repository sits in the agency's personal account, you only get a copy of the latest state. You cannot see who changed what, or when.

That history also helps with ownership questions. For instance, you can tell which parts the team wrote for your project and which parts came from shared libraries. In addition, a new team understands the code much faster with the full history.

Add these three points to your contract or handover list:

• Create the repository under your company account, or transfer it to you at handover.
• Give the agency contributor access during the project, and keep owner rights yourself.
• Record the tag and date of the final release in the handover document.

Do your rights change when a maintenance contract ends?

They should not, but that depends on the contract language. For example, some agreements tie the license to the maintenance plan. When maintenance ends, the right to use the code ends too. That setup can trap you when you want to switch teams.

So we suggest keeping two separate agreements. The development agreement handles the assignment or the perpetual license. The maintenance agreement covers only time based services such as updates, backups and support. That way, ending maintenance does not touch your right to run the site.

Also, new features that the agency builds during maintenance are creative works too. The same transfer logic should apply to them. In short, consider a clause like "code developed under maintenance transfers to the client on the same terms."

When you finally switch teams, this clause decides how smooth the move will be. Ask for the latest backup and a current access list in writing before maintenance ends.

Can the agency show your site in its portfolio?

Even after a full assignment, agencies usually want to show their work. That request is reasonable. Still, you should define its limits in the contract. Otherwise, an admin screen or an unreleased product might appear in a sales deck.

You can add details like these:

• The agency may use screenshots of public pages only.
• Admin panels, customer data and internal workflows stay private.
• Use of your logo stays limited to a client list.
• You can withdraw permission with written notice.

Also, this clause does not change ownership. It only grants a narrow promotional permission. Therefore it fits next to the assignment clause without any conflict.

Does ownership work differently with a freelancer?

The basic rule stays the same, because the law looks at authorship, not job titles. A freelancer is the author, and the rights stay with them until a signed transfer. However, freelance deals often live in a short email thread. That makes ownership far less clear than in an agency project.

So prepare a short written agreement, even for a small job. State the scope, the deliverables, the rights that transfer and the payment schedule. Also ask whether the freelancer used anyone else's code, and get the answer in writing.

Freelancers may also want to keep their reusable components. That follows the same logic as with agencies, and a perpetual license usually solves it. We compare the two models in more depth in our guide on web design agency vs freelancer.

In other words, the title of the person you hire does not decide ownership. The signed document does.

Who owns website source code if the agency refuses to hand it over?

First, start with your contract, because it decides who owns website source code in a dispute. If it includes an assignment, send a written request that lists every file you need. Keep your payment records and emails together. They matter if the dispute ever needs legal help.

If the contract has no assignment, the situation is harder. Still, many cases end with a negotiation. The developer may agree to an assignment or a broad license for a reasonable fee. On the other hand, copying code without permission or accessing a server without authorization creates legal risk. We never recommend those routes.

Instead, keep the tone calm and specific. Explain which files you need and why. That usually gets a faster answer. Before you take any formal step, talk to an attorney.

Which ownership mistakes should you avoid?

The mistakes we see in the field tend to repeat, so a short checklist goes a long way. Here is a short list:

• Reading the contract only for price and timeline.
• Relying on one vague line such as "all rights belong to the client."
• Registering the domain in the agency's name.
• Leaving premium licenses in the agency's account.
• Making the final payment before signing a handover document.
• Keeping backups only on the agency's server.

Most of these take five minutes to prevent at the start. So bring this list to your first proposal call.

Should you check ownership yourself or get professional help?

For a simple brochure site, you can run this checklist yourself. However, ecommerce, membership areas and custom integrations grow the handover list fast. Someone who can read the code needs to confirm that the files are complete.

In our projects, we put the ownership model in writing at the proposal stage. At handover, we deliver files, licenses and access as one package. If you want business website design built on that kind of transparency, you can reach us there. For the legal text itself, always work with your own attorney.

To sum up, a website is a set of parts with separate ownership rules. Aim for a written assignment or a clear license for code and design, company registration for domain and hosting, and licenses in your name for third party products. Then collect every file and the signed handover document. That way, the question of who owns website source code never surprises you during a redesign, and your next team can start work on day one. This article is not legal advice.