Skip to main content
Find your template →
Menu

Intellectual Property in Website Development Agreements | LegalDocuments.co.uk

We're not a law firm — we help you find the right legal support. For advice on your situation, speak to a legal adviser or find a solicitor.

Part ofIP Rights

Written by Brad Askew Solicitor (non-practising)
Brad is on the roll of solicitors of England & Wales but does not hold a practising certificate and does not provide legal advice.
Updated June 2026 · England & Wales
When a business commissions a website, the contract that sits behind the build matters far more than most people realise. A site is never just a collection of pages, it's code, graphics, text, structure, and often data, each of which carries its own intellectual property footprint. Get the IP provisions wrong and you can end up paying for a website you don't actually own, or finding that you can't move away from your developer without losing the lot. I'm Brad Askew, and in my years working across civil and commercial matters I've seen both sides make assumptions that later cost them. This page walks through the IP clauses that tend to matter most in development contracts in England and Wales, so you can go into negotiations with your eyes open and your questions ready.

What this document is

A website development agreement is the contract between the party commissioning a website (the client) and the party building it (the developer or agency). Alongside commercial terms like timelines, milestones and payment, the agreement should set out who owns what once the site goes live.

That question is rarely as simple as "the client pays, so the client owns". Under UK law, the default position is that the person who creates original work generally owns the copyright in it, unless the contract says otherwise or an employment relationship applies.

So without a clear IP clause, a developer may end up retaining copyright in code, designs and graphics they produced, even though the client paid for the build. IP provisions therefore tend to cover: who owns the newly created material, what happens to any pre-existing tools or libraries the developer brings to the project, how third-party components (such as open-source code, stock images or plugins) are licensed, and what rights the client has to modify or transfer the site in future. Getting this right protects both sides from arguments down the line.

How to use this document

  1. Identify what's actually being created. Before drafting IP terms, list out every element the project will produce: source code, front-end design, logos, written copy, photography, video, databases, and any custom integrations. Each category may sit under different IP rights, and lumping them together can create ambiguity about what is transferred and what is merely licensed to the client.
  2. Decide between assignment and licence. Work out whether the client needs full ownership (an assignment of the IP) or whether a licence to use the site is sufficient. Assignments give the client control and the ability to resell or transfer the site, while licences typically cost less but restrict what the client can do and may tie them to the developer for future changes or hosting.
  3. Address pre-existing and third-party materials. Most developers reuse their own frameworks, templates or code libraries, and may also incorporate open-source components or licensed stock assets. The agreement should distinguish these from bespoke work, set out what rights the client has to use them going forward, and confirm that any third-party licences are compatible with how the client intends to run the site.
  4. Deal with trademarks, branding and content. If the client is supplying logos, brand assets or copy, the contract should confirm the developer has permission to use them for the project only. If the developer is designing new branding, make clear who owns the resulting marks and whether the client needs to register any trademarks to protect them properly.
  5. Build in warranties, indemnities and handover terms. The developer should warrant that the work is original and does not infringe anyone else's IP, and ideally indemnify the client if a third party later claims otherwise. The agreement should also cover practical handover: delivery of source files, access credentials, documentation, and any assistance needed if the client later moves to a new developer.

Common questions

Q Do I automatically own my website because I paid for it?
No, and this catches a lot of businesses out. Under UK copyright law, the creator of a work is generally the first owner of the copyright in it, regardless of who paid. Unless your development agreement expressly assigns the IP to you in writing, the developer may retain ownership of the code and design and simply grant you a licence to use the site. Always check the contract before signing.
Q What's the difference between an IP assignment and a licence?
An assignment transfers ownership of the intellectual property from the developer to you, meaning you can use, change, sell or transfer the work freely. A licence leaves ownership with the developer but gives you permission to use the site on agreed terms. Licences can be limited in scope, time or territory, and may restrict whether you can modify the site or move it to another developer.
Q What happens with open-source code used in my website?
Open-source components come with their own licences, which the developer cannot override. Some licences are permissive and cause few issues, while others (such as copyleft licences) can impose obligations on how the wider code is distributed. A good development agreement will list any open-source elements used and confirm their licences are compatible with the way you plan to operate the site.
Q Who owns the database behind my website?
Databases can attract both copyright and a separate database right in the UK, protecting the investment put into compiling and arranging the data. The contract should make clear whether the database structure, the data itself, and any rights in it pass to you on completion. This matters if you hold customer records, product catalogues or other content that you want full control over.
Q Should the developer indemnify me against IP claims?
An IP indemnity is a clause where the developer agrees to cover your losses if a third party successfully claims the work infringes their IP rights. It is a sensible protection to request, though developers often try to cap their liability or exclude claims arising from materials you supplied. Negotiating a fair balance here is one of the more commercially important parts of the agreement.
Q What should I ask for at handover to protect my IP position?
At a minimum, ask for the full source code, design files, content management system credentials, domain and hosting access, and written confirmation that any IP assignment has taken effect. If the developer has used third-party assets, get a list of them with their licences. This ensures you can operate, move or redevelop the site without being dependent on the original developer.
Q Can I register a trademark for my website's branding?
Yes. If new logos, names or slogans have been created as part of the project, you can apply to register them as trademarks with the UK Intellectual Property Office, provided they meet the distinctiveness requirements. Registration gives stronger protection than unregistered rights. Make sure the development agreement confirms you own the branding first, so there is no dispute about who is entitled to register.

Sources

This guide is based on primary UK law and official guidance.

Brad Askew, Solicitor (non-practising)

Written & reviewed by

Brad Askew Solicitor (non-practising)

Brad is on the roll of solicitors of England & Wales but does not hold a practising certificate and does not provide legal advice. LegalDocuments.co.uk is not a law firm and does not provide regulated legal advice.

Full profile →SRA register ↗
Legal disclaimer
This article is for general information only. It is a tool to help you find your way — not legal advice, and not a substitute for speaking to a qualified adviser about your situation.