Google LLC v. Oracle America, Inc., 593 U.S. ___, 141 S. Ct. 1183 (2021) (U.S. Supreme Court)
Google v. Oracle is the Supreme Court's most consequential modern decision at the intersection of software and copyright.
Assuming the Java API declaring code (including its structure, sequence, and organization) is copyrightable, was Google's copying of approximately 11,500 lines of that declaring code to create the Android platform a fair use under 17 U.S.C. § 107?
Under 17 U.S.C. § 107, fair use is a mixed question of law and fact evaluated by balancing four nonexclusive factors: (1) the purpose and character of the use, including whether it is of a commercial nature or is transformative; (2) the nature of the copyrighted work; (3) the amount and substantiality of the portion used relative to the copyrighted work as a whole; and (4) the effect of the use upon the potential market for or value of the copyrighted work. The ultimate fair-use determination is a legal judgment informed by historical, judicially developed equitable principles and the statute's objective to promote the Progress of Science and useful Arts. In the software context, particularly for API declaring code that is highly functional and closely tied to unprotectable ideas, methods of operation, and programmer learning, the second factor may weigh heavily in favor of fair use, and transformative uses that enable programmers to apply their accrued skills on new platforms may satisfy factor one. Commerciality is not dispositive, and copying no more than necessary to achieve a legitimate, transformative purpose can favor fair use. Courts must consider whether the challenged use acts as a market substitute or instead fosters creativity and innovation.
Yes. Assuming copyrightability, Google's copying of 11,500 lines of Java API declaring code to enable programmers to use their accumulated Java knowledge to write applications for Android was fair use as a matter of law. The Supreme Court reversed the Federal Circuit and reinstated the judgment for Google.
Google v. Oracle redefines how fair use applies to software and APIs. It signals that reimplementing functional interfaces for compatibility—when done to build new products and markets, copying only what is necessary, and without supplanting demand for the original—can be fair use as a matter of law. At the same time, the Court left unresolved whether API declaring code is copyrightable, ensuring continued doctrinal development on that threshold question. For law students, the case is a masterclass in applying the four fair-use factors to a nontraditional work, appreciating how function and interoperability shape the analysis, and understanding the standard of review for mixed questions. It also illustrates how copyright's constitutional purpose channels factor balancing and cautions against extending protection in ways that would stifle follow-on innovation.