Software License Agreement in United Kingdom: Template, Key Clauses and Local Law (2026)

Is a software license agreement binding in the United Kingdom? Yes. A software license agreement is a binding contract in the United Kingdom, and clickwrap and signed agreements are routinely enforced. A licence is permission to use software under stated terms, not a sale of the software, so the licensor keeps ownership and the licensee gets only the rights the agreement grants. That distinction drives the whole contract. This is general information, not legal advice. For a high-value or on-premise enterprise licence, ask a qualified UK solicitor. ## What UK law applies to a software licence ### Copyright, Designs and Patents Act 1988

Software is protected as a literary work under the Copyright, Designs and Patents Act 1988. The licence is the permission that lets the licensee copy and run the software without infringing that copyright. The Act also preserves certain user rights, such as making a back-up copy and, in limited circumstances, decompiling for interoperability, which a licence cannot entirely remove. ### Contract law and UCTA The licence terms rest on the common law of contract. The Unfair Contract Terms Act 1977 (UCTA) controls liability exclusions in B2B licences: the cap must be reasonable, and liability for death or personal injury from negligence cannot be excluded. For consumer software, the Consumer Rights Act 2015 treats it as digital content with quality standards. ### Supply context Where software is supplied with services (installation, support), the Supply of Goods and Services Act 1982 implies reasonable care and skill into those services. ### Export control UK export control and sanctions rules can apply to software supplied across borders. ## Key clauses in a UK software license agreement ### Grant of licence and scope The core clause: what the licensee may do (use, install, copy, modify), whether exclusive or non-exclusive, the territory, and whether transferable or sublicensable. Most commercial licences are non-exclusive, non-transferable, and limited to internal business use. ### Licence type: perpetual or subscription A perpetual licence lets the licensee keep using the version bought, usually for a one-time fee. A subscription or term licence works only while fees are paid. State which, and what survives at the end. ### Permitted users and metrics Licences are limited by a metric: named users, seats, devices, cores, or usage. Overuse is the most common cause of an audit bill, so the metric must match real use. ### Restrictions Typically no reverse engineering (subject to the statutory interoperability exception), no renting or reselling, no removing notices, and no building a competing product. ### Ownership and IP Confirm the licensor keeps all IP and the licensee gets only the rights granted. If the licensee pays for custom development, state who owns it, because the default usually favours the developer. ### Fees, payment, and renewal pricing Set the fee, billing, VAT, and whether renewal increases are capped. ### Maintenance, support, and updates Say what support and updates are included, response times, and the update-versus-upgrade line. ### Warranties and limitation of liability A limited performance warranty with an "as is" disclaimer beyond it is standard. The cap must be UCTA-reasonable, with carve-outs for IP indemnity and confidentiality. ### IP infringement indemnity The licensor should defend the licensee against third-party IP claims, with options to fix, replace, or refund. ### Audit rights Enterprise licences often allow usage audits. A fair clause gives notice, limits frequency, and runs in business hours. ### Source code escrow For critical on-premise software, an escrow clause can release the source code if the licensor fails. ### Term, termination, and export State the term, termination grounds, post-termination duties, and export-control compliance. ## A simple UK software license skeleton 1. Parties and commencement 2. Definitions and interpretation 3. Grant of licence and scope 4. Licence type and users or metrics 5. Restrictions (with statutory exceptions preserved) 6. Ownership and intellectual property 7. Fees, payment, VAT, and renewal 8. Maintenance, support, and updates 9. Warranties and disclaimers 10. Limitation of liability (UCTA-compliant) 11. IP infringement indemnity 12. Confidentiality 13. Audit rights 14. Source code escrow (if applicable) 15. Term, termination, and export control 16. Governing law and general terms ## Points worth negotiating Get the grant and the usage metric right so you do not trip an audit. Negotiate a cap on renewal price increases. Insist on a real IP infringement indemnity. Check the liability carve-outs and confirm the cap is UCTA-reasonable. For on-premise software you depend on, consider source code escrow. Remember that the statutory rights to back up and, in limited cases, decompile for interoperability survive the licence. ## Where a single contract workspace helps One licence is manageable; a portfolio of them, each with a different metric, renewal date, price-increase cap, and liability carve-out, is the real work. An AI contract workspace is built for that: each licence becomes a structured clause tree, positions are marked favourable, neutral, or unfavourable to your company, and renewal and audit dates surface automatically. Adira is one such workspace. Adira is India-first today, and deeper United Kingdom jurisdiction coverage is on its roadmap, so for UK-governed licences treat it as a drafting and tracking aid and confirm specifics such as the UCTA reasonableness test with a UK solicitor. The clauses above do not change; a workspace just makes them easier to manage.