Last updated: 2026-11-18

U
Undergraduate level
APL
Applied / Methodological โ€” Knowledge with a 5โ€“10 year half-life โ€” stable practice

SAS v World Programming: What Copyright Protects in Software

Can you build a program that does everything a competitor's program does, runs its customers' scripts and reads its data files, without infringing anything? In the UK, largely yes, provided you never copy its code and are careful with its documentation. The case that established this, SAS Institute Inc v World Programming Ltd, ran from 2009 to 2020 through the High Court, the Court of Justice of the European Union (CJEU), the Court of Appeal and several US courts.

This page sets out the facts, then follows the case through five questions: what copyright in a program protects, what copyright in a manual protects, what a licence can forbid, whom a click-through licence binds, and what happens when another country's law disagrees. It ends with what the case means for building compatible software.

The Facts FoundationalKnowledge that endures for decades โ€” core principles

SAS Institute makes analytical software (the SAS System) whose core lets users write programs, called scripts, in the SAS Language. Its customers had written thousands of such scripts, and a customer who wanted to change supplier "would be faced with re-writing its existing application programs in a different language"1. World Programming Ltd (WPL) built the World Programming System (WPS) to run those scripts and produce the same outputs from the same inputs.

WPL's developers studied the SAS manuals and the behaviour of the SAS Learning Edition, a cheap version sold for learning. It was common ground that "none of the developers of WPS have ever had access to the source code of any of the SAS System" and that none had decompiled it. One of WPS's principal developers estimated that about 90% of its source code did not relate to the SAS manuals at all1.

DateCourtOutcome
July 2010High Court (Arnold J)Facts found; limited infringement by the WPS manual; questions referred to the CJEU
May 2012CJEU, Case C-406/10Functionality, programming language and data file formats are not protected expression; licensees may observe, study and test
January 2013High Court (Arnold J)All claims dismissed except the limited manual-to-manual infringement
November 2013Court of Appeal (Lewison LJ)SAS's appeal dismissed
2015โ€“2017North Carolina and the Fourth CircuitSAS wins on contract, fraud and unfair trade practices: about US$79 million
2018โ€“2020High Court (Cockerill J); Court of Appeal (Males LJ)US judgment not enforceable in England; injunctions limiting US enforcement against UK-held funds
April 2023US Federal CircuitSAS's separate US copyright claim fails

SAS argued that reproducing its programs' functions, language and file formats copied the programs indirectly. The CJEU disagreed: "neither the functionality of a computer program nor the programming language and the format of data files used in a computer program in order to exploit certain of its functions constitute a form of expression of that program". Protecting functionality "would amount to making it possible to monopolise ideas, to the detriment of technological progress and industrial development"2.

The Court drew the line at the code. If a competitor obtained "the part of 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 liable to constitute partial reproduction"2. Studying behaviour is lawful; copying the implementation is not.

SAS also claimed the SAS Language as a copyright work in its own right. Arnold J's view was that a programming language "is not capable of being a work": dictionaries and grammars describe a language, but the language itself "is a system of rules for the generation and recognition of meaningful statements". Nor does being an intellectual creation make something a work, since "there are many intellectual creations which are not works, such as scientific theories"3.

WPL admitted the SAS manuals were copyright works. The question was what it could take from them. The CJEU said keywords, syntax, commands, options and defaults, "considered in isolation, are not, as such, an intellectual creation of the author"; it is "only through the choice, sequence and combination of those words, figures or mathematical concepts that the author may express his creativity in an original manner"2.

WPS itself did not infringe. The Court of Appeal adopted the Advocate General's summary, "The WPL System does not reproduce the description [in the SAS Manuals] of those statistical operations but simply executes them", and added that "the functionality of a computer program is, quite simply, not a form of expression at all"4.

WPL's own manual partly did. Arnold J accepted that its writers did not copy from an open book, and that similar language was to be expected when describing identical functions. Even so, "WPL's writers had the language of the SAS Manuals firmly in their minds when writing the WPS Manual entries. Although they tried to avoid describing the functions in the same language, they did not succeed"1. By the time of the appeal WPL had withdrawn that manual and was having a new one written from scratch4.

Note well. Behaviour can be studied and reproduced freely. Wording can't be carried across, even from memory. In this case the documentation, not the code, was where the infringement happened.

What a Licence Can Forbid Applied / MethodologicalKnowledge with a 5โ€“10 year half-life โ€” stable practice

Each copy of the Learning Edition came with a click-through licence: "By clicking on the 'Yes' button, the individual licensing the Software ('Customer') agrees to these terms". It allowed use "on one (1) workstation at a time, for Customer's [own self-training] non-production purposes only"4. Arnold J read "non-production" to mean WPL "must not use the Learning Edition to produce anything, but only to learn about the SAS Language", so using it to compare outputs, test WPS and tune performance was outside the licence as written1.

The statute overrode the contract. Section 50BA of the Copyright, Designs and Patents Act 1988 (CDPA) allows a lawful user "to observe, study or test the functioning of the program in order to determine the ideas and principles which underlie any element of the program if he does so while performing any of the acts of loading, displaying, running, transmitting or storing the program which he is entitled to do", and section 296A makes void any term that "purports to prohibit or restrict" that5. The CJEU held that copyright "cannot be infringed where, as in the present case, the lawful acquirer of the licence did not have access to the source code โ€ฆ but merely studied, observed and tested that program in order to reproduce its functionality in a second program"2. The Court of Appeal put the distinction as one between acts and purposes: "Once you have crossed the threshold of being entitled to perform acts for any purpose specified in the licence, article 5(3) permits you to perform those same acts for a purpose that falls within article 5(3)"4.

