Google LLC v. Oracle America, Inc.
The Supreme Court ruled that Google's copying of part of Oracle's Java programming interface was a lawful 'fair use,' meaning Google owed Oracle nothing for the code it took to build the Android smartphone platform.
The decision clarifies that copying the 'interface' layer of a software system — the shorthand commands developers use to call up prewritten tasks — can be protected as fair use when it lets an existing community of programmers work in a genuinely new computing environment rather than simply replacing the original product.
How it got here: A federal trial court found the API code uncopyrightable; the Federal Circuit reversed; on remand a jury found fair use for Google; the Federal Circuit reversed again; Google then asked the Supreme Court to review both copyrightability and fair use.
The Case in Depth
What happened
Oracle owns the copyright to Java SE, a programming platform used by millions of software developers on desktop and laptop computers. When Google built its Android smartphone platform starting around 2005, it copied roughly 11,500 lines of code from Java's Application Programming Interface — the set of shorthand commands that let programmers call up prewritten computing tasks — so that Java-trained developers could work with Android without learning an entirely new system. Google wrote its own code for all the underlying computing tasks.
The question before the Court
Did Google's copying of roughly 11,500 lines of Oracle's Java programming interface code to build its Android smartphone platform qualify as "fair use" under copyright law, shielding Google from paying damages?
The Court's answer
Yes — the Court held that Google's copying qualified as fair use under copyright law, meaning Google owed Oracle nothing for taking the 11,500 lines of Java API declaring code. Rather than decide whether the code was even copyrightable, the Court assumed it was and applied the four-factor fair-use test. All four factors pointed toward Google: the declaring code's tight link to uncopyrightable organizational ideas placed it at the outer edge of copyright's protection; Google's purpose — letting Java-trained programmers bring their skills to a new smartphone environment — was transformative; the 11,500 lines copied amounted to only 0.4% of the total Java code; and Android served a different market than Java SE while Oracle had never successfully entered the smartphone space.
The Court also emphasized that allowing Oracle to enforce its copyright here would risk turning the Java API into a legal lock blocking future programmers from building on widely adopted tools — the opposite of what copyright is designed to achieve.
Curious how the Court got there? See the step-by-step legal reasoning →
Why it matters
Software developers and technology companies now have clearer guidance that reusing a programming interface to bring an existing developer community into a new computing environment can qualify as fair use. This limits any software company's ability to use copyright to demand royalties whenever familiar programming commands are adapted for new devices, reducing the risk that widely-adopted tools become legal monopolies.
What changes now
The case is sent back to the lower courts with the fair-use question resolved in Google's favor, ending Oracle's copyright damages claim for the 37 Java API packages at issue in this lawsuit. The Court's ruling covers only Android versions released through November 2014, which were the subject of this suit. Future disputes about software interface copying will be analyzed under the same four-factor fair-use framework, applied to their own specific facts.
What this does not decide
The Court explicitly did not decide whether Oracle's Java API declaring code is protected by copyright at all — it only assumed so for purposes of the fair-use analysis. The ruling also does not establish a blanket rule that programming interfaces can always be freely copied; it applies the four-factor test to the specific facts of how and why Google copied this particular interface.
Concurrences and dissents
Dissent — Justice Thomas
Justice Thomas argued the Court should have first decided — and held — that Oracle's declaring code is fully copyrightable under the Copyright Act, which expressly protects code that operates 'directly or indirectly' in a computer. He contended that skipping copyrightability distorted the entire fair-use analysis. Applying the four factors properly, Thomas concluded that three decisively favor Oracle: Google's use was massively commercial, not transformative (same purpose in a new context is merely derivative, not transformative); Google copied the 'heart' of Oracle's work; and Google's copying devastated Oracle's actual and potential markets, erasing hundreds of millions in licensing revenue. He would have ruled for Oracle.
How the Court got there
The legal reasoning, step by step
- The Court declined to decide whether Oracle's API declaring code was copyrightable at all, choosing instead to assume it was and resolve only the fair-use question — reasoning that deciding no more than necessary was appropriate given fast-changing technology and business conditions.
- Because computer programs are primarily functional, the Court stressed that fair use plays an especially important role in keeping copyright monopolies within their proper limits for software — more so than for purely expressive works like novels or films.
- On the second statutory factor (the nature of the copyrighted work): the declaring code functions as a user interface inherently bound up with uncopyrightable ideas (the general system of organizing computing tasks) and with implementing code that Google independently wrote. This placed declaring code further from copyright's core, favoring fair use.
- On the first factor (purpose and character of the use): Google's copying was 'transformative' because it used the familiar Java commands not to replicate Java SE but to enable programmers to bring their existing skills to a fundamentally different computing environment — smartphones — through a new platform with all-new underlying code. The jury's factual findings supported this conclusion, though the ultimate fair-use question was one of law for the Court to decide independently.
- On the third factor (amount and substantiality): although Google copied virtually all of the declaring code for 37 packages (~11,500 lines), that was only 0.4% of the entire Java codebase. Google copied those lines not for their creativity but because programmers had already learned them; the amount was tethered to a valid, transformative purpose, so this factor favored fair use.
- On the fourth factor (market effects): evidence showed Android served a different market than Java SE (smartphones vs. desktops/laptops), Oracle was never positioned to succeed in the smartphone market, and enforcing Oracle's copyright would risk creating a legal 'lock' that stifled future programming creativity — harms that copyright is not meant to produce. Weighing all four factors, Google's copying was fair use as a matter of law.
Doctrinal impact
Cases affected by this decision
Reaffirms Campbell v. Acuff-Rose Music, Inc. (510 U. S. 569)
Reaffirmed as the Court's leading guide to applying all four statutory fair-use factors in a balanced, context-sensitive way.