Last updated: 2026-11-18
Why Maths Isn't Copyright, and Every File Is a Number
Take the two bytes of the text "Hi": 72 and 105. Read them as a single number in base 256 and you get 72 ร 256 + 105 = 18,537. Every file works the same way. A one-megabyte program is a single integer somewhere below 28,388,608, a number about two and a half million decimal digits long. Mathematics, meanwhile, is excluded from copyright and from patents. If every program is a number and numbers are mathematics, how can any program be protected?
This page explains why mathematical concepts are excluded, why the exclusion doesn't swallow software whole, and what the "every file is a number" argument gets right and wrong about how copyright works.
The Exclusion FoundationalKnowledge that endures for decades โ core principles
The exclusion is written into the treaties. TRIPS states that "copyright protection shall extend to expressions and not to ideas, procedures, methods of operation or mathematical concepts as such"1, and the WIPO Copyright Treaty repeats the sentence word for word2. The Software Directive applies it to programs: "Ideas and principles which underlie any element of a computer program, including those which underlie its interfaces, are not protected"3. Patent law has its own version: the Patents Act 1977 declares that "a discovery, scientific theory or mathematical method" is not an invention4.
The CJEU applied the copyright exclusion in SAS v World Programming. The keywords, syntax and commands in a software manual "consist of words, figures or mathematical concepts which, considered in isolation, are not, as such, an intellectual creation of the author"5.
Why the Law Excludes It FoundationalKnowledge that endures for decades โ core principles
Three reasons run through the cases.
- Monopolies on ideas block everyone else. The CJEU's reason for refusing to protect functionality applies equally to mathematics: protection "would amount to making it possible to monopolise ideas, to the detriment of technological progress and industrial development". Copyright on a program instead "covers only the individual expression of the work and thus leaves other authors the desired latitude to create similar or even identical programs provided that they refrain from copying"5.
- Mathematics is discovered, not authored. A theorem is true whoever proves it first, and its statement leaves little room for choice. Where "technical considerations, rules or constraints โฆ leave no room for creative freedom", the CJEU has held, the originality test isn't met6. A formula is the extreme case of a result dictated by its constraints.
- A patent on a method of calculation would cover every use of it. In Gottschalk v Benson (1972), the US Supreme Court refused a patent on a method of converting binary-coded decimal numbers to pure binary, because the patent would wholly pre-empt the formula and "in practical effect would be a patent on the algorithm itself"7.
The exclusion covers the concept, not every text that contains mathematics. A textbook's explanation of a proof, its choice of examples and its ordering are expression and can be protected; the theorem it proves can't. A program implementing an algorithm is expression; the algorithm is not.
Every File Is a Number Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
The observation is mathematically correct and has been made memorably more than once. In 2001 Phil Carmody found prime numbers that encode the DeCSS program, software for decrypting DVDs whose distribution was being challenged in the US courts, including one whose binary form is itself an executable DeCSS program8. In 2007, after the industry body behind HD DVD and Blu-ray encryption sent takedown notices over a 16-byte processing key, Digg users posted the key, a 128-bit number usually written in hexadecimal beginning 09 F9, so many times that the site gave up removing it9. That dispute was about anti-circumvention law, not copyright, but it showed how strange it looks to treat a number as forbidden. Borges imagined the same idea in fiction: a library containing every possible book of a fixed length, and therefore every book ever written or to be written, alongside endless nonsense10.
If copyright attached to bit patterns, these examples would make it incoherent: every possible program already "exists" as an integer, and no one could own a number that has always been there. Copyright doesn't attach to bit patterns.
What Copyright Attaches To: Provenance, Not Pattern Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
Two features of copyright law resolve the puzzle.
The first is that copyright protects a work, created by an author at a time, not a number. Originality is a property of how something came to be, through free and creative choices, and two identical files can have different legal status because they have different histories. Matthew Skala's essay "What Colour are your bits?" makes the point by saying that bits carry a "colour" (their provenance) that can't be detected by inspecting them but matters to the law. Computer scientists treat identical bit sequences as interchangeable; lawyers ask where they came from11.
The second is that infringement requires copying. Owning the copyright in a program doesn't stop someone else producing an identical file independently; it stops them copying yours. English law has long required a causal connection between the two works, though that copying can be subconscious12. For a large program, independent creation of an identical file is so improbable that identity is strong evidence of copying. For a short one, such as a ten-line function or a common idiom, independent creation is entirely plausible, and the expression may also be too constrained to be original at all.
| Question | Mathematics' answer | Copyright's answer |
|---|---|---|
| Are these two files the same? | Yes, if the bits are equal | The bits may be equal while their legal status differs |
| Does this number exist before anyone writes it down? | Yes | Irrelevant; what matters is whether a particular author created this work |
| Can you own a number? | No | No, but you can stop others copying your work, whatever number encodes it |
| What if someone produces the same file independently? | It is the same number | No infringement, because there was no copying |
Our reading of what this means for software is that the "large number" argument is right about one thing and wrong about another. It is right that nothing in a file's content marks it as protected or unprotected, which is why disputes turn on evidence of origin: version history, access to the original, and similarity in details that function doesn't dictate. It is wrong to conclude that protection is therefore incoherent, because the law never claimed to protect the number. It protects an author's act of creation against being copied.
What This Means for Programmers Applied / MethodologicalKnowledge with a 5โ10 year half-life โ stable practice
- You can implement any algorithm, formula or mathematical method without infringing copyright, provided you write your own implementation. Patents are the only right that can block you from using a method, and only a patented technical application of it.
- The more your code is dictated by mathematics or by a specification, the thinner its protection. A direct transcription of a formula into code leaves little room for creative choice.
- Keep evidence of origin. Since bits don't show where they came from, version history and design records are what prove independent creation, or prove copying by someone else. See Making More of Your Output Protectable.
Related Topics
- Software and Intellectual Property: A Map for Programmers: the hub for this set.
- Is a Binary a Copyright Work?: how a binary carries the source author's creative choices.
- Beyond Copyright: when a mathematical method applied to a technical problem can be patented.
References
-
Agreement on Trade-Related Aspects of Intellectual Property Rights (TRIPS), Article 9(2). https://www.wto.org/english/docs_e/legal_e/27-trips_04_e.htm โฉ
-
WIPO Copyright Treaty (1996), Article 2. https://www.wipo.int/wipolex/en/text/295166 โฉ
-
Directive 2009/24/EC on the legal protection of computer programs, Article 1(2). https://eur-lex.europa.eu/eli/dir/2009/24/oj โฉ
-
Patents Act 1977, s.1(2)(a). https://www.legislation.gov.uk/ukpga/1977/37/section/1 โฉ
-
Case C-406/10 SAS Institute Inc v World Programming Ltd, EU:C:2012:259, paras 40โ41 and 66. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 โฉโฉ
-
Case C-604/10 Football Dataco Ltd v Yahoo! UK Ltd, EU:C:2012:115, para 39. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0604 โฉ
-
Gottschalk v Benson, 409 U.S. 63 (1972). โฉ
-
The Register. (2001, September 11). World's first DeCSS executable prime number. https://www.theregister.com/2001/09/11/worlds_first_decss_executable_prime/ โฉ
-
Computerworld. (2007, May 3). Digg users are revolting, and 09f911029d74e35bd84156c5635688c0. https://www.computerworld.com/article/1497516/digg-users-are-revolting-and-09f911029d74e35bd84156c5635688c0.html โฉ
-
Borges, J. L. (1941). La biblioteca de Babel. In El jardรญn de senderos que se bifurcan. Sur. โฉ
-
Skala, M. (2004, June 10). What colour are your bits? https://ansuz.sooke.bc.ca/entry/23 โฉ
-
Francis Day & Hunter Ltd v Bron [1963] Ch 587 (CA). โฉ