Who Owns The Code In A Website Build?

If you're asking who owns website code in the UK, the usual answer is: not automatically you, even if you paid for the website.

That can feel surprising. You approve the brief, pay the invoices and launch the site, so it seems natural to assume your business owns everything. Under UK copyright law, though, ownership depends on what was created, who created it and what your contract says.

The good news is that this doesn't have to be complicated. Once you separate custom code, templates, plugins, open-source components and third-party tools, it's much easier to see what rights your business actually needs.

Do You Own The Website Code If You Paid For It?

Usually, no. Paying for a website build doesn't automatically transfer copyright in the code to your business.

In the UK, copyright is mainly governed by the Copyright, Designs and Patents Act 1988. Website code will usually be protected as a literary work, and other parts of the site may have their own protection, such as graphic designs, written content, images, video and databases.

The first owner of copyright is generally the person who creates the work. If your website developer is an employee creating the code as part of their job, your business will usually own the copyright. But if you hire an external freelancer or agency, they will usually own the copyright unless there's a written assignment transferring it to you.

A copyright assignment must be in writing and signed by or on behalf of the assignor. If you need an exclusive copyright licence, that also needs to be in writing and signed by or on behalf of the copyright owner. In practice, any important website licence should still be set out clearly in writing. A copyright licence agreement is often used to record those rights clearly.

So, if your contract is silent, your business may only have an implied licence to use the website for the purpose you both had in mind. That may be enough to run the site day to day, but it may not be enough if you want to:

• move the site to a new developer
• reuse the code in a second website or app
• sell the business and transfer the website assets to the buyer
• modify the code without the original developer's help
• stop the developer reusing parts of the work for a competitor

Say Priya runs a small skincare brand in Manchester. She pays a web agency to build a custom eCommerce site. Two years later, she wants another developer to add a subscription feature. If her original contract only gave her a licence to use the site as delivered, she may not have the rights or files needed to make those changes easily.

What Rights Does Your Website Developer Keep?

It depends on your agreement, but your developer may keep ownership of code, reusable tools, processes and know-how unless they agree to transfer them.

This isn't always unfair. Many developers use existing libraries, frameworks, snippets and internal tools they've built over years. You probably don't need to own every general piece of development know-how they used to create your website.

What you do need is enough control to run, maintain, improve and transfer your site without being locked in unnecessarily.

Background IP

Background IP is material your developer already owned before your project started. For example, they may have a standard booking module, admin dashboard or code base they adapt for different clients.

Your agreement should say whether you get a licence to use that background IP as part of your website, and whether that licence is:

• perpetual, meaning it continues without an end date
• worldwide, so it works wherever your site is accessed
• royalty-free, so you don't pay extra each time the site is used
• transferable, so it can move with your business if you sell it
• modifiable, so you or another developer can maintain and improve the site

New Custom Code

New custom code is code created specifically for your project. This is often the part your business is most likely to want to own, especially if it gives you a commercial advantage.

For example, if you've paid for a custom quoting tool, customer portal or stock management integration, you may want copyright assigned to your business. If the developer wants to reuse non-confidential concepts, the contract can deal with that separately.

Moral Rights

For non-code elements of a website, such as graphic design, copy or images, creators may have moral rights, including the right to be identified where that right has been asserted and the right to object to derogatory treatment. These moral rights generally don't apply to computer programs. Website contracts often include appropriate moral rights waivers or consents for design and content assets.

What About Open-Source Code, Plugins And Templates?

You usually don't own open-source code, plugins or templates. You're more likely to have permission to use them under a licence.

This is where website IP can get messy. A modern website is rarely built from scratch. It may include a mix of custom code, open-source libraries, a purchased theme, third-party plugins, payment tools, analytics scripts, maps, fonts and stock images.

Your contract should be honest about that. You don't need your developer to promise that every line of code is completely original if that isn't how the site is being built. You do need to know what has been included and what rules apply.

Open-Source Components

Open-source software can be incredibly useful, and many commercial websites rely on it. But open-source doesn't mean no rules.

Each open-source component comes with licence terms. Some licences are very permissive. Others, such as certain copyleft licences, may require notices, source code sharing or other conditions if the software is modified or distributed.

For a typical business website, the risk is often manageable. But if your site includes a platform, SaaS product or customer-facing software tool, open-source licence compliance matters more. You should ask your developer for a list of open-source components, source code dependencies and licences used in the build.

Plugins And Themes

Plugins and themes are usually licensed, not owned. The licence might sit in your business account, the developer's agency account or an individual freelancer's account.

This matters because paid plugins and themes often need ongoing subscriptions for updates, security patches and support. If the licence is held in the developer's account, you may lose access if you change developers.

Where possible, your business should hold key plugin, theme and hosting accounts in its own name. That way, you're not dependent on one supplier for basic access.

Third-Party Tools

Tools like payment processors, booking systems, CRM forms, email marketing platforms, maps, chat widgets and analytics platforms are usually separate services. Your website connects to them, but you don't own the underlying software.

Your agreement should make clear who sets up the accounts, who owns the login, who pays the fees and what happens if the tool changes its pricing or terms.

Do You Own The Design, Content And Source Files?

Not automatically. Design files, written content, images and source files each need to be dealt with clearly in your website development agreement.

Website ownership isn't just about code. When you launch a site, you may also need rights to the visual design, logo usage, UX layouts, copy, images, videos, animations and editable design files.

