This appeal presents the question of whether distributors of peer-to-peer file-sharing computer networking software may be held contributorily or vicariously liable for copyright infringements by users. Under the circumstances presented by this case, we conclude that the defendants are not liable for contributory and vicarious copyright infringement and affirm the district court’s partial grant of summary judgment.
*1158 I. Background
From the advent of the player piano, every new means of reproducing sound has struck a dissonant chord with musical copyright owners, often resulting in federal litigation. This appeal is the latest reprise of that recurring conflict, and one of a continuing series of lawsuits between the recording industry and distributors of file-sharing computer software.
The plaintiffs in the consolidated cases (“Copyright Owners”) are songwriters, music publishers, and motion picture studios who, by their own description, “own or control the vast majority of copyrighted motion pictures and sound recordings in the United States.”
1
Defendants Grokster Ltd. and StreamCast Networks, Inc. (“Software Distributors”) are companies that freely distribute software that allows users to share computer files with each other, including digitized music and motion pictures. The Copyright Owners allege that over 90% of the files exchanged through use of the “peer-to-peer” file-sharing software offered by the Software Distributors involves copyrighted material, 70% of which is owned by the Copyright Owners. Thus, the Copyright Owners argue, the Software Distributors are liable for vicarious and contributory copyright infringement pursuant to 17 U.S.C. §§ 501-13 (2000), for which the Copyright Owners are entitled to monetary and in-junctive relief. The district court granted the Software Distributors partial summary judgment as to liability arising from present activities and certified the resolved questions for appeal pursuant to Fed. R.Civ.P. 54(b).
Metro-Goldwyn-Mayer Studios, Inc. v. Grokster, Ltd.,
To analyze the legal issues properly, a rudimentary under-standing of the peer-to-peer file-sharing software at issue is required — particularly because peer-to-peer file sharing differs from typical internet use. In a routine internet transaction, a user will connect via the internet with a website to obtain information or transact business. In computer terms, the personal computer used by the consumer is considered the “client” and the computer that hosts the web page is the “server.” The client is obtaining information from a centralized source, namely the server.
In a peer-to-peer distribution network, the information available for access does not reside on a central server. No one computer contains all of the information that is available to all of the users. Rather, each computer makes information available to every other computer in the peer-to-peer network. In other words, in a peer-to-peer network, each computer is both a server and a client.
Because the information is decentralized in a peer-to-peer network, the software must provide some method of cataloguing the available information so that users may access it. The software operates by connecting, via the internet, to other users of the same or similar software. At any given moment, the network consists of other users of similar or the same software online at that time. Thus, an index of files available for sharing is a critical component of peer-to-peer file-sharing networks.
At present, there are three different methods of indexing: (1) a centralized indexing system, maintaining a list of available files on one or more centralized servers; (2) a completely decentralized indexing system, in which each computer maintains a list of files available on that *1159 computer only; and (3) a “supernode” system, in which a select number of computers act as indexing servers. 2
The first Napster system employed a proprietary centralized indexing software architecture in which a collective index of available files was maintained on servers it owned and operated. A user who was seeking to obtain a digital copy of a recording would transmit a search request to the Napster server, the software would conduct a text search of the centralized index for matching files, and the search results would be transmitted to the requesting user. If the results showed that another Napster user was logged on to the Napster server and offering to share the requested recording, the requesting user could then connect directly with the offering user and download the music file. 3
Under a decentralized index peer-to-peer file-sharing model, each user maintains an index of only those files that the user wishes to make available to other network users. Under this model, the software broadcasts a search request to all the computers on the network and a search of the individual index files is conducted, with the collective results routed back to the requesting computer. This model is employed by the Gnutella software system and is the type of architecture now used by defendant StreamCast. Gnutella is open-source software, meaning that the source code is either in the public domain or is copyrighted and distributed under an open-source license that allows modification of the software, subject to some restrictions.
The third type of peer-to-peer file-sharing network at present is the “supernode” model, in which a number of select computers on the network are designated as indexing servers. The user initiating a file search connects with the most easily accessible supernode, which conducts the search of its index and supplies the user with the results. Any computer on the network could function as a supernode if it met the technical requirements, such as processing speed. The “supernode” architecture was developed by KaZaa BV, a Dutch company, and licensed under the name of “Fast-Track” technology. 4
Both Grokster and StreamCast initially used the FastTrack technology. However, StreamCast had a licensing dispute with KaZaa, and now uses its own branded “Morpheus” version of the open-source Gnutella code. StreamCast users connect to other users of Gnutella-based peer-to-peer file-sharing software. 5 Both Grokster *1160 and StreamCast distribute their separate softwares free of charge. Once downloaded onto a user’s computer, the software enables the user to participate in the respective peer-to-peer file-sharing networks over the internet. 6
Users of the software share digital audio, video, picture, and text files. Some of the files are copyrighted and shared without authorization, others are not copyrighted (such as public domain works), and still others are copyrighted, but the copyright owners have authorized software users in peer-to-peer file-sharing networks to distribute their work. The Copyright Owners assert, without serious contest by the Software Distributors, that the vast majority of the files are exchanged illegally in violation of copyright law.
II. Analysis
The question of direct copyright infringement is not at issue in this case. Rather, the Copyright Owners contend that the Software Distributors are liable for the copyright infringement of the software users. The Copyright Owners rely on the two recognized theories of secondary copyright liability: contributory copyright infringement and vicarious copyright infringement. Ellison v. Robertson, 357 F.3d 1072, 1076(9th Cir.2004). We agree with the district court’s well reasoned analysis that the Software Distributors’ current activities do not give rise to liability under either theory.
A Contributory Copyright Infringement
The three elements required to prove a defendant liable under the theory of contributory copyright infringement are: (1) direct infringement by a primary infringer, (2) knowledge of the infringement, and (3) material contribution to the infringement. Id. The element of direct infringement is undisputed in this case.
1. Knowledge
Any examination of contributory copyright infringement must be guided by the seminal case of
Sony Corp. of America v. Universal City Studios, Inc.,
In
Napster I,
we construed
Sony-Betamax
to apply to the knowledge element of contributory copyright infringement.
Napster I
held that if a defendant could show that its product was capable of substantial or commercially significant nonin-fringing uses, then constructive knowledge of the infringement could not be imputed.
*1161
Rather, if substantial noninfringing use was shown, the copyright owner would be required to show that the defendant had reasonable knowledge of specific infringing files.
7
Napster I,
Thus, in order to analyze the required element of knowledge of infringement, we must first determine what level of knowledge to require. If the product at issue is not capable of substantial or commercially significant noninfringing uses, then the copyright owner need only show that the defendant had constructive knowledge of the infringement. On the other hand, if the product at issue
is
capable of substantial or commercially significant noninfringing uses, then the copyright owner must demonstrate that the defendant had reasonable knowledge of specific infringing files and failed to act on that knowledge to prevent infringement.
See Napster I,
In this case, the district court found it undisputed that the software distributed by each defendant was capable of substantial noninfringing uses.
Grokster I,
The Copyright Owners submitted no evidence that could contradict these declarations. Rather, the Copyright Owners argue that the evidence establishes that the vast majority of the software use is for copyright infringement. This argument misapprehends the
Sony
standard as construed in
Napster I,
which emphasized that in order for limitations imposed by
Sony
to apply, a product need only be
capable
of substantial noninfringing uses.
Napster I,
In this case, the Software Distributors have not only shown that their products are capable of substantial noninfringing uses, 10 but that the uses have commercial viability. Thus, applying Napster I, Napster II, and Sony-Betamax to the record, the district court correctly concluded that the Software Distributors had established that their products were capable of substantial or commercially significant nonin-fringing uses. Therefore, the district correctly reasoned, the Software Distributors could not be held liable for constructive knowledge of infringement, and the Copyright Owners were required to show that the Software Distributors had reasonable knowledge of specific infringement to satisfy the threshold knowledge requirement.
Having determined that the “reasonable knowledge of specific infringement” requirement applies here, we must then decide whether the Copyright Owners have raised sufficient genuine issues of material fact to satisfy that higher standard. As the district court correctly concluded, the time at which such knowledge is obtained is significant. Because contributory copyright infringement requires knowledge
and
material contribution, the Copyright Owners were required to establish that the Software Distributors had “specific knowledge of infringement at a time at which they contribute^] to the infringement, and [] fail[ed] to act upon that information.”
Grokster I,
In the context of this case, the software design is of great import. As we have discussed, the software at issue in
Napster I
and
Napster II
employed a centralized set of servers that maintained an index of available files. In contrast, under both StreamCast’s decentralized, Gnutellatype network and Grokster’s quasi-decentralized, supernode, KaZaa-type network, no central index is maintained. Indeed, at present, neither StreamCast nor Grokster maintains control over index files. As the district court observed, even if the Software Distributors “closed their doors and deactivated all computers within their control, users of their products could continue sharing files with little or no interruption.”
Grokster I,
Therefore, we agree with the district court that the Software Distributors were entitled to partial summary judgment on the element of knowledge.
2. Material Contribution
We also agree with the district court that with respect to their current software distribution and related activities, defendants do not materially contribute to copyright infringement.
In
Napster I,
we found material contribution after reciting the district court’s factual finding that “Napster is an integrated service.”
As indicated by the record, the Software Distributors do not provide the “site and facilities” for infringement, and do not otherwise materially contribute to direct infringement. Infringing messages or file indices do not reside on defendants’ computers, nor do defendants have the ability to suspend user accounts.
Grokster I,
While material contribution can be established through provision of site and facilities for infringement, followed by a failure to stop specific instances of infringement once knowledge of those infringements is acquired, the Software Distributors have not provided the site and facilities for infringement in the first place. If the Software Distributors were true access providers, failure to disable that access after acquiring specific knowledge of a user’s infringement might be material contribution.
Netcom,
The Copyright Owners have not provided evidence that defendants materially contribute in any other manner. Stream-Cast maintains an XML 11 file from which user software periodically retrieves parameters. These values may include the addresses of websites where lists of active users are maintained. The owner of the FastTrack software, Sharman, maintains root nodes containing lists of currently active supernodes to which users can connect. Both defendants also communicate with users incidentally, but not to facilitate infringement. All of these activities are too incidental to any direct copyright infringement to constitute material contribution. No infringing files or lists of infringing files are hosted by defendants, and the defendants do not regulate or provide access.
While Grokster and StreamCast in particular may seek to be the “next Napster,”
Grokster I,
B. Vicarious Copyright Infringement
Three elements are required to prove a defendant vicariously liable for copyright infringement: (1) direct infringement by a primary party, (2) a direct financial benefit to the defendant, and (3) the right and ability to supervise the infringers.
Napster I,
The elements of direct infringement and a direct financial benefit, via advertising revenue, are undisputed in this case.
1. Right and Ability To Supervise
We agree with the district court that there is no issue of material fact as to whether defendants have the right and ability to supervise the direct infringers in this case. Allocation of liability in vicarious copyright liability cases has developed from a historical distinction between the paradigmatic “dance hall operator” and “landlord” defendants.
Cherry Auction,
A salient characteristic of that relationship often, though not always, is a formal licensing agreement between the defendant and the direct infringer.
See, e.g., Napster I,
In
Cherry Auction,
we held that the right and ability to supervise existed where a swap meet operator reserved the right to terminate vendors for any reason, promoted the swap meet, controlled access by customers, patrolled the meet, and could control direct infringers through its rules and regulations.
It does not appear from any of the evidence in the record that either of the defendants has the ability to block access to individual users. Grokster nominally reserves the right to terminate access, while StreamCast does not maintain a licensing agreement with persons who download Morpheus. However, given the lack of a registration and log-in process, even Grokster has no ability to actually terminate access to filesharing functions, absent a mandatory software upgrade to all users that the particular user refuses, or IP address-blocking attempts. 12 It is also clear that none of the communication between defendants and users provides a point of access for filtering or searching for infringing files, since infringing material and index information do not pass through defendants’ computers.
In the case of StreamCast, shutting down its XML file altogether would not prevent anyone from using the Gnutella network. In the case of Grokster, its licensing agreement with KaZaa/Sharman does not give it the ability to mandate that root nodes be shut down. Moreover, the alleged ability to shut down operations altogether is more akin to the ability to close down an entire swap meet or stop distributing software altogether, rather than the ability to exclude individual participants, a practice of policing aisles, an ability to block individual users directly at the point of log-in, or an ability to delete individual filenames from one’s own computer.
See Napster I,
The district court here found that unlike Napster, Grokster and StreamCast do not operate and design an “integrated service,”
Grokster I,
The district court correctly characterized the Copyright Owners’ evidence of the right and ability to supervise as little more than a contention that “the software
*1166
itself could be altered to prevent users from sharing copyrighted files.”
Grokster I,
C. Turning a “Blind Eye” to Infringement
The Copyright Owners finally argue that Grokster and StreamCast should not be able to escape vicarious liability by turning a “blind eye” to the infringement of their users, and that “[t]urning a blind eye to detectable acts of infringement for the sake of profit gives rise to liability.”
Napster I,
III.
Resolution of these issues does not end the case. As the district court clearly stated, its decision was limited to the specific software in use at the time of the district court decision. The Copyright Owners have also sought relief based on previous versions of the software, which contain significant — and perhaps crucial— differences from the software at issue. We express no opinion as to those issues.
As to the question at hand, the district court’s grant of partial summary judgment to the Software Distributors is clearly dictated by applicable precedent. The Copyright Owners urge a re-examination of the law in the light of what they believe to be proper public policy, expanding exponentially the reach of the doctrines of contributory and vicarious copyright infringement. Not only would such a renovation conflict with binding precedent, it would be unwise. Doubtless, taking that step would satisfy the Copyright Owners’ immediate economic aims. However, it would also alter general copyright law in profound ways with unknown ultimate consequences outside the present context.
*1167
Further, as we have observed, we live in a quicksilver technological environment with courts ill-suited to fix the flow of internet innovation.
AT & T Corp. v. City of Portland,
Indeed, the Supreme Court has admonished us to leave such matters to Congress. In
Sony-Betamax,
the Court spoke quite clearly about the role of Congress in applying copyright law to new technologies. As the Supreme Court stated in that case, “The direction of Art. I is that
Congress
shall have the power to promote the progress of science and the useful arts. When, as here, the Constitution is permissive, the sign of how far Congress has chosen to go can come only
from
Congress.”
In this case, the district court correctly applied applicable law and properly declined the invitation to alter it. We affirm the district court, and remand for resolution of the remaining issues.
AFFIRMED.
Notes
. The plaintiffs in the Leiber case represent a certified class of over 27,000 songwriters and music publishers. The plaintiffs in the MGM case include most of the major motion picture studios and recording companies.
. This is an extremely simplistic overview of peer-to-peer file-sharing networks. There are a number of more complete descriptions available. See, e.g., Yochai Benkler, Coase’s Penguin, or, Linux and The Nature of the Firm, 112 Yale L.J. 369, 396-400 (2002); Jesse M. Feder, Is Betamax Obsolete?: Sony Corp. of America v. Universal City Studios, Inc. in the Age of Napster, 37 Creighton L.Rev. 859, 862-68 (2004).
. A more complete description of the Napster system is contained in
A & M Records v. Napster,
. Since the litigation in this case began, control of the FastTrack software passed from KaZaa to Sharman Networks. KaZaa was named as a defendant in this action, but eventually ceased defending and default judgment was entered against it.
. The owners of the FastTrack Software successfully prevented users of the StreamCast version of FastTrack from being able to connect to the Grokster and KaZaa users of Fast-Track by using a software upgrade that was not sent to StreamCast users. Peer-to-peer file-sharing software upgrades can be coded in a way that prevents those who do not accept the upgrade from communicating with those who do, but those users who do not accept an upgrade may still be able to communicate with each other. The record indi *1160 cates this has already occurred, with a number of nonupgraded users still being able to communicate and share files with each other.
. A more detailed description of each system is contained in the district court opinion in this case.
Grokster I,
. In full, the test adopted in
Napster I
for defendants whose products are capable of substantial or commercially significant nonin-fringing uses is that "contributory liability may potentially be imposed only to the extent that the defendant (1) receives reasonable knowledge of specific infringing files ...; (2) knows or should know that such files are available on the Napster system; and (3) fails to act to prevent viral distribution of the works.”
. After
Napster I
was decided, the district court on remand required plaintiffs to give Napster notice of specific infringing files, and then required Napster to continually search its index and block all files containing the particular works at issue.
Napster II,
. We are mindful that the Seventh Circuit has read
Sony’s
substantial noninfringing use standard differently.
In re Aimster Copyright Litig.,
. Indeed, even at a 10% level of legitimate use, as contended by the Copyright Owners, the volume of use would indicate a minimum of hundreds of thousands of legitimate file exchanges.
. XML is an abbreviation for Extensible Markup Language. A markup language the reader may be more familiar with is HTML, which stands for HyperText Markup Language.
. IP address-blocking will not be effective against a user who, like most persons, does not have a permanent IP address, but is rather assigned one each time he connects to the Internet.
