Last updated: 2026-11-18
Is a Binary a Copyright Work? Compilers, Generated Code and Authorship
Nobody writes a binary. A programmer writes source code, a compiler turns it into object code, a linker stitches in libraries, and an optimiser makes thousands of decisions along the way that no human reviews. Copyright, meanwhile, now asks whether a work reflects its author's "free and creative choices". So is the executable a company ships protected at all, and if so, whose creative choices does it carry?
This page sets out what the law says about object code, how compilation fits the statute, where the EU's reason for protecting software and its test for protecting it point in different directions, and what follows for generated code, AI-written code and trained models.
Object Code Is Protected: The Settled Part FoundationalKnowledge that endures for decades โ core principles
On the basic question the answer is clear. The TRIPS Agreement requires that "computer programs, whether in source or object code, shall be protected as literary works under the Berne Convention"1, and the WIPO Copyright Treaty says protection "applies to computer programs, whatever may be the mode or form of their expression"2. The EU Software Directive's recitals define "computer program" to "include programs in any form, including those which are incorporated into hardware"3. The CJEU confirmed in 2010 that "the source code and the object code of a computer program are forms of expression thereof which, consequently, are entitled to be protected by copyright as computer programs"4.
UK law reaches the same place through its definition of adaptation. Under section 21(4) of the Copyright, Designs and Patents Act 1988 (CDPA), "in relation to a computer program a 'translation' includes a version of the program in which it is converted into or out of a computer language or code or into a different computer language or code"5. Compiling is that conversion, and making a translation is one of the acts restricted by copyright. A binary is therefore the source program in another form: copying the binary copies the program, and the copyright in both belongs to whoever owns the source.
SAS v World Programming fits the same picture from the other side. The CJEU said that if a competitor took "the source code or the object code relating to the programming language or to the format of data files" and built similar elements "with the aid of that code", that would be partial reproduction6. Object code is protected expression even in part; the behaviour it produces is not. See SAS v World Programming.
Whose Creative Choices Does a Binary Carry? Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
creative choices"] --> S["Source code
(literary work)"] S --> C["Compiler and
optimiser"] L["Library and runtime
authors' choices"] --> R["Runtime libraries"] C --> B["Binary"] R --> B C -. "mechanical choices,
no human author" .-> B
Since Infopaq and Painer, a work is original only if it is its author's own intellectual creation, reflecting "free and creative choices" that "stamp the work created with their personal touch"; the Court of Appeal confirmed in 2023 that this is the UK test7. The compiler makes choices too (register allocation, inlining, instruction ordering), but they are determined by its algorithms and settings, not by anyone's creativity. Our reading is that these add no new authorship: the binary is protected because, and to the extent that, it expresses the source author's choices in a different code, not because of anything the compiler did.
That has two consequences worth knowing:
- Two binaries can carry different owners' rights. When you compile with GCC, "GCC may combine portions of certain GCC header files and runtime libraries with the compiled program", which is why those files carry a Runtime Library Exception permitting their use in non-GPL and proprietary programs8. Your executable contains other people's copyright works under licence, as well as your own.
- The person who presses "build" isn't an author by doing so. Running a compiler involves no creative choice about the result. Authorship and ownership stay with whoever wrote the source (or their employer).
Two Reasons for Protection That Don't Quite Agree Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
The EU Software Directive gives its rationale in its second recital: "The development of computer programs requires the investment of considerable human, technical and financial resources while computer programs can be copied at a fraction of the cost needed to develop them independently." It also says that "no tests as to the qualitative or aesthetic merits of the program should be applied"3. That is an investment rationale: protect software because it is expensive to make and cheap to copy, and protect it in whatever form it is distributed, which in practice usually means binaries.
The test it sets, though, is about authorship: "A computer program shall be protected if it is original in the sense that it is the author's own intellectual creation. No other criteria shall be applied"3. Investment alone doesn't satisfy it.
For ordinary compiled software the two agree, because the binary inherits the originality of hand-written source. They diverge as the share of human choice in the code falls:
| How the code was made | Investment | Human creative choice in the code | Likely position |
|---|---|---|---|
| Hand-written source, compiled | High | High (in the source) | Protected, source and binary alike |
| Generated from a hand-written specification (parser generators, interface compilers, schema-to-code tools) | Moderate | In the specification and the generator's templates, not the output's details | Protection follows the specification's and templates' authors; the boilerplate itself may add nothing |
| Written mainly by an AI model from a short prompt | Low to moderate | Little, unless a human selects, arranges and edits substantially | Uncertain; see below |
| Trained model weights | Very high | In the architecture, data selection and training code, not the individual weight values | Open question |
Database law shows that the EU knew how to protect investment without originality when it wanted to: database right protects "substantial investment in obtaining, verifying or presenting the contents of the database" regardless of whether anything in it is a copyright work9. Software got no equivalent. Our reading is that this leaves heavily generated code in a gap the investment rationale didn't anticipate: expensive to produce, cheap to copy, and with little human creative choice for the originality test to find.
Computer-Generated Works and AI-Written Code Ephemeral / ToolingKnowledge that evolves in months to a year โ check for updates
The UK is one of few jurisdictions with a specific rule for works without a human author. Section 9(3) of the CDPA says that for a computer-generated work "the author shall be taken to be the person by whom the arrangements necessary for the creation of the work are undertaken", and section 178 defines computer-generated as "generated by computer in circumstances such that there is no human author of the work"5. In Nova v Mazooma the court applied it to the frames an arcade game drew on screen: the programmer who "devised the appearance of the various elements of the game and the rules and logic by which each frame is generated" was the author, and the player, who had "contributed no skill or labour of an artistic kind", was not10.
A compiled binary is not a computer-generated work in this sense, because it has a human author: whoever wrote the source. Code generated by an AI model from a short prompt is closer to the case section 9(3) was written for, but the provision sits awkwardly with the modern originality test. The government's March 2026 report on copyright and AI puts it this way: the test "is very much associated with human qualities, suggesting that a work created by a non-human could not be 'original'", yet section 9(3) "only applies to works 'without a human author'". It proposed, "in the absence of evidence of its ongoing value", that protection for wholly computer-generated works "should be removed, while copyright should continue to protect works created with AI assistance"; no legislation has followed yet11. In the US, the D.C. Circuit held in 2025 that the Copyright Act requires a human author, and the Supreme Court declined to review the decision in 202612.
Trained Models: An Open Question Ephemeral / ToolingKnowledge that evolves in months to a year โ check for updates
A file of trained weights is the output of a program run over data. Patent law has taken a position on whether such a thing is a program: in Emotional Perception (2026) the Supreme Court held that artificial neural networks of the kind in that case "are 'programs for computers'" for the purposes of the patent exclusion13. That is a ruling on patent law, not copyright. Whether a set of weights is a copyright work, and if so whose, hasn't been decided. Applying the reasoning above, the architecture, training code and curated dataset carry human creative choices; the individual weight values, produced by optimisation, carry none. Our view is that any copyright in a model would have to rest on the former, which makes it thin protection for the most expensive part of the artefact, and trade secrecy and contract more important for model owners than copyright.
What Follows for Programmers Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
- Your binaries are protected as forms of your source code. Distributing a binary doesn't weaken the copyright in it.
- Know what's linked in. Runtime libraries and dependencies bring their own copyright and licence terms into your binary.
- Generated code is only as protected as the human choices behind it. Keep the specifications, templates and design decisions, which is where the authorship lies.
- For AI-assisted work, make and record real decisions about structure, selection and editing. See Making More of Your Output Protectable.
Related Topics
- Software and Intellectual Property: A Map for Programmers: the hub for this set.
- Why Maths Isn't Copyright, and Every File Is a Number: why a binary's bits alone can't settle whether it is protected.
- Beyond Copyright: the Emotional Perception decision in its patent context.
References
-
Agreement on Trade-Related Aspects of Intellectual Property Rights (TRIPS), Article 10(1). https://www.wto.org/english/docs_e/legal_e/27-trips_04_e.htm โฉ
-
WIPO Copyright Treaty (1996), Article 4. https://www.wipo.int/wipolex/en/text/295166 โฉ
-
Directive 2009/24/EC on the legal protection of computer programs, recitals 2, 7 and 8 and Article 1(3). https://eur-lex.europa.eu/eli/dir/2009/24/oj โฉโฉโฉ
-
Case C-393/09 Bezpeฤnostnรญ softwarovรก asociace v Ministerstvo kultury, EU:C:2010:816, paras 34โ35. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62009CJ0393 โฉ
-
Copyright, Designs and Patents Act 1988, ss.9(3), 21(4) and 178. https://www.legislation.gov.uk/ukpga/1988/48/contents โฉโฉ
-
Case C-406/10 SAS Institute Inc v World Programming Ltd, EU:C:2012:259, para 43. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 โฉ
-
THJ Systems Ltd v Sheridan [2023] EWCA Civ 1354, paras 16 and 23. https://caselaw.nationalarchives.gov.uk/ewca/civ/2023/1354 โฉ
-
Free Software Foundation. (2009). GCC Runtime Library Exception, version 3.1. https://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html โฉ
-
Copyright and Rights in Databases Regulations 1997 (SI 1997/3032), reg 13. https://www.legislation.gov.uk/uksi/1997/3032/regulation/13 โฉ
-
Nova Productions Ltd v Mazooma Games Ltd [2006] EWHC 24 (Ch), paras 104โ106. https://caselaw.nationalarchives.gov.uk/ewhc/ch/2006/24 โฉ
-
Department for Science, Innovation and Technology, Department for Culture, Media and Sport, and Intellectual Property Office. (2026, March 18). Report on Copyright and Artificial Intelligence, Section I: Computer-generated works. https://www.gov.uk/government/publications/report-and-impact-assessment-on-copyright-and-artificial-intelligence/report-on-copyright-and-artificial-intelligence โฉ
-
Thaler v Perlmutter, No. 23-5233 (D.C. Cir. 18 March 2025); certiorari denied, No. 25-449 (2 March 2026). https://law.justia.com/cases/federal/appellate-courts/cadc/23-5233/23-5233-2025-03-18.html โฉ
-
Emotional Perception AI Ltd v Comptroller General of Patents, Designs and Trade Marks [2026] UKSC 3, para 23. https://caselaw.nationalarchives.gov.uk/uksc/2026/3 โฉ