Google LLC v. Oracle America, Inc.
The Supreme Court ruled that Google's copying of part of Oracle's Java programming system to build Android was a legally permitted 'fair use,' ending a decade-long copyright battle worth billions of dollars.
The decision is a significant victory for the software industry, setting important limits on how far copyright law reaches into the functional code that programmers rely on to move their skills from one platform to another.
How it got here: After the Federal Circuit reversed a jury's fair use verdict in Google's favor, Google 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
Google, building its Android platform for smartphones, copied about 11,500 lines of code from Oracle's Java programming system — specifically the "declaring code" that connects a programmer's commands to prewritten computing tasks. Google did this so that the millions of developers already familiar with Java could use Android without learning an entirely new system. Oracle, which acquired Java creator Sun Microsystems in 2010, sued Google for copyright infringement and sought billions of dollars in damages.
The question before the Court
Did Google infringe Oracle's copyright when it copied about 11,500 lines of Java programming code to make Android easier for experienced developers to use?
The Court's answer
No — Google's copying was a legally permissible "fair use" and therefore did not violate copyright law. The Court applied the four-factor fair use test and concluded that all four factors favored Google. The copied code was a functional user interface bound up with uncopyrightable ideas, Google's purpose was transformative (building a new smartphone platform rather than reproducing the original), the amount copied was small relative to the full Java system and tied to that valid purpose, and the smartphone market Google entered was distinct enough from Oracle's primary desktop market that no cognizable harm resulted.
The Court deliberately left open whether Oracle's Java API code is protected by copyright at all, deciding only the fair use question. It also said explicitly that it was not overturning its prior fair use decisions involving parody, journalism, or other creative works.
Curious how the Court got there? See the step-by-step legal reasoning →
Why it matters
Software companies that build new platforms using established programming interfaces — the standard connection points developers already know — face far less copyright liability risk, as long as copying is limited and serves a genuinely new purpose. Programmers can carry their skills across platforms without starting over. Companies holding copyrights in widely adopted programming tools have less ability to demand payment simply because others find those tools convenient.
What changes now
With the fair use ruling in Google's favor, Oracle's copyright claims are defeated and the case returns to lower courts only for proceedings consistent with the Supreme Court's ruling — effectively ending the copyright litigation. The decision does not resolve whether Oracle's Java API code is copyrightable, leaving that question open for future cases. The ruling also does not address more recent Android versions, which were not at issue.
What this does not decide
The Court does not decide whether Oracle's Java API code is protected by copyright at all — it only assumes so for purposes of argument. The ruling also does not disturb prior fair use decisions in other areas such as parody, journalism, or 'knockoff' products, which the Court explicitly says it is not overturning. It does not address Android versions released after November 2014.
Concurrences and dissents
Dissent — Justice Thomas
Justice Thomas argued the majority gets the analysis backward by skipping copyrightability. He would hold Oracle's declaring code is clearly protected by copyright, because Congress expressly included both direct and indirect computer instructions in the Copyright Act. On fair use, he contended three of four factors decisively favor Oracle: Google's use was overwhelmingly commercial and non-transformative, Google copied the heart of Oracle's work verbatim, and the market harm to Oracle — including a 97.5% collapse in one licensing deal and the elimination of Oracle's smartphone licensing opportunities — was enormous and largely ignored by the majority.
How the Court got there
The legal reasoning, step by step
- The Court set aside the copyrightability question — whether Oracle's Java API code can be protected by copyright — and assumed for purposes of argument that it can. This focused the entire analysis on a single question: whether Google's copying was 'fair use,' the legal doctrine that permits copying without permission in certain circumstances. The Court reasoned that resolving the case on fair use grounds was more appropriate given rapidly changing technological and business conditions.
- On the standard of review, the Court agreed with the Federal Circuit that fair use is a mixed question. Juries determine underlying facts (like how much was copied or what the market impact was), but the ultimate question of whether those facts add up to fair use is a legal question that judges decide independently, without deferring to the jury's verdict. The Seventh Amendment right to a jury trial does not include the right to have a jury resolve a fair use defense.
- On the first factor — the nature of the copyrighted work — the Court found it favored Google. The copied 'declaring code' is a user interface inextricably bound up with uncopyrightable ideas (the general organization of computing tasks) and with Google's own independently written implementing code. Its value is partly derived from programmers' own investment in learning it, not just Oracle's creative effort. This places it further from the core of copyright protection than most programs.
- On the second factor — the purpose and character of the use — the Court found Google's copying 'transformative.' Google did not simply reproduce Oracle's code; it used familiar Java commands as a bridge to let programmers apply existing skills to a wholly new smartphone platform running entirely new underlying code. This goal of enabling programmers to build new creative work in a new environment is consistent with copyright's constitutional purpose of promoting creative progress.
- On the third factor — the amount copied — the Court found it favored Google. Although 11,500 lines sounds large, it was only 0.4% of the full Java API. Google copied only what was necessary to allow programmers to use their accumulated knowledge in the new Android environment. When copying is tethered to a valid, transformative purpose, the amount copied generally weighs in favor of fair use.
- On the fourth factor — market effect — the Court found it also favored Google. Sun (Oracle's predecessor) was poorly positioned to compete in the smartphone market and had been failing to break into it before Android arrived. Part of the revenue Oracle stood to gain reflected programmers' own investment in learning Java, not Oracle's creative output. And blocking Google's use risked harming the public by letting Oracle effectively lock up a widely learned interface, interfering with future creativity rather than incentivizing it.
Doctrinal impact
Cases affected by this decision
Reaffirms Campbell v. Acuff-Rose Music, Inc. (510 U. S. 569)
The Court relies on Campbell's transformative-use framework and four-factor balancing as the governing fair use standard.
Reaffirms Harper & Row, Publishers, Inc. v. Nation Enterprises (471 U. S. 539)
Reaffirmed as foundational fair use authority, including its guidance on mixed questions of fact and law.