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

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.