Who actually owns your website?

Why does paying for a website not automatically mean you own it?

In most legal systems, the creator of an original work holds the copyright by default. When you hire a web designer, they are the creator. Unless the contract explicitly transfers that copyright to you, they retain it even after you have paid in full. You received a license to use the work, not ownership of it. The distinction feels academic until you try to move your site to a different host, hire a different developer, or sell your business, and suddenly the original designer controls assets you assumed were yours.

This is not unique to bad actors. Plenty of perfectly competent designers operate this way simply because they never thought to address it in a contract, or because it is standard practice in their market. The solution is not to assume the best. It is to read the contract carefully before signing and insist on an intellectual property assignment clause. If you are still evaluating designers and want to know which contract terms matter most, the guide on what a website contract should include covers every clause worth checking.

What does website ownership actually cover?

Ownership of a website is not a single thing. It breaks into at least four distinct assets, each of which requires separate attention.

1. The code and design files

This is the core of the intellectual property question. The HTML, CSS, JavaScript, and any custom templates or components are creative works. The design, meaning the visual layout, color choices, and interface decisions, is also a separate protectable work. A complete ownership transfer means both are assigned to you. Some contracts transfer the design visuals but only license the underlying code, which means you can use the site but cannot freely take the code elsewhere or build on it without permission.

2. Your domain name

Your domain is registered through a registrar and whoever controls that account is the effective owner. If a designer registered your domain for you and never transferred the registrar account to you, you do not have real ownership of it, even if you paid for the registration. The test is simple: can you log in to the registrar independently, change the DNS settings, and transfer the domain to another registrar without involving anyone else? If no, you do not fully own it yet.

3. Your hosting account and server files

If your site is hosted on a server or platform account the designer controls, and they go out of business, raise their prices, or simply become unresponsive, your live site is at their mercy. Full ownership means either having your own hosting account or having an unconditional right to receive all files and be assisted in moving them. A care plan from a reputable studio is different from a lock-in arrangement: you are choosing to pay for ongoing service, not being held hostage to it.

4. Your content

Text you wrote, photos you supplied, and your logo generally belong to you regardless of the contract. But if the designer or a copywriter created content as part of the project, that content has its own ownership question. Make sure the contract covers content deliverables alongside the design and code.

Does it matter whether my site was built on a platform or custom coded?

It matters a great deal, and this is one of the least discussed trade-offs when people compare a builder like Squarespace or Wix against a custom-built site.

When you use a hosted website builder, you own your content, which includes your text, images, and domain name if you purchased it separately. But the platform owns the infrastructure, the proprietary templates, and the underlying code that makes the site function. You cannot export the working site and independently host it elsewhere. If the platform changes its terms, raises its prices, or sunsets a feature you depend on, your options are limited to rebuilding from scratch on a different platform. You are renting the site, not owning it.

A custom-coded website is the opposite situation. All of the files exist independently of any platform, and if the contract includes a proper IP transfer, those files are yours to take anywhere. You can move hosts, hand the codebase to a different developer, or modify the design without asking anyone for permission. The same logic applies whether the build cost you $599 or $15,000. What matters is that the contract is clear.

What are the red flags that a designer is not giving you real ownership?

Most ownership problems are visible before a project starts if you know where to look. There are specific behaviors and contract patterns that consistently indicate a buyer will not have genuine control of their site after launch. The full list is covered in the guide on red flags when hiring a web designer, but the ownership-specific ones are:

• The designer registers your domain on their own account. This is the single most common ownership trap. Your domain should always be registered under your own email address in your own account at a registrar like Namecheap, Google Domains, or Cloudflare. If a designer offers to handle this for you, the answer should be that they walk you through registering it yourself.
• The contract says nothing about intellectual property. Silence on IP ownership is not neutrality. It defaults to the creator retaining the rights. No IP clause is a bad clause.
• The contract uses the word "license" where you expected "transfer" or "assign." A license lets you use the work. An assignment transfers the copyright to you. They are legally very different things.
• The site is built inside the designer's own agency hosting account. This is fine as a temporary arrangement during the build, but by launch you should be on your own hosting account or have a documented path to get there whenever you want.
• The proposal mentions a monthly fee required to keep the site live, but the contract does not describe what happens to the files if you stop paying. This is different from a voluntary care plan. If stopping a monthly payment means your site goes dark because the designer controls the server, that is a structural dependency, not a service relationship.
• The designer is vague or defensive when you ask about file delivery at the end of the project. A confident professional will tell you exactly what you will receive, in what format, and how it will be transferred. Evasiveness here is a serious signal.

What does a proper ownership transfer actually look like in practice?

When a project is done and ownership is handled correctly, the handover is specific and documented. Here is what it should include:

