Who Owns My Website After a Developer Builds It?

You own your website only if your business controls each part of it: the domain registration, the hosting account, the admin logins, and a written agreement that transfers the copyright in the custom design and code to you. Paying the developer's final invoice does not, on its own, hand any of that over. The cheapest time to settle who owns your website after a developer builds it is before work starts, and the second cheapest is at handover.

Most owners find out where they stand at a bad moment: the developer stops replying, a renewal notice goes to someone else's inbox, or a buyer asks for proof of ownership during a sale. Here is what owning a website means in practice, what your contract should say, and what to collect before you pay the balance.

Who owns my website after a developer builds it? Start with the parts

In practice a website is six or seven separate assets, each with its own owner and its own way of going wrong.

Part	Who should control it	How to check in five minutes
Domain name	Your business, as registrant, in your registrar account	Log in to the registrar yourself and check the registrant name and renewal card
Hosting or server	Your account and payment card, or a documented agency arrangement with an exit plan	Log in to the hosting panel and check who is billed
CMS admin	An administrator account in your name, with your email	Log in and check your role under users
Custom code and design	You, through a written copyright assignment or a clear licence	Read the contract's intellectual property clause
Content and images	You, with licences for any stock or third-party assets	Ask for a list of image sources and licence terms
Themes, plugins, fonts	Licences transferred to you, or listed with renewal dates	Ask for a written licence register
Surrounding accounts	Your business as owner: email, analytics, Search Console, Google Business Profile	Check each one lists your business as owner or administrator

If any row points to your developer, you are renting that part of your website.

Does paying the developer mean I own the website?

Not automatically. In many countries, copyright belongs to whoever creates the work, and paying for the work doesn't change that unless a written agreement says otherwise. Prominent Web's guide to website ownership puts it simply: payment for time or labour does not transfer copyright, and if the contract says nothing about ownership, the developer keeps the rights.

The detail varies by country. The UK, Pakistan and Saudi Arabia each have their own copyright legislation, and what counts as a valid transfer, and whether employees and contractors are treated differently, is not identical between them. If the site is a significant asset, or your developer is in another country, ask a lawyer in your jurisdiction to check the intellectual property clause before you sign.

Assignment or licence: which do you need?

Two set-ups are reasonable:

Assignment. The developer transfers copyright in the bespoke design and code to you, usually once the final payment clears. This is the cleanest option for a custom website or web app you intend to keep for years.
Licence. The developer keeps copyright but grants you a permanent, transferable right to use, modify and move the site. This is common when an agency reuses its own components across many clients.

Either can work, provided the licence is permanent, survives the end of the relationship and lets another developer work on the code. A licence that ends when you stop paying for hosting is a lock-in.

It is also normal that some parts can't be assigned to you at all. As Orbit Media's website ownership guide notes, you will never own the CMS platform, database software or programming language your site runs on; you use them under their own licences. That is fine, provided those licences are open source or transferable to you.

Who owns the domain name?

Strictly, nobody owns a domain outright: the registrant holds the exclusive right to use it while it is renewed. The registrant should be your business, the registrar account should use an email address your business controls, and auto-renew should be switched on with a company card.

If you want to move a generic domain such as a .com to another registrar, you need its transfer code (sometimes called the EPP or auth code). Pixel2Tech's ownership checklist notes that ICANN requires registrars to give the domain holder that code within five calendar days of a request. Country-code domains such as .uk, .pk and .sa are run by their own registries, each with its own transfer process, so check the rules for yours.

Disputes over domains held back as leverage tend to go the business's way. In Bill Hartzer's review of domain hostage cases, published UDRP decisions consistently treat a developer keeping a client's domain over an unpaid invoice as bad-faith use, and order it returned. The unpaid invoice is a separate debt question. Even so, registering the domain in your own name from day one avoids the dispute entirely.

Who owns the hosting and the code running on it?

Hosting is where the files, database and backups live. Two options make sense:

Hosting in your own account. You hold the contract and the card, and give your developer a user account. If you part ways, you remove their access.
Agency-managed hosting. Perfectly reasonable, but the contract should say how and when you get a full copy of the files and database if you leave.

For custom websites and web apps, ask for the source code, not just a working copy. Some technologies compile code before it runs, which means a working site can still be almost impossible to change without the original source. Webbed Feet describes a business whose developer died with the source code for a critical system on an encrypted drive, leaving only compiled code and a costly reverse-engineering job. The fix is simple: keep the source code in a version control repository, such as GitHub or GitLab, under an organisation account your business owns, and give developers access to it rather than the other way round.

If you are moving an existing site out of a developer's account, our hosting and cloud migration service covers that kind of move.

What about content, photos and licences?

Text your staff write is yours; text an agency writes should be covered by the same assignment as the code. Stock photos are licensed, not owned, and the licence is often tied to the account that bought them, so ask for a list of image sources and licence terms.

Premium themes, plugins and fonts work the same way. If they were bought on the developer's account, the licence may lapse and security updates stop. Ask for them to be transferred to you, or listed with renewal dates so you can buy your own.

What should a web development contract say about ownership?

Before you sign, check that the contract covers these points in plain language:

The domain is registered to your business, and the developer has access only to do the work.
Copyright in bespoke design, code and written content passes to you on final payment, or you receive a permanent, transferable licence.
The developer can reuse its own generic tools and libraries, but you get a licence to them as used in your site.
Source code is kept in a repository your business owns, or delivered in full at handover.
Third-party licences are listed, with who pays for renewals.
On termination, the developer hands over all files, databases, credentials and documentation within a stated number of days.

A developer who is confident in their work will rarely object to any of this.

What should I receive at handover?

Treat this as a checklist before you transfer the final payment:

Registrar login, with you shown as registrant, plus DNS access.
Hosting control panel login, or a documented copy of files and database.
Administrator access to the CMS under your own email.
Source code repository access, or a full code archive.
Owner or administrator access to analytics, Search Console, Google Business Profile and any ad accounts.
A licence register for themes, plugins, fonts and images.
Notes on how the site is deployed and where backups are stored.
A recorded walkthrough showing your team how to edit pages, add posts or products, and check form submissions.

Then test it: log in to every account yourself, submit the contact form, and confirm you can restore a backup. If you want help with that last step, our cybersecurity and backups service covers backup testing and recovery.

What if my developer won't hand over my website?

Work in this order:

Find out what you already control. Check your domain's public registration details and any accounts you can still access.
Read your contract and gather your records. Invoices, payment receipts and emails about ownership all matter.
Make a clear written request listing exactly what you need and a reasonable deadline. Keep it factual.
Contact your registrar if the domain is affected. Registrars have account recovery and dispute processes.
Take legal advice if the asset is valuable and the developer won't co-operate.

Once you have control back, put the site on a footing that doesn't depend on any single person. A managed maintenance plan with documented access is one way to do that.

Frequently asked questions

Can my web developer legally keep my website if I've paid in full?

They may still hold copyright in the code if your contract doesn't transfer it, and that can limit what you do with it. Rules differ between the UK, Pakistan, Saudi Arabia and elsewhere, so check your contract and take local legal advice if the stakes are high.

Is it a red flag if an agency wants to host my website?

No. Agency hosting is common and often well managed. It becomes a red flag only if the contract doesn't explain how you get a complete copy of your site, data and domain control if you leave.

Do I need the source code if I can already edit the site in the CMS?

For a standard CMS site, admin access and a full backup may be enough. For a custom website or web app, yes: without it, another developer may not be able to fix or extend it.

If you're planning a new site and want ownership, access and editing settled from the first conversation, talk to us about web development. We build fast websites and web apps that your team can update without calling a developer.