Software Licence Agreement UK: Key Terms Explained
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.
If you build software, or you rely on software built by someone else, a licence agreement is the document that quietly runs the relationship between you. It sets out who can do what with the code, for how long, and on what terms.
I'm Brad Askew, and over the years I've seen developers hand over valuable intellectual property with nothing more than a handshake, and businesses sign licences without understanding what they were agreeing to. Both sides tend to regret it later. This guide walks through how software licensing works in England and Wales, what a well-drafted agreement usually contains, and the decisions you need to think through before you put anything in writing. Whether you're licensing a tool you've built, or taking a licence from a vendor, the fundamentals are the same.
What this document is
A software licence agreement is a contract between the owner of software (the licensor) and someone who wants to use it (the licensee). Rather than selling the software outright, the owner grants permission to use it on specific terms. That distinction matters.
Under UK intellectual property law, software is protected automatically by copyright the moment it's written, and the author keeps ownership unless they actively assign it. A licence is how the author allows others to use the work while keeping the underlying rights.
These agreements can cover almost anything: a one-off desktop application, a mobile app, a cloud-based SaaS platform, an API, or an open-source library. They apply whether the software is paid for or free, and whether it's aimed at consumers, businesses, or other developers.
The terms set out what the licensee can do (install, copy, modify, redistribute), what they can't, how long the permission lasts, and what happens if things go wrong. Without one, both parties are exposed: the owner has limited control over how the software is used, and the user has no clear right to rely on it.
How to use this document
- Decide what you're actually licensing. Be precise about the software itself. Is it the compiled application only, or does it include source code, documentation, updates, or supporting services? Many disputes come from vague descriptions. Spell out versions, modules, and anything that sits alongside the core product.
- Choose the licence type. Think about whether the licence should be exclusive or non-exclusive, perpetual or time-limited, and whether the user can transfer it to someone else. A single-user desktop licence looks very different from an enterprise-wide deployment. The commercial model (one-off fee, subscription, usage-based) shapes this decision.
- Set out permitted and prohibited uses. Be explicit about what the user can do. Can they copy the software onto multiple devices? Modify it? Reverse-engineer it? Sublicense it to their own customers? The default under UK copyright law is restrictive, so anything you want to allow needs to be written in, and anything you want to forbid should be called out clearly.
- Deal with liability, warranties and IP indemnities. Decide what the licensor promises about the software working as described, and what happens if a third party claims the code infringes their rights. Limitation of liability clauses need careful drafting to be enforceable under the Unfair Contract Terms Act 1977 and, for consumer deals, the Consumer Rights Act 2015.
- Plan for termination and what happens next. Cover how either party can end the agreement, what triggers automatic termination (non-payment, breach, insolvency), and what the user must do with the software afterwards. If data or customer records sit inside the software, the exit arrangements matter enormously.
Common questions
Q Do I need a licence agreement if I'm giving my software away for free?
Yes, it's still worth having one. Free doesn't mean unrestricted. A licence lets you control how your software is used, limit your liability if something goes wrong, and keep ownership of the underlying code. Open-source licences (MIT, GPL, Apache and others) are essentially free software licences with specific conditions. Even a simple end-user licence is better than nothing.
Q What's the difference between a licence and an assignment?
A licence grants permission to use the software while the original author keeps ownership. An assignment transfers ownership outright, so the author no longer controls it. Most commercial software deals are licences. Assignments are less common and usually appear in acquisitions, bespoke development contracts where the client wants the IP, or employment situations. The distinction has major tax and commercial consequences.
Q Can I use a template I found online?
Templates can be a reasonable starting point, but software licensing has a lot of variables, and a generic document rarely fits a specific commercial situation. Terms that protect an enterprise SaaS vendor are very different from those needed for a mobile app or an open-source library. At a minimum, any template needs careful adaptation to match your actual business model and risk appetite.
Q Does UK or EU law apply to my software licence?
For agreements governed by English law, the relevant framework includes the Copyright, Designs and Patents Act 1988, the Unfair Contract Terms Act 1977, and the Consumer Rights Act 2015 where consumers are involved. Data protection is governed by UK GDPR and the Data Protection Act 2018. If you licence across borders, other jurisdictions may apply, and the choice of law clause becomes important.
Q How do I limit my liability as a software vendor?
Limitation clauses typically cap financial liability and exclude certain types of loss (such as indirect or consequential damages). They must be reasonable to be enforceable, and certain liabilities (death or personal injury caused by negligence, fraud) can't be excluded at all. Consumer contracts face stricter rules than business-to-business deals. Getting this clause right is one of the most commercially important parts of the document.
Q What happens if the licensee breaches the agreement?
Remedies depend on what the licence says and the nature of the breach. Typical options include termination of the licence, injunctive relief to stop the misuse, damages for any loss caused, and claims for copyright infringement where the breach involves unauthorised copying or distribution. A well-drafted agreement will spell out the termination process and preserve the licensor's right to pursue separate remedies under intellectual property law.
Q Should my licence cover updates and support?
It should say something, even if the answer is 'none provided'. Users often assume updates and technical support are included, which can cause friction later. Spell out whether updates are automatic, optional, free or chargeable, and what level of support (if any) the licensee is entitled to. For SaaS products, service levels and uptime commitments usually sit in a separate schedule.
Sources
This guide is based on primary UK law and official guidance.
- LegislationCopyright, Designs and Patents Act 1988legislation.gov.uk
- Guidance · UK GovIntellectual Property Office – software and copyright guidancegov.uk
- LegislationUnfair Contract Terms Act 1977legislation.gov.uk
- LegislationConsumer Rights Act 2015legislation.gov.uk
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.