Software copyright UK protection is automatic: the moment original code is written and saved, it becomes a protected literary work under the Copyright, Designs and Patents Act 1988, with no registration and no fee involved. ApexCounsel works with Cambridge developers, startups and scale-ups who assume copyright works like a trademark, and are often surprised to learn how it actually applies to code, contracts and AI-assisted development.
Key Takeaways
- UK software code is automatically protected as a literary work under section 3(1)(b) of the CDPA 1988, with no registration system or fee.
- Copyright in software normally lasts for the life of the author plus 70 years; computer-generated works with no human author currently get only 50 years, under section 12(7).
- The UK government’s Report on Copyright and Artificial Intelligence, published 18 March 2026, proposes removing copyright protection for computer-generated works altogether.
- The Court of Appeal confirmed in SAS Institute Inc v World Programming Ltd [2013] EWCA Civ 1482 that copyright protects the code itself, not the functionality or programming language behind it.
- Without a written assignment, a freelance developer usually keeps copyright in code a business paid them to write, under section 11 of the CDPA 1988.
Is Software Protected by Copyright in the UK?
Yes. UK software copyright arises automatically the moment original code is written and recorded in some fixed form, protected as a literary work under section 3(1)(b) of the Copyright, Designs and Patents Act 1988. Computer programming, consultancy and related activities already account for the largest single share of the UK’s digital economy, which contributed almost £160 billion in gross value added in 2023, according to the Office for National Statistics.
This is the single most misunderstood point in software copyright UK questions we hear from founders. Unlike a trademark, which has to be actively filed with the UK Intellectual Property Office and examined before it registers, copyright in code simply exists, provided the work is original in the sense required by the CDPA 1988: it must reflect the author’s own intellectual creation rather than being copied.
UK software copyright is automatic and unregistered. Under section 3(1)(b) of the Copyright, Designs and Patents Act 1988, computer programs are protected as literary works from the moment of creation, with no application, fee or certificate involved, unlike trademark or patent registration through the UK Intellectual Property Office.
Because there is no register, ownership disputes turn on evidence: version control history, timestamped commits and signed contracts, not a certificate from a government office. Businesses that treat this casually often discover the gap only when an investor, buyer or co-founder asks them to prove it.
What Software Copyright Protects, and What It Leaves Out
Software copyright protects the literal expression of code, meaning the source code, object code and certain preparatory design material, but it does not protect the underlying functionality, ideas or programming language a program uses. This distinction was confirmed decisively by the Court of Appeal in SAS Institute Inc v World Programming Ltd [2013] EWCA Civ 1482, which held that a rival developer could lawfully replicate what software does, without copying how the original code does it.
| Usually protected by copyright | Usually not protected by copyright |
|---|---|
| Source code, as originally written | The functionality or behaviour the code produces |
| Object code (compiled/executable form) | The programming language or file formats used |
| Preparatory design material, such as detailed flow diagrams | Ideas, algorithms and mathematical methods themselves |
| Original screen layouts and graphics, as artistic works | The “look and feel” of a program’s outputs, generally |
The Court of Appeal reached a similar conclusion on visual output in Nova Productions Ltd v Mazooma Games Ltd [2007] EWCA Civ 219, rejecting a claim that a rival arcade game had copied the “look and feel” of another, since the expression protected by copyright is the code, not what a user sees on screen. For developers, a competitor building a similar product, even one that behaves identically, is not automatically infringing, provided they write their own code.
Who Owns the Copyright in Code: The Developer, the Freelancer or the Business?
An employer automatically owns copyright in code written by an employee during their employment, under section 11(2) of the CDPA 1988, but a freelance developer keeps copyright in what they write unless a contract assigns it. This single default rule, buried in a piece of 1988 legislation, is behind a large share of the ownership disputes ApexCounsel sees in early-stage tech businesses.
[CAMBRIDGE PERSPECTIVE] This catches out Cambridge tech startups constantly. A founder commissions a freelance developer to build the first version of a product, pays the invoice in full, and reasonably assumes payment means ownership. It does not. Without a written assignment clause, the freelancer remains the legal owner of the code under section 11 of the CDPA 1988, however much the business paid for it, and that gap tends to surface at the worst possible moment, during an investor’s due diligence review.
Getting this right matters beyond the legal technicality. Intangible assets including software copyright can be recognised on a balance sheet, but only where ownership is clear, and unresolved assignment gaps are a routine flag in due diligence, according to ICAEW guidance on valuing intellectual property assets. A signed assignment agreement, in place before the code is written rather than after, is the cheapest fix available.
How Long Does Software Copyright Last in the UK?
Software copyright in the UK lasts for the life of the human author plus 70 years for the vast majority of code, but a computer-generated work with no identifiable human author currently gets only 50 years from the end of the year it was made, under section 12(7) of the CDPA 1988. Most commercial software falls into the first category, since it has one or more identifiable human authors.
| Type of work | Legal basis | Duration |
|---|---|---|
| Code written by an identifiable human author | Section 12(2), CDPA 1988 | Life of the author plus 70 years |
| Code with joint human authors | Section 12(8), CDPA 1988 | Life of the last surviving author plus 70 years |
| Computer-generated work, no human author | Sections 9(3) and 12(7), CDPA 1988 | 50 years from the end of the year of creation |
The computer-generated works category was written into UK law in 1988, decades before generative AI tools existed, and it is now under direct review.
AI-Generated Code and the Changing Rules on Computer-Generated Works
Code produced with little or no human input from an AI coding assistant may currently qualify as a UK “computer-generated work” under section 9(3) of the CDPA 1988, with copyright credited to whoever made the arrangements for its creation, but the government’s own March 2026 report proposes scrapping this protection entirely. The Report on Copyright and Artificial Intelligence, published on 18 March 2026 under the Data (Use and Access) Act 2025, recommends that protection for computer-generated works should be removed, while the government continues to monitor its use and impact.
Under sections 9(3) and 12(7) of the Copyright, Designs and Patents Act 1988, a UK “computer-generated work” created with no human author is currently protected for 50 years, with the author deemed to be the person who made the arrangements necessary for its creation. The government’s Report on Copyright and Artificial Intelligence, published 18 March 2026, proposes removing this protection.
[ORIGINAL ANALYSIS] In our view, most developers using tools such as GitHub Copilot or similar AI coding assistants do not need to worry about this shift day to day, because code produced through genuine human-directed prompting, editing and integration will usually still count as human-authored rather than computer-generated. The real exposure sits with businesses that let an AI tool generate substantial, largely unedited blocks of code and then rely on copyright to stop a competitor copying them. If the computer-generated works category is removed as proposed, that fallback protection disappears, which makes ordinary contractual and confidentiality protections, not copyright, the safety net worth checking now.
The same report noted that over 90% of consultation respondents wanted AI developers to disclose the sources of their training material, a related debate worth watching for any software business training or fine-tuning models on proprietary code.
What Counts as Software Copyright Infringement?
Software copyright infringement in the UK means copying a substantial part of the original code itself, not replicating what the program does or how it looks on screen, following the Court of Appeal’s reasoning in SAS Institute v World Programming. “Substantial” is judged by quality, not quantity, so copying a small but functionally important routine can infringe even if it is a tiny fraction of the overall codebase.
In SAS Institute Inc v World Programming Ltd [2013] EWCA Civ 1482, the Court of Appeal held that copyright does not protect a computer program’s functionality, programming language or file formats, only its literal source and object code. A rival developer who independently writes new code that behaves the same way does not infringe copyright by doing so.
The CDPA 1988 also carves out specific permitted acts that are not infringement. Sections 50B and 50BA allow limited decompilation to achieve interoperability with an independently created program, and allow a lawful user to observe, study or test a program’s functioning to understand the ideas behind it, provided this happens while using the program for its intended purpose. These exceptions cannot be excluded by a software licence.
Where infringement is suspected, the starting point is usually a side-by-side comparison of the disputed code, followed by a formal letter before claim. The Law Society’s guidance on copyright and reporting infringements sets out the general framework, though software disputes usually need a solicitor experienced in reading and comparing source code.
Does Open Source Code Put Your Software Copyright at Risk?
Almost certainly yes, if it isn’t tracked properly: 97% of commercial codebases now contain open source components, and open source code makes up roughly 70% of the average scanned codebase, according to the 2025 Open Source Security and Risk Analysis Report from Synopsys/Black Duck. Each embedded package carries its own licence, and not all licences are compatible with keeping your own code proprietary.
- Permissive licences (MIT, Apache 2.0, BSD) generally allow you to use the code in a proprietary product with minimal obligations, usually just retaining the original copyright notice.
- Weak copyleft licences (LGPL, MPL) typically only require you to share modifications to the licensed component itself, not your entire application built around it.
- Strong copyleft licences (GPL, AGPL) can require you to release your own source code under the same licence if you distribute a product that incorporates the component, which is a serious commercial risk if missed.
The practical risk is rarely a developer deliberately breaching a licence. It is usually a dependency of a dependency, pulled in automatically by a package manager, that nobody reviewed. A software bill of materials, checked before release rather than after a customer’s legal team asks for one, is the standard fix.
How Can Developers Prove and Protect Ownership of Their Code?
Because UK software copyright has no register, ownership is proved with evidence of authorship and timing, not a certificate. None of the steps below are legally required to hold copyright, but each one matters if ownership is ever challenged.
- Keep full version control history (Git or equivalent) rather than deleting or squashing early commits, since timestamped history is strong evidence of authorship.
- Use written assignment agreements with every freelancer or contractor, signed before or at the point work begins, not after a dispute arises.
- Confirm employment contracts include IP clauses that put beyond doubt that code written for the business belongs to the business.
- Keep dated design documents, specifications and drafts, which help establish when a work was created and by whom.
- Mark distributed software with a copyright notice (© [year] [owner]), which is not legally required in the UK but puts third parties on clear notice of ownership.
You can start assembling an IP assignment clause or a developer confidentiality agreement using the ApexCounsel document creator, then have a solicitor review it before it’s relied on for anything commercially significant.
Software Licences and Developer Contracts: What to Include
[SOLICITOR INSIGHT] The single most common gap we find when reviewing developer and freelancer contracts is a missing or badly drafted IP assignment clause, often replaced with a vague line about the client “owning the final product,” which does not actually transfer copyright in the underlying code. A proper clause needs to assign copyright expressly, cover future works created under the agreement, and address moral rights, since authors retain certain moral rights under the CDPA 1988 even after assigning copyright, unless those rights are also waived in writing.
A commercial software licence needs equivalent care in the other direction: whether it is exclusive, whether sublicensing or modification is allowed, and what happens to it on an acquisition. Gaps here tend to surface at renewal, or when a buyer’s solicitors query who actually owns what.
Software Copyright or Patent: Which Protects Your Code?
Copyright protects your code automatically, but a computer program is excluded from patent protection “as such” under section 1(2)(c) of the Patents Act 1977, meaning software itself generally cannot be patented in the UK. This exclusion is one of the most persistent points of confusion among first-time founders who assume any original piece of technology can be patented.
The exclusion has limits. Where software delivers a genuine technical effect beyond the ordinary running of a computer, such as controlling an external process, the underlying invention can still be patentable. For most software businesses, though, copyright combined with confidentiality and strong contracts, rather than a patent application, is the realistic and cheaper route to protecting the code itself.
If you are unsure which protection applies to a specific product, or need a contract reviewed before it goes out, the ApexCounsel IP services team can talk it through from a straightforward, transparently priced starting point, and you can book a consultation if your situation involves a live dispute or an upcoming funding round.
Frequently Asked Questions
Do I need to register software copyright in the UK?
No. UK software copyright arises automatically under section 3(1)(b) of the CDPA 1988 as soon as original code is created, with no registration, application or fee. Dated version control history and signed ownership agreements are the practical substitute for a register if you ever need to prove ownership.
Can two developers independently write the same code without infringing each other’s copyright?
Yes, in principle. Copyright only protects against copying, not independent creation, so if two developers genuinely write similar code without access to each other’s work, neither infringes, though proving genuine independence can be difficult in practice.
Does copyright protect an app’s user interface design as well as its code?
Original visual elements, such as bespoke icons and screen layouts, can separately be protected as artistic works, but the general “look and feel” of an app is not protected by copyright, following cases such as Nova Productions v Mazooma Games [2007] EWCA Civ 219.
Who owns the copyright if I build an app using an AI coding assistant?
It depends how much human creative input went into the result. Code substantially directed, edited and integrated by a human developer is usually treated as authored by that person or their employer, while code with no identifiable human author may fall into the UK’s narrower, currently under-review “computer-generated work” category.
Can I stop an ex-employee from using code they wrote for my business?
Generally yes, since section 11(2) of the CDPA 1988 makes the employer first owner of copyright in work created during employment. This default can be varied by the employment contract, so check its IP clause rather than assuming.
Is it software copyright infringement to reverse engineer a competitor’s program?
Not always. Sections 50B and 50BA of the CDPA 1988 permit limited decompilation for interoperability with an independently created program, and allow a lawful user to study how a program works while using it for its intended purpose, and a licence cannot remove these rights.
Software copyright UK protection gives developers and businesses a strong, automatic starting point, but the real risk usually sits in what surrounds the code: unclear freelancer contracts, unreviewed open source dependencies, and, increasingly, how much of a codebase was genuinely human-authored. If any of that sounds unresolved in your business, contact ApexCounsel to talk it through with a solicitor in plain English.