• A ZIP file or repository access containing all project files. HTML, CSS, JavaScript, image assets, fonts, and any other files the site depends on. You should be able to upload these to any web server and have the site work.
• Domain credentials or confirmation of your control. Either you registered the domain yourself, or the designer transfers it to your registrar account before the project closes.
• Hosting setup on your own account. Whether that is a standalone hosting account you own or a care plan you choose to sign up for, the distinction from a lock-in arrangement is that you can leave and take your files with you at any time.
• Third-party asset documentation. If the build includes licensed fonts, stock images, icon libraries, or plugins with their own licenses, you need to know what they are, what the license terms are, and whether you need your own paid license for any of them.
• A written confirmation in the contract that copyright is assigned to you upon final payment. Verbal agreements and handshakes are not enough. This needs to be in the document you both signed.

If you are working through the contract stage and want a checklist of everything the written agreement should cover beyond ownership, the guide on what a website contract should include goes through each clause in detail.

Which accounts should be in your name before any project starts?

Beyond the domain and hosting, there is a set of accounts that touch your website and should be yours from day one rather than being set up by the designer on your behalf.

The pattern is the same across all of them. The designer should be a collaborator with access you grant, not the primary account holder. When the project ends or you want to make a change, you should be able to do it without chasing anyone for credentials.

What if you already have a site and are not sure who owns it?

This situation is more common than most people expect. A business owner gets a site built, everything seems fine, and then a year later they try to make a change or move to a new designer and discover they do not have the credentials or the files.

Start by doing a practical audit. Can you log in to the domain registrar independently? Do you have access to the hosting account, or do you have to contact the original designer to make changes to the live site? Do you have a copy of all the project files? If the answers are no, you are not in full ownership regardless of what you paid.

In most cases the original designer will cooperate if you simply ask directly. Request the domain be transferred to an account in your name, ask for a full file export, and ask to be added as the primary owner on any accounts they created on your behalf. Put the transfer requests in writing by email so there is a record.

If the original designer is unresponsive or has gone out of business, a domain registrar dispute process exists for cases where the registrant contact information is yours but account access is blocked. The specifics depend on the registrar. For the hosting side, if you do not have the files, rebuilding is often the practical answer, which is also an opportunity to set things up correctly from the start. When comparing what a rebuild might cost, the website cost guide lays out realistic ranges for different project sizes.

How does FineWright handle ownership?

At FineWright, every build transfers full ownership of the code and design files to the client on final payment. The files are yours. The domain should be registered in your name before the project starts, and we walk you through that if needed. Hosting is either set up on your own account or through a FineWright care plan that you can cancel at any time and take your files from. There is no lock-in, no hostage hosting, and no fine print that retracts ownership if you stop a monthly subscription.

Care plans, starting at $49 per month, are a service you choose because it is convenient and good value, not a lever that controls your access to your own site. The full breakdown of what is included is on the FineWright pricing page.

Frequently asked questions

If I paid for my website, do I automatically own it?

Not automatically. In most countries, the person or company who created the work holds the copyright by default unless the contract explicitly transfers it to you. Paying a designer does not transfer ownership of the code or design unless there is a written agreement that says it does. Always get a contract that includes a clear IP assignment clause.

What is the difference between owning the design and owning the code?

The design, meaning the visual layout and creative elements, and the underlying code are technically separate works that can be owned by different parties. Some contracts transfer the design but license the code, meaning you can use it but cannot freely copy or modify it. You want both assigned to you in writing.

Who owns my domain name?

Whoever registered the domain and holds the registrar account credentials owns it in practice. If a designer registered your domain on your behalf and controls the account, you do not have full control even if you paid for it. Always register your own domain in your own name, or insist on being added as the registrant contact immediately.

What happens to my website if I stop paying a monthly fee to my designer?

This depends entirely on what the contract says and where the site is hosted. If your site is hosted on a platform or server the designer controls, and the contract does not require them to transfer files when you leave, you may lose access to the working site. If you own the files and they are hosted independently, stopping a care plan simply means you manage the site yourself going forward.

What should a contract say about website ownership?

A solid contract should include: a clear IP assignment transferring all original code and design to you on final payment, a statement that you own your domain and content from day one, terms covering what happens to files if the relationship ends, and whether any third-party licensed components are included in the build and what your rights are for those.

Does using a website builder like Squarespace or Wix mean I do not own my site?

Correct. When you build on a hosted platform like Squarespace, Wix, or Shopify, you own your content, such as text and images, but the platform owns the underlying code and infrastructure. You cannot export and independently host the working site. If the platform changes its pricing, discontinues a feature, or closes, your options are limited to rebuilding elsewhere from scratch.

Keep reading: what a website contract should include, red flags when hiring a web designer, and how much a website costs to build.