Google LLC v. Oracle America, Inc.
The Supreme Court ruled that Google's copying of part of Oracle's Java software — the portion that lets programmers call up prewritten tasks using commands they already know — was a lawful 'fair use,' ending a decade-long copyright dispute and clearing Google of liability.
The decision signals that reusing a programming interface's code to allow developers to work in a new computing environment can be legally permissible without a license, with broad implications for how the software industry builds on existing platforms.
How it got here: After a lengthy trial history, the Federal Circuit ruled Oracle's API was copyrightable and that Google's copying was not fair use; Google petitioned the Supreme Court, which agreed to review both questions.
The Case in Depth
What happened
Oracle owns the copyright to Java SE, a widely used software platform. When Google built its Android mobile operating system, it copied about 11,500 lines of Java's Application Programming Interface (API) — specifically the "declaring code" that lets programmers invoke prewritten tasks using familiar commands — so that millions of Java-trained developers could work on Android without learning an entirely new system. Google wrote its own underlying task-executing code but copied Oracle's organizational structure and command labels for 37 Java packages.
The question before the Court
Did Google's copying of roughly 11,500 lines of Java programming interface code to build its Android smartphone platform count as legally permissible "fair use" under copyright law?
The Court's answer
Yes — the Court held that Google's copying was a fair use of Oracle's Java API as a matter of law. The Court assumed (without deciding) that the copied code was protected by copyright, then applied all four factors of the statutory fair use test, finding each one favored Google. The declaring code was a functional user interface tied to uncopyrightable ideas, placing it further from copyright's creative core than most works. Google's purpose was transformative — creating a new smartphone platform for a computing environment fundamentally different from Java's original desktop context. The 11,500 lines copied were only 0.4% of the total Java API and were taken only to give programmers familiar tools in the new environment. And Android was not a market substitute for Java SE; enforcing Oracle's copyright would risk turning a widely-learned interface into a "lock" on future software development — a harm to public creativity that copyright law is not designed to impose.
Curious how the Court got there? See the step-by-step legal reasoning →
Why it matters
Software companies building new platforms can now point to this ruling when arguing that copying familiar programming interfaces to attract developers is legally permissible fair use. The decision may lower barriers to platform innovation but could also reduce the financial incentive for companies to invest in creating widely adopted programming interfaces, since competitors may be able to reuse them without paying.
What changes now
The Federal Circuit's ruling against Google is reversed and the case is sent back for further proceedings. Because the Court found fair use as a matter of law, Google does not owe Oracle damages for copying the API. The Court expressly did not decide whether Oracle's Java API code is copyrightable, leaving that question open. Future disputes over similar API copying — particularly for more recent software — will need to be litigated under the same fair use framework the Court applied here.
What this does not decide
The Court expressly declined to rule on whether Oracle's Java API code is actually protected by copyright, leaving that question entirely open. The decision also does not overturn existing fair use precedents involving knockoffs, journalism, or parody, and is limited to the specific facts of reusing a programming interface to enable developers to work in a new computing environment.
Concurrences and dissents
Dissent — Justice Thomas
Justice Thomas argued the Court should have first decided — and answered yes — whether Oracle's declaring code is copyrightable, because that threshold question shapes the entire fair use analysis. Skipping it, he said, allowed the majority to improperly treat declaring code as less worthy of protection than implementing code, a distinction Congress rejected. Thomas concluded that three of the four fair use factors clearly favored Oracle: Google's use was overwhelmingly commercial and not transformative, it copied the 'heart' of Oracle's work, and it decimated Oracle's market — wiping out billions in licensing revenue. Only the nature-of-the-work factor possibly favored Google, and that alone cannot legally establish fair use.
How the Court got there
The legal reasoning, step by step
- The Court first resolved who decides fair use: judges, not juries alone. Fair use is a 'mixed question' — juries determine the underlying facts (such as how much was copied and what the market looked like), but judges decide de novo, meaning fresh and without deference, whether those facts legally add up to fair use. This does not violate the Seventh Amendment's jury trial guarantee because the ultimate fair-use question is legal in nature, not factual.
- Turning to the four-factor fair use test in §107 of the Copyright Act, the Court began with the 'nature of the copyrighted work.' The declaring code at issue functions as a user interface — inextricably tied to uncopyrightable ideas (the organizational system of tasks) and deriving much of its value from the time programmers invested learning it rather than from Oracle's own creative choices. This placed it further from copyright's creative core than most works, weighing in favor of fair use.
- For the 'purpose and character' factor, the Court asked whether Google's copying was 'transformative' — adding something new rather than simply duplicating the original. Google copied the API to build a new smartphone platform, letting millions of Java-trained programmers bring their existing skills to a fundamentally different computing environment. Although Google used the code for a similar technical function, its broader purpose — enabling a new creative platform for smartphones — advanced copyright's constitutional goal of promoting progress and was therefore transformative.
- The third factor — the amount and substantiality of what was copied — also favored Google. The 11,500 copied lines were virtually all of the declaring code for 37 packages, but only 0.4% of the Java API's 2.86 million total lines. More importantly, the Court held that when the amount copied is directly tied to a valid, transformative purpose — here, taking only what was needed so programmers would not have to abandon familiar tools when building for smartphones — this factor weighs toward fair use.
- The fourth factor — effect on the market for Oracle's work, often the most important consideration — favored Google as well. Android served a distinct advanced smartphone market, not a substitute for Java SE's laptop and desktop market; Sun was already struggling to enter smartphones before Android launched; and Sun's own executives had viewed broad use of Java as a benefit. Finally, allowing Oracle to enforce its copyright would risk turning the widely-learned declaring code into a 'lock' blocking future software creativity — a public harm copyright law is not meant to cause.
Doctrinal impact
Cases affected by this decision
Reaffirms Campbell v. Acuff-Rose Music, Inc. (510 U. S. 569)
Reaffirmed as the controlling framework for applying the four-factor fair use test, especially transformative use.