Who actually owns your website? (It might not be you)

You paid for your website. You signed off the design, you sent over the photos, you wrote (or at least approved) every word on it.

So it’s yours, right?

Not necessarily. And it’s the sort of thing most business owners only find out when they’re trying to leave a developer, which is about the worst possible time to discover it.

Paying for it isn’t the same as owning it

Here’s the bit that surprises people. Under UK copyright law, when you commission someone to create something, the copyright belongs to whoever made it, not whoever paid for it. That applies to designers, photographers, copywriters and, yes, web developers.

The only way that changes is if there’s a written agreement transferring ownership to you. GOV.UK’s guidance on copyright ownership is pretty clear on this: if you commission a work, the person who created it is the first owner unless you agree otherwise in writing.

In practice, you’ll almost certainly have some kind of implied right to use the website you paid for. But “implied” is doing a lot of heavy lifting there. Can you take the design to another developer? Can they change it? Can you reuse the code on a second site? Without a clear agreement, those questions get murky quickly.

Most developers will never make an issue of it. But “most” isn’t a great thing to build your business on.

The three things to check in your contract

Dig out whatever you signed when your site was built. Terms and conditions, a proposal you said yes to, an email chain that ended in “sounds great, let’s go”. Then look for these three things.

1. Who owns the copyright

You’re looking for a clause that transfers ownership of the design, code and content to you. Usually it’ll say something like “on payment of the final invoice”, which is fair enough. Nobody should be handing over the keys before the bill’s paid.

If there’s no mention of ownership at all, assume it hasn’t been transferred. No clause, no transfer.

One thing that’s always yours, regardless: the content you supplied. Your words, your photos, your logo. Those were yours before the developer got involved, and they stay yours.

2. Who holds the licences

This is the one almost nobody thinks about.

Most websites rely on bits and pieces the developer didn’t build from scratch: premium WordPress themes and plugins, paid fonts, stock photos. These all come with licences, and those licences are very often registered to the developer’s account, not yours.

That’s not dodgy in itself. Developers buy these in bulk and it’s cheaper for everyone. But if you move on, those licences might not come with you. With plugins, that usually means no more updates or support, which quietly turns into a security problem a few months down the line. With stock photos and fonts, you might technically not have the right to keep using them at all.

It’s worth asking: which licences does my site use, whose name are they in, and what happens to them if I leave?

3. What happens when you leave

Nobody likes thinking about the break-up at the start of a relationship, but this is the section that matters most when things go sideways.

A good contract should spell out:

• What gets handed over. Your website files, the database, admin logins, and your domain name.
• How much notice you need to give on any hosting or maintenance agreement.
• Whether there are any fees for leaving, migrating, or “releasing” your site. Yes, some agencies charge for this.

If your contract is silent on all of this, you’re relying on goodwill. Which is lovely right up until it isn’t.

While you’re at it: check your access

Contracts cover who legally owns what. But there’s a practical side too, and it’s worth ten minutes of your time to check you’ve got:

• Your domain name registered in your business’s name, with a login to the registrar that you control. Lose the domain and you lose the website, and quite often your email with it.
• An administrator login to your website. Not an “editor” account. A proper admin one.
• Your Google Analytics and Search Console set up under your own Google account. That’s years of data about your customers, and it shouldn’t live in someone else’s account.

How I handle it

I’ll keep this short, because this isn’t meant to be a sales pitch.

My view is simple: once you’ve paid, your website is yours, not mine to hold hostage. If you ever decide to move on, you get everything you need to take it with you, and I’ll happily help with the handover.

I’d rather keep clients because they want to stay, not because leaving is a hassle.

A quick disclaimer

I build websites. I’m not a lawyer, and this post isn’t legal advice. If your website is a big part of how you make money, or you’re already in a dispute, it’s well worth paying a solicitor to have a proper look at your paperwork.

But if you’ve never actually read the ownership bit of your website contract, now’s a good time. It takes ten minutes, and it’s a lot less stressful to find out today than when you’re trying to leave.

Not sure what you’ve got, or what you should have? Get in touch and I’ll help you work it out, no strings attached.