Google LLC v. Oracle America, Inc.
The Supreme Court ruled that Google's copying of Oracle's Java programming code to build the Android smartphone platform was a legally permitted 'fair use,' ending a decade-long copyright battle worth billions of dollars.
The decision clarifies that copying a software interface — the part of a programming toolkit that lets developers invoke pre-built functions — can qualify as fair use when the copier builds a genuinely new product for a different computing environment rather than simply replacing the original.
“The result could well prove highly profitable to Oracle (or other firms holding a copyright in computer interfaces). But those profits could well flow from creative improvements, new applications, and new uses developed by users who have learned to work with that interface.”
The majority explaining why enforcing Oracle's copyright would reward programmers' investment, not Oracle's creativity.
How it got here: After a jury found fair use for Google on remand, the Federal Circuit reversed and held Google's copying was not fair use; Google then asked the Supreme Court to review both copyrightability and fair use, and the Court agreed to hear the case.
The Case in Depth
What happened
Oracle owns the copyright in Java SE, a programming platform used widely for desktop and laptop software. When Google built its Android mobile platform in the mid-2000s, it copied about 11,500 lines of Java's interface code — the part that lets programmers call up pre-written software functions using commands they already knew — so that the millions of developers familiar with Java could easily write Android apps. Google wrote its own underlying software but copied Oracle's organizational code to keep the command structure familiar. Oracle sued for copyright infringement, seeking billions in damages.
The question before the Court
When Google copied roughly 11,500 lines of Oracle's Java programming code to build its Android smartphone platform without a license, did copyright law permit it as a "fair use"?
The Court's answer
Yes — Google's copying was fair use. The Court assumed, without deciding, that Oracle's Java interface code is protected by copyright, then concluded that all four of the statutory factors used to analyze fair use point in Google's favor.
The copied interface code is a special kind of software whose value depends heavily on what programmers themselves invested in learning it, placing it further from the heart of copyright protection than most other code. Google's purpose was transformative: it used familiar commands not to reproduce Oracle's product but to let Java-trained developers work in an entirely new computing environment — smartphones — without starting from scratch. Google copied only 0.4 percent of the total Java platform, and only what was necessary for that goal. Finally, Android served a different market than Java SE; evidence showed Oracle was never positioned to succeed in the smartphone space on its own, and locking up the interface code would harm public creativity more than it would protect Oracle's investment.
Curious how the Court got there? See the step-by-step legal reasoning →
Why it matters
Software companies building platforms that need to work with tools programmers already know can, in the right circumstances, copy interface code without paying a licensing fee. The ruling removes a potential multi-billion-dollar damages award against Google and signals that copyright law will not give a single company a permanent lock on widely-used programming interfaces that the broader developer community depends on.
What changes now
The case is sent back to lower courts for proceedings consistent with the Supreme Court's ruling. Because the Court found fair use as a matter of law, the damages trial that the Federal Circuit had ordered will not take place for the copying at issue. Oracle's copyright claims against Google for the specific Java interface code in Android are resolved in Google's favor. The question of whether the code was copyrightable at all remains formally undecided and open for future cases.
What this does not decide
The ruling does not decide whether software interface code like Oracle's can actually be copyrighted — the Court only assumed it could for the sake of argument. The ruling also does not establish a general rule that copying any programming interface is fair use; the outcome depended on the specific facts of how Google copied and what it built.
Concurrences and dissents
Dissent — Justice Thomas
Justice Thomas argued the majority made a critical mistake by skipping the copyrightability question, which distorted the entire fair use analysis. In his view, three of the four fair use factors clearly favor Oracle: Google's copying was massively commercial, it used the code for the identical purpose Oracle did (not transformatively), and it wiped out Oracle's market — evidenced by Amazon negotiating a 97.5% discount on its Java license after Android launched. He would have held that Oracle's interface code is fully copyrightable and that Google's copying was not fair use.
How the Court got there
The legal reasoning, step by step
- The Court first resolved a threshold procedural question: who decides fair use? Fair use is a 'mixed question' — factual findings by a jury get deference, but the ultimate legal conclusion (whether those facts add up to fair use) is a question for judges to decide fresh, without deferring to the jury. The Court agreed with the Federal Circuit on this point and reviewed the fair use question de novo.
- Under the second statutory factor — the nature of the copyrighted work — the Court found that the copied 'declaring code' is a user interface whose value is inextricably tied to (1) uncopyrightable ideas about how to organize computing tasks and (2) the time programmers themselves invested in learning the system. Unlike most software, its worth comes largely from users' own labor, not the creator's. This places it further from the core of copyright protection than typical code, and this factor favors fair use.
- Under the first statutory factor — purpose and character of the use — the key question is whether the copying was 'transformative,' meaning it added something new with a different purpose. The Court found Google's use transformative: Google was not reproducing Oracle's desktop-and-laptop product. It was building a distinct platform for a different device category (smartphones), using new underlying software it wrote itself, and copying Oracle's interface only so programmers could bring their existing skills to that new environment.
- Under the third statutory factor — amount and substantiality — Google copied roughly 11,500 lines (virtually all the declaring code for 37 packages), but that was only 0.4 percent of the full Java platform. The Court reasoned that copying a larger share of a sub-component does not automatically weigh against fair use when the amount copied is tightly tied to a valid transformative purpose and does not capture the independently creative heart of the work. This factor also favors fair use.
- Under the fourth statutory factor — market effects — the Court found that Android was not a substitute for Java SE: the two products served different devices, and evidence showed Oracle had consistently failed to break into the smartphone market even before Android launched. The Court also warned that enforcing the copyright would risk 'locking up' interface code that an entire generation of programmers had built their careers around, diverting profits toward Oracle based on programmers' own investment rather than Oracle's creative contribution — the opposite of what copyright is meant to do.
- With all four factors pointing toward fair use — and with the Court stressing it was not rewriting copyright rules for other kinds of works — the Court concluded that Google's copying of the Java interface code was fair use as a matter of law, leaving no basis for Oracle's copyright claims to proceed to a damages trial.