Google LLC v. Oracle America, Inc.
The Supreme Court ruled that Google's copying of Oracle's Java programming interface to build its Android smartphone platform was lawful 'fair use,' ending a decade-long copyright battle over billions of dollars.
The decision gives software developers and technology companies more room to reuse programming interfaces — the technical bridges that let programmers apply existing skills on new platforms — without automatically triggering copyright liability.
How it got here: The Federal Circuit held Oracle's API was copyrightable and reversed a jury finding of fair use; Google petitioned the Supreme Court to review both rulings, and the Court agreed to hear the case.
The Case in Depth
What happened
Oracle owns the copyright to Java SE, a widely used software platform built around the Java programming language. Google, constructing its Android smartphone operating system starting around 2005, copied roughly 11,500 lines of Java's programming interface code — the "declaring code" that lets programmers invoke pre-written software tasks using commands they already know. Google copied this code so that the millions of Java-trained programmers could build Android apps without learning an entirely new system from scratch. Oracle sued Google for copyright infringement, setting off more than a decade of litigation.
The question before the Court
When Google copied thousands of lines of Java programming interface code so that developers could build Android smartphone apps using skills they already had, did that copying count as lawful "fair use" under copyright law?
The Court's answer
Yes — Google's copying was lawful fair use. The Court assumed for argument's sake that Oracle's Java interface code could be copyrighted, then applied the four-factor fair use test and found all four factors favored Google.
The nature of the copied code mattered: declaring code sits at the edges of copyright protection because its value comes largely from programmers' own investment in learning it, not solely from Oracle's creative expression. Google's purpose was transformative — not replicating Java in the same market, but building an entirely new smartphone computing environment. The amount copied (about 0.4% of Oracle's total API) was no more than necessary for that purpose. And the market evidence showed Android was not a substitute for Java SE, while enforcing the copyright risked locking programmers' accumulated skills behind Oracle's control, harming future innovation rather than protecting legitimate creative investment.
Curious how the Court got there? See the step-by-step legal reasoning →
Why it matters
Software developers and tech companies can now point to this ruling when copying programming interfaces to build new platforms. If a company takes only what is needed to let programmers apply skills they already have — in a genuinely new computing environment — that copying is more likely to be protected as fair use. Oracle cannot collect billions in copyright damages from Google for the copying at issue.
What changes now
The Federal Circuit's judgment is reversed and the case is returned to lower courts for further proceedings consistent with the Supreme Court's ruling. Because the Court found fair use as a matter of law, Oracle cannot recover copyright damages from Google for the copying at issue. The Court deliberately left open whether API declaring code is copyrightable at all, so that question remains unresolved for future cases involving different facts.
What this does not decide
The Court explicitly did not decide whether Oracle's Java API code is protected by copyright law in the first place — it only assumed copyrightability for the sake of argument. The ruling also does not address whether copying programming interfaces will be fair use in other factual settings; the decision is tied to these specific circumstances.
Concurrences and dissents
Dissent — Justice Thomas
Justice Thomas would first hold that Oracle's declaring code is clearly copyrightable — Congress expressly protected computer code that brings about results 'indirectly,' which is exactly what declaring code does. He argues the majority's fair use analysis is distorted by its refusal to resolve copyrightability first. On the merits, he finds three of four factors decisively favor Oracle: the market effects factor (the most important) shows Google devastated Oracle's licensing market; the use was overwhelmingly commercial and not truly transformative; and Google copied the qualitative heart of Oracle's work. The majority's ruling, he warns, makes it nearly impossible to enforce copyright protection over declaring code going forward.
How the Court got there
The legal reasoning, step by step
- The Court declined to decide whether Oracle's API code is even protected by copyright, because a ruling for Google on fair use would resolve the entire case. Assuming the code is copyrightable, the Court applied the four-factor fair use test — the legal framework courts use to decide when copying a protected work is nonetheless permissible.
- The Court first clarified the standard of review: fair use is a mixed question of fact and law. Juries decide disputed underlying facts (such as whether markets were harmed), but the ultimate legal question — whether those facts add up to fair use — is for judges to decide independently without simply deferring to a jury's verdict.
- On the 'nature of the copyrighted work' (factor 2): The declaring code is an unusual kind of code — a user-facing interface bound together with uncopyrightable ideas (the organizational system) and Google's independently written implementing code. Its value derives largely from programmers' own investment in learning it rather than from Oracle's expressive choices alone, placing it at the edges of copyright protection and pointing toward fair use.
- On 'purpose and character' (factor 1): Google's copying was transformative — it did not replicate Java to compete in Oracle's existing desktop/laptop market, but used the familiar interface as a key to unlock programmers' existing skills in an entirely new smartphone computing environment. That purpose aligned with copyright's constitutional goal of promoting creative progress, even though the copying was admittedly commercial.
- On 'amount and substantiality' (factor 3): The 11,500 copied lines were only 0.4% of Oracle's total API code, and Google copied them not for their creative expression but because programmers had already learned to use them. The Court held that when the amount of copying is tethered to a valid, transformative purpose, this factor generally favors fair use.
- On 'market effects' (factor 4): The record showed Android served a distinct smartphone market while Java SE targeted desktops and laptops; Sun had struggled to enter mobile even before Android existed; and enforcing the copyright would risk letting Oracle lock up the accumulated skills of millions of programmers — harming future innovation rather than protecting the creative investment that copyright is designed to reward. All four factors together compelled a finding of fair use as a matter of law.