Whom a Click-Through Licence Binds Applied / MethodologicalKnowledge with a 5โ€“10 year half-life โ€” stable practice

Arnold J held that "Customer" meant the individual employee who clicked "Yes", so colleagues using the same copy were outside the licence. The Court of Appeal disagreed. Lewison LJ accepted that "only a human being can click on the 'Yes' button", but "individual" could mean a single person, including a company; the clicker could act as the company's agent; the licence called the Customer "it" and assumed the Customer paid; and SAS itself said its agreement was with WPL. Then he added the point that settles most arguments over standard terms:

"Finally, one cannot forget that the licence agreement is offered on a take-it-or-leave-it basis. The purchaser has only two choices: click on the 'Yes' button or click on the 'No' button. There is no room for negotiation. If there were any doubt about the meaning of the licence at this stage, in my judgment the application of the contra proferentem principle would tip the balance in WPL's favour."4

Under contra proferentem, ambiguity in a contract is resolved against the party who drafted it. The Court also held that the trial judge had pushed background too far by relying on SAS's website, since "simply because something is available on the internet does not mean that it is relevant background"4.

When Another Country's Law Disagrees Ephemeral / ToolingKnowledge that evolves in months to a year โ€” check for updates

The licence chose North Carolina law, and SAS sued there too. The US court held it was "under no obligation to apply the Software Directive because the licence was governed by an express choice of North Carolina law" and granted summary judgment for breach of contract; SAS's copyright claims there were dismissed. A jury then found WPL liable for fraud, on the theory that it had impliedly promised to abide by the terms the English court had held void, and for unfair trade practices. Damages of about US$26 million were trebled to about US$79 million6.

The English courts refused to enforce it. Cockerill J held the void licence terms were "a fundamental building block" of the fraud claim and refused enforcement on grounds including issue estoppel, abuse of process, public policy and section 5 of the Protection of Trading Interests Act 1980, which bars enforcing multiple-damages awards76. In 2020 the Court of Appeal restrained SAS from seeking US orders over funds held in UK banks and over debts owed by some non-US customers6. A later US copyright action, brought in Texas, failed because SAS could not identify protectable elements once unprotectable ones were filtered out; the Federal Circuit affirmed in 20238.

The copyright outcome was much the same on both sides of the Atlantic. The difference came from contract law and the licence's choice of law.

What This Means When You Build Something Compatible Applied / MethodologicalKnowledge with a 5โ€“10 year half-life โ€” stable practice

  • Never look at the competitor's source code, and don't decompile unless the strict conditions of CDPA s.50B are met. WPL's case rested on this.
  • Study behaviour freely if you're a lawful user. Terms that forbid observing, studying or testing are void in the UK.
  • Write your own documentation from your own specification, by people who haven't been steeped in the competitor's wording. See the clean-room discussion in Making More of Your Output Protectable.
  • Check the governing law of any licence you accept. A term void in England may be enforced elsewhere, and so may damages for breaching it.
  • If you draft licence terms, draft them clearly. Standard terms are read against their author when unclear.

References


  1. SAS Institute Inc v World Programming Ltd [2010] EWHC 1829 (Ch), paras 2, 69, 72, 148 and 286. https://caselaw.nationalarchives.gov.uk/ewhc/ch/2010/1829 โ†ฉโ†ฉโ†ฉโ†ฉ

  2. Case C-406/10 SAS Institute Inc v World Programming Ltd, EU:C:2012:259, paras 39โ€“46, 61 and 66โ€“67. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 โ†ฉโ†ฉโ†ฉโ†ฉ

  3. SAS Institute Inc v World Programming Ltd [2013] EWHC 69 (Ch), paras 33โ€“34. https://caselaw.nationalarchives.gov.uk/ewhc/ch/2013/69 โ†ฉ

  4. SAS Institute Inc v World Programming Ltd [2013] EWCA Civ 1482, paras 63, 78, 90, 91, 101 and 105โ€“108. https://caselaw.nationalarchives.gov.uk/ewca/civ/2013/1482 โ†ฉโ†ฉโ†ฉโ†ฉโ†ฉโ†ฉ

  5. Copyright, Designs and Patents Act 1988, ss.50B, 50BA and 296A. https://www.legislation.gov.uk/ukpga/1988/48/contents โ†ฉ

  6. SAS Institute Inc v World Programming Ltd [2020] EWCA Civ 599, paras 15โ€“20 and 137. https://caselaw.nationalarchives.gov.uk/ewca/civ/2020/599 โ†ฉโ†ฉโ†ฉ

  7. SAS Institute Inc v World Programming Ltd [2018] EWHC 3452 (Comm). https://caselaw.nationalarchives.gov.uk/ewhc/comm/2018/3452 โ†ฉ

  8. SAS Institute Inc v World Programming Ltd, 64 F.4th 1319 (Fed. Cir. 2023). โ†ฉ