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
Software sits at the heart of almost every modern business, from small startups writing their first mobile app to established companies running complex enterprise platforms. When you or your team have poured months of work into building something useful, the question of how to stop others copying it becomes urgent.
I'm Brad Askew, and in this guide I want to walk you through how intellectual property law in England and Wales actually protects software in practice, what it covers, what it doesn't, and where the common traps lie. We'll look at copyright as the default layer of protection, then touch on patents, trade marks, database rights and the role of contracts and confidentiality.
By the end you should have a clearer picture of which rights apply to your code, your interfaces and your documentation, and what steps you can take to keep control of the work you've built.
Overview
Intellectual property protection for software is not a single right but a bundle of overlapping legal protections that together shield the different elements of a software product. In the UK, the primary layer is copyright, which arises automatically the moment original code is written down or stored.
Copyright covers the source code, the compiled object code, and the supporting written materials such as technical manuals and user guides. Beyond copyright, other rights can apply depending on what you've built. Patents may protect certain technical inventions implemented in software, though the threshold is high in Europe.
Trade marks protect the name and branding of the product. Database rights may apply where significant investment has gone into compiling structured data. Trade secret and confidentiality law protects know-how, algorithms and internal documentation that you haven't publicly released. Contracts, licences, NDAs, employment terms and assignments, tie these rights together and control how your software is used, shared and commercialised. Understanding which rights apply to which parts of your product is the first step to protecting it properly.
Key steps
Identify what you actually own. Start by listing every component of your software, the source code, any third-party libraries, open source dependencies, graphics, written documentation, databases and branding. For each item, work out who created it and under what arrangement. Code written by an employee in the course of their job generally belongs to the employer, but contractor work usually needs a written assignment to transfer ownership.
Consider patents for genuinely technical inventions. If your software solves a technical problem in a novel and inventive way, for instance, a new data compression method or a hardware-controlling process, a patent may be available. Patents are expensive and time-consuming, and pure business methods or straightforward code generally won't qualify. Speak to a patent attorney early, before any public disclosure, because disclosure can destroy your ability to patent.
Register trade marks and secure your brand. The name of your product, its logo and distinctive visual elements can be protected as registered trade marks through the UK Intellectual Property Office. Registration gives you a far stronger position than relying on unregistered rights alone, and it's often the cheapest meaningful IP investment a software business can make. Check availability carefully before launch to avoid expensive rebrands later.
Lock down contracts, licences and confidentiality. The legal rights only work if your contracts back them up. Make sure employment contracts contain proper IP assignment clauses, contractor agreements assign rights in writing, NDAs cover sensitive technical information, and your end-user licence or SaaS terms clearly define what customers can and cannot do with the software. Open source licences also need careful review, using GPL code, for example, may affect how you can distribute your own product.
Q Does software copyright need to be registered in the UK?
No. Copyright in the UK arises automatically the moment an original work is fixed in a tangible form, which for software means as soon as the code is written or stored. There is no copyright register in the UK. That said, keeping dated records, version histories and signed authorship documentation is important because you may need to prove ownership and creation dates if a dispute arises later.
Q Can I patent my software in the UK?
Software as such is excluded from patentability in the UK, but software that produces a genuine technical effect beyond normal computer operation may qualify. Examples include software controlling industrial processes, improving hardware performance or solving specific technical problems. Pure business methods, presentation of information or straightforward applications generally cannot be patented. The threshold is assessed case by case, and specialist patent attorney input is usually essential before filing.
Q Who owns code written by a contractor?
By default, a freelance developer or contractor retains copyright in code they create, even if you've paid them to build it. To own the code outright, you need a written assignment of copyright signed by the contractor. A licence alone is not the same as ownership. This is one of the most common and costly mistakes in early-stage software businesses, so always get assignment terms in writing before work starts.
Q What happens if I use open source code in my product?
Open source licences are legally binding contracts, and different licences impose very different obligations. Permissive licences like MIT or Apache generally allow commercial use with attribution. Copyleft licences like GPL can require you to release your own source code if you distribute software that incorporates GPL-licensed components. Always audit your dependencies and understand the terms before shipping a product that mixes open source with proprietary code.
Q How do I protect algorithms and know-how that aren't in published code?
Algorithms, training data methodologies, internal architectures and other confidential know-how can be protected as trade secrets under the law of confidence and the Trade Secrets Regulations. Protection depends on actually keeping the information confidential, through NDAs, restricted access, employee confidentiality clauses and reasonable security measures. Once information is published or leaked without control, trade secret protection is usually lost permanently.
Q Does copyright protect the look and feel of my user interface?
Individual graphic elements, icons and original text within a UI can attract copyright, and distinctive visual layouts may have some protection. However, the overall functional 'look and feel' or the general way a program behaves is harder to protect, because copyright covers expression rather than underlying ideas or functions. Registered designs may offer additional protection for the appearance of screens and interfaces in some cases.
Q How long does software copyright last?
In the UK, copyright in software written by a human author lasts for the life of the author plus 70 years from the end of the year in which they died. Where the work is created by an employee, the employer owns the copyright but the duration is still calculated by reference to the human author's life. This is far longer than the commercial lifetime of almost any software product.
Software protection pulls together copyright, contracts, trade marks and sometimes patents, and which matters most depends entirely on what you've built and how you plan to use it. An experienced legal adviser can help you think through the options based on what you describe on the call, so you can focus on the protections that actually matter for your situation.
✓Plain-English answers to your specific questions about protecting your software
✓Practical perspective on which IP rights are most relevant to what you describe
✓What to watch out for when using contractors, open source or third-party components
✓Clarity on your next steps for securing the work you've built
Personal call · For information only · Independent advisers
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.
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.