Website Design

If a designer creates a custom visual design for your website, copyright may sit with the designer unless assigned to your business. Your contract should say whether you own the final approved designs, working files and any unused concepts.

Some designers are happy to assign final designs but keep rejected concepts or reusable design elements. That can be a fair middle ground if it's clearly written down.

Content And Images

If your business writes the website copy, takes the photos or creates the videos, you may already own that content. If your developer, copywriter or photographer creates it for you, you should check whether rights are assigned or licensed.

Stock images, icons and fonts are often licensed from third parties. Your business needs permission to use them in the way your site uses them, including across different pages, campaigns and territories. Some licences restrict use in logos, merchandise or paid advertising, so don't assume one licence covers everything.

Source Files And Admin Access

Source files are the editable files needed to maintain or adapt the website properly. They may include design files, code repositories, build files, configuration files and database exports.

You should agree upfront what will be handed over at launch or final payment. At a minimum, many businesses need:

• administrator access to the website CMS
• domain name and DNS access
• hosting or deployment access
• code repository access, where relevant
• theme, plugin and licence account details
• editable design files, if you've paid for them
• documentation for key integrations

Your domain name deserves special mention. It's not the same as copyright, but it's a critical business asset. Ideally, the domain should be registered in your business name, not your developer's name.

What Should A Website Development Agreement Say?

A good website development agreement should clearly say what is being built, who owns what and what happens after launch.

Templates can be a useful starting point, but website projects vary a lot. A brochure site, online store, marketplace and SaaS platform each need different terms. Your agreement works best when it matches the actual build and your commercial plans.

Your website development agreement should usually cover:

• scope of work, including pages, features, integrations and deliverables
• project milestones, approvals, testing and launch process
• fees and payment timing, including deposits, staged payments and late payment consequences
• change requests, so extra work is priced and approved before it starts
• IP ownership, including custom code, designs, content and documentation
• licences for background IP, open-source software, templates and third-party tools
• handover, including source files, accounts, passwords and repositories
• support and maintenance, including bug fixes, updates and response times
• confidentiality, especially if the developer sees customer data, business plans or trade secrets
• data protection, including UK GDPR and Data Protection Act 2018 obligations where personal data is handled
• warranties, such as promises that the developer has the right to provide the work and that it won't knowingly infringe third-party rights
• termination, including what happens to work in progress if the project ends early

If your website collects personal data, your developer may also act as a processor for UK GDPR purposes, particularly if they host, maintain or access user data. You may need data processing terms covering security, instructions, sub-processors, breach notification and deletion or return of data.

If your site sells to consumers, your legal setup should also deal with website terms and conditions, privacy notices, cookies and the Consumer Rights Act 2015. That's separate from code ownership, but it's often best handled while the site is being built, not after launch.

What If You Already Launched Without A Proper Agreement?

You can often fix the position, but it's easier if you deal with it while the relationship with your developer is still positive.

Start by checking what documents and messages you already have. Look at proposals, statements of work, invoices, emails, project management tickets and any terms on the developer's website. You're looking for anything that mentions ownership, licensing, source files, accounts or handover.

Then make a practical list of what your business needs now. For example:

• confirmation that you can keep using the site permanently
• an assignment of copyright in custom code and designs
• a licence to use any developer-owned background tools
• a list of third-party plugins, themes and open-source components
• transfer of domain, hosting and software accounts
• access to the code repository, editable files and any source code escrow arrangements
• permission for a new developer to maintain and modify the site

In many cases, this can be resolved with an IP assignment deed, a website handover agreement or a variation to the original contract. If there's disagreement, the practical question is often whether you have enough rights and access to keep trading while you work through the issue.

Try to avoid using final payment as your only leverage unless the contract clearly supports that position. A better approach is to tie payment, acceptance and handover obligations together from the start, so everyone knows what needs to happen before the project is complete.

Common Mistakes To Avoid

The biggest mistake is assuming website ownership is all-or-nothing. In reality, your site is a bundle of different rights and access points.

Here are some common traps to watch for:

• Assuming payment equals ownership. It often doesn't, unless the contract says so clearly.
• Ignoring reusable developer tools. You may not need to own them, but you do need a licence that lets your site keep working.
• Letting the developer hold every account. Your business should control key assets like the domain, hosting and critical plugin licences where possible.
• Forgetting source files. A live website is useful, but editable files and repository access may be needed for future work.
• Overlooking open-source licences. Most are manageable, but you need to know what has been used.
• Leaving maintenance vague. After launch, you still need updates, security patches and support responsibilities.

A clean handover process can save a lot of frustration later. It also makes your business easier to sell, franchise, invest in or scale, because you can show what digital assets you control.

Key Takeaways

• Paying for a website build doesn't automatically mean your business owns the code.
• Under UK copyright law, external developers usually keep copyright unless there's a written assignment.
• Exclusive copyright licences need signed writing, but important website licences should be written down even when the law allows more flexibility.
• Custom code, open-source components, plugins, templates, content and third-party tools all need separate treatment.
• Your business should aim to control key accounts, source files and access needed to run and maintain the site.
• A tailored website development agreement can set out IP ownership, licences, handover, maintenance and UK GDPR responsibilities clearly.

If you'd like help with website development agreements, IP ownership clauses, software licensing or website handover documents, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.