PatentBrief

Patent Battle

Oracle vs Google

Is copying an API copyright infringement? Oracle claimed Google owed $9 billion for using Java APIs in Android. The Supreme Court said no — in one of the most consequential software IP decisions ever written.

At a Glance

Filed

August 2010

Court

N.D. California → Supreme Court

Oracle Sought

$9 billion

Duration

11 years

Outcome

Google wins (6-2)

The IP at Stake

US6,061,520Java Programming Language Compiler

Oracle's patent on the Java compiler — the mechanism that converts Java source code into bytecode that runs on the Java Virtual Machine. Google's Android used a modified Java compiler (eventually replaced by the Open JDK compiler) to generate Dalvik bytecode for Android's custom virtual machine.

Copyright: 37 Java API PackagesJava Standard Library Declaring Code

The more consequential claim: Oracle alleged that Google copied the declaring code for 37 Java API packages — approximately 11,500 lines of Java code that define the method signatures and class structure of the Java standard library. Google reimplemented these APIs so that Java programs could compile for Android with minimal changes.

US5,367,685Object-Oriented Language Virtual Machine Architecture

Sun Microsystems (acquired by Oracle) held patents on aspects of the JVM architecture. Google's Dalvik VM implemented a similar register-based virtual machine design to execute Android apps, though Google argued its approach was a clean-room implementation that did not infringe the specific claimed mechanisms.

The Timeline

August 2010

Oracle files suit

Oracle, having acquired Sun Microsystems for $7.4 billion in 2010, files suit in the Northern District of California alleging Google infringed Java patents and copyrights in Android. Oracle seeks $9 billion in damages.

May 2012

First jury trial: patent claims fail

A jury finds Google did not infringe Oracle's Java patents. On the copyright question — whether the Java API declarations are copyrightable — the jury deadlocks. Judge William Alsup rules the APIs are not copyrightable: "To accept Oracle's claim would be to allow anyone to monopolize a language."

May 2014

Federal Circuit reverses: APIs are copyrightable

The Court of Appeals for the Federal Circuit reverses Judge Alsup on the copyright question, ruling that the structure, sequence, and organization of the Java API packages are copyrightable. The case is remanded for a fair use trial.

May 2016

Second trial: jury finds fair use

A second jury trial focuses on fair use — whether Google's use of the Java API declarations was permissible even if copyrightable. The jury finds in Google's favor on fair use, ruling Android's use of the Java APIs was transformative.

March 2018

Federal Circuit reverses again: not fair use

The Federal Circuit reverses the fair use finding as a matter of law — an unusual move that takes the fair use question away from the jury. Oracle appeals for Supreme Court review.

April 2021

Supreme Court rules 6-2 for Google

In Google LLC v. Oracle America, the Supreme Court rules 6-2 that Google's use of the Java API declarations was fair use. The Court analyzes all four fair use factors, finding Google's use was transformative — creating a new platform rather than replacing Oracle's Java market. The majority opinion, written by Justice Breyer, explicitly declines to rule on whether APIs are copyrightable at all.

The Outcome

Google wins 6-2. Oracle gets nothing. The API ecosystem survives.

The Supreme Court's 2021 ruling was a complete victory for Google and a decisive loss for Oracle. The Court held that Google's use of the 11,500 lines of Java API declaring code was fair use — analyzing all four factors and finding the use transformative because Android represented a new platform rather than a replacement for Sun's Java products.

Crucially, the Court declined to rule on whether APIs are copyrightable at all — leaving that question officially unresolved. This strategic narrowness allowed the Court to decide the case without creating broad precedent that might affect other areas of copyright law. Practically, however, the fair use ruling means that reimplementing an API for a transformative purpose is legally safe — a ruling that protects open-source reimplementations, interoperability projects, and competitive software development.

What It Changed

01

Protected API Interoperability and Open Source

The ruling provides a legal safe harbor for projects that reimplement APIs to achieve compatibility — like OpenJDK, Wine (reimplementing Windows APIs on Linux), and ReactOS. Without a favorable ruling, the practice of reimplementing APIs to enable cross-platform compatibility would have faced significant legal risk.

02

Defined Fair Use for Transformative Software Platforms

The Court's analysis established that creating a new computing platform that incorporates existing API declarations can be transformative fair use — even if the new platform commercially competes with the original. This framework is now the controlling precedent for software fair use analysis in the United States.

03

Ended the Oracle-Java Licensing Threat to Android

Oracle had sought $9 billion — a sum that would have fundamentally changed Android's economics and potentially forced Google to pay licensing fees that would flow through to Android device manufacturers and ultimately consumers. The ruling removed this threat permanently, securing Android's position as a zero-cost platform for device manufacturers.

From PatentBrief

Explore related patents on PatentBrief →

Search Java, Android, and software platform patents in the full USPTO database. Read any patent in plain English — including the ones at the center of this case.

Search Java patentsAll patent battles →