|Original author(s)||Bram Cohen|
|Standard(s)||The BitTorrent Protocol Specification|
|Type||peer-to-peer file sharing|
|Part of a series on|
|Video sharing sites|
|File sharing networks|
|Anonymous file sharing|
|Development and societal aspects|
|By country or region|
To send or receive files, a person uses a BitTorrent client on their Internet-connected computer. A BitTorrent client is a computer program that implements the BitTorrent protocol. BitTorrent clients are available for a variety of computing platforms and operating systems, including an official client released by BitTorrent, Inc. Popular clients include μTorrent, Xunlei Thunder, Transmission, qBittorrent, Vuze, Deluge, BitComet and Tixati. BitTorrent trackers provide a list of files available for transfer and allow the client to find peer users, known as "seeds", who may transfer the files.
Programmer Bram Cohen, a University at Buffalo alumnus, designed the protocol in April 2001, and released the first available version on 2 July 2001. On 15 May 2017, an update to the protocol specification was released by BitTorrent, called BitTorrent v2. libtorrent was updated to support the new version on 6 September 2020.
BitTorrent is one of the most common protocols for transferring large files, such as digital video files containing TV shows and video clips, or digital audio files containing songs. As of February 2013, BitTorrent was responsible for 3.35% of all worldwide bandwidth—more than half of the 6% of total bandwidth dedicated to file sharing. In 2019, BitTorrent was a dominant file sharing protocol and generated a substantial amount of Internet traffic, with 2.46% of downstream, and 27.58% of upstream traffic. As of 2013, BitTorrent has 15–27 million concurrent users at any time. As of January 2012, BitTorrent is utilized by 150 million active users. Based on this figure, the total number of monthly users may be estimated to more than a quarter of a billion (≈ 250 million).
The use of BitTorrent may sometimes be limited by Internet Service Providers (ISPs), on legal or copyright grounds. In turn, users may choose to run seedboxes or Virtual Private Networks (VPNs) as an alternative.
This section needs expansion. You can help by adding to it. (September 2021)
The first release of the BitTorrent client had no search engine and no peer exchange. Up until 2005, the only way to share files was by creating a small text file called a "torrent", that they would upload to a torrent index site. The first uploader acted as a seed, and downloaders would initially connect as peers. Those who wish to download the file would download the torrent, which their client would use to connect to a tracker which had a list of the IP addresses of other seeds and peers in the swarm. Once a peer completed a download of the complete file, it could in turn function as a seed. These files contain metadata about the files to be shared and the trackers which keep track of the other seeds and peers.
In 2005, first Vuze and then the BitTorrent client introduced distributed tracking using distributed hash tables which allowed clients to exchange data on swarms directly without the need for a torrent file.
In 2006, peer exchange functionality was added allowing clients to add peers based on the data found on connected nodes.
BitTorrent v2 is intended to work seamlessly with previous versions of the BitTorrent protocol. The main reason for the update was that the old cryptographic hash function, SHA-1 is no longer considered safe from malicious attacks by the developers, and as such, v2 uses SHA-256. To ensure backwards compatibility, the v2 .torrent file format supports a hybrid mode where the torrents are hashed through both the new method and the old method, with the intent that the files will be shared with peers on both v1 and v2 swarms. Another update to the specification is adding a hash tree to speed up time from adding a torrent to downloading files, and to allow more granular checks for file corruption. In addition, each file is now hashed individually, enabling files in the swarm to be deduplicated, so that if multiple torrents include the same files, but seeders are only seeding the file from some, downloaders of the other torrents can still download the file. Magnet links for v2 also support a hybrid mode to ensure support for legacy clients.
The BitTorrent protocol can be used to reduce the server and network impact of distributing large files. Rather than downloading a file from a single source server, the BitTorrent protocol allows users to join a "swarm" of hosts to upload and download from each other simultaneously. The protocol is an alternative to the older single source, multiple mirror sources technique for distributing data, and can work effectively over networks with lower bandwidth. Using the BitTorrent protocol, several basic computers, such as home computers, can replace large servers while efficiently distributing files to many recipients. This lower bandwidth usage also helps prevent large spikes in internet traffic in a given area, keeping internet speeds higher for all users in general, regardless of whether or not they use the BitTorrent protocol.
The file being distributed is divided into segments called pieces. As each peer receives a new piece of the file, it becomes a source (of that piece) for other peers, relieving the original seed from having to send that piece to every computer or user wishing a copy. With BitTorrent, the task of distributing the file is shared by those who want it; it is entirely possible for the seed to send only a single copy of the file itself and eventually distribute to an unlimited number of peers. Each piece is protected by a cryptographic hash contained in the torrent descriptor. This ensures that any modification of the piece can be reliably detected, and thus prevents both accidental and malicious modifications of any of the pieces received at other nodes. If a node starts with an authentic copy of the torrent descriptor, it can verify the authenticity of the entire file it receives.
Pieces are typically downloaded non-sequentially, and are rearranged into the correct order by the BitTorrent client, which monitors which pieces it needs, and which pieces it has and can upload to other peers. Pieces are of the same size throughout a single download (for example, a 10 MB file may be transmitted as ten 1 MB pieces or as forty 256 KB pieces). Due to the nature of this approach, the download of any file can be halted at any time and be resumed at a later date, without the loss of previously downloaded information, which in turn makes BitTorrent particularly useful in the transfer of larger files. This also enables the client to seek out readily available pieces and download them immediately, rather than halting the download and waiting for the next (and possibly unavailable) piece in line, which typically reduces the overall time of the download. This eventual transition from peers to seeders determines the overall "health" of the file (as determined by the number of times a file is available in its complete form).
The distributed nature of BitTorrent can lead to a flood-like spreading of a file throughout many peer computer nodes. As more peers join the swarm, the likelihood of a successful download by any particular node increases. Relative to traditional Internet distribution schemes, this permits a significant reduction in the original distributor's hardware and bandwidth resource costs. Distributed downloading protocols in general provide redundancy against system problems, reduce dependence on the original distributor, and provide sources for the file which are generally transient and therefore there is no single point of failure as in one way server-client transfers.
Though both ultimately transfer files over a network, a BitTorrent download differs from a one way server-client download (as is typical with an HTTP or FTP request, for example) in several fundamental ways:
- BitTorrent makes many small data requests over different IP connections to different machines, while server-client downloading is typically made via a single TCP connection to a single machine.
- BitTorrent downloads in a random or in a "rarest-first" approach that ensures high availability, while classic downloads are sequential.
Taken together, these differences allow BitTorrent to achieve much lower cost to the content provider, much higher redundancy, and much greater resistance to abuse or to "flash crowds" than regular server software. However, this protection, theoretically, comes at a cost: downloads can take time to rise to full speed because it may take time for enough peer connections to be established, and it may take time for a node to receive sufficient data to become an effective uploader. This contrasts with regular downloads (such as from an HTTP server, for example) that, while more vulnerable to overload and abuse, rise to full speed very quickly, and maintain this speed throughout. In the beginning, BitTorrent's non-contiguous download methods made it harder to support "streaming playback". In 2014, the client Popcorn Time allowed for streaming of BitTorrent video files. Since then, more and more clients are offering streaming options.
The BitTorrent protocol provides no way to index torrent files. As a result, a comparatively small number of websites have hosted a large majority of torrents, many linking to copyrighted works without the authorization of copyright holders, rendering those sites especially vulnerable to lawsuits. A BitTorrent index is a "list of .torrent files, which typically includes descriptions" and information about the torrent's content. Several types of websites support the discovery and distribution of data on the BitTorrent network. Public torrent-hosting sites such as The Pirate Bay allow users to search and download from their collection of torrent files. Users can typically also upload torrent files for content they wish to distribute. Often, these sites also run BitTorrent trackers for their hosted torrent files, but these two functions are not mutually dependent: a torrent file could be hosted on one site and tracked by another unrelated site. Private host/tracker sites operate like public ones except that they may restrict access to registered users and may also keep track of the amount of data each user uploads and downloads, in an attempt to reduce "leeching".
Web search engines allow the discovery of torrent files that are hosted and tracked on other sites; examples include The Pirate Bay and BTDigg. These sites allow the user to ask for content meeting specific criteria (such as containing a given word or phrase) and retrieve a list of links to torrent files matching those criteria. This list can often be sorted with respect to several criteria, relevance (seeders-leechers ratio) being one of the most popular and useful (due to the way the protocol behaves, the download bandwidth achievable is very sensitive to this value). Metasearch engines allow one to search several BitTorrent indices and search engines at once.
The Tribler BitTorrent client was among the first to incorporate built-in search capabilities. With Tribler, users can find .torrent files held by random peers and taste buddies. It adds such an ability to the BitTorrent protocol using a gossip protocol, somewhat similar to the eXeem network which was shut down in 2005. The software includes the ability to recommend content as well. After a dozen downloads, the Tribler software can roughly estimate the download taste of the user, and recommend additional content.
In May 2007, researchers at Cornell University published a paper proposing a new approach to searching a peer-to-peer network for inexact strings, which could replace the functionality of a central indexing site. A year later, the same team implemented the system as a plugin for Vuze called Cubit and published a follow-up paper reporting its success.
A somewhat similar facility but with a slightly different approach is provided by the BitComet client through its "Torrent Exchange" feature. Whenever two peers using BitComet (with Torrent Exchange enabled) connect to each other they exchange lists of all the torrents (name and info-hash) they have in the Torrent Share storage (torrent files which were previously downloaded and for which the user chose to enable sharing by Torrent Exchange). Thus each client builds up a list of all the torrents shared by the peers it connected to in the current session (or it can even maintain the list between sessions if instructed).
At any time the user can search into that Torrent Collection list for a certain torrent and sort the list by categories. When the user chooses to download a torrent from that list, the .torrent file is automatically searched for (by info-hash value) in the DHT Network and when found it is downloaded by the querying client which can after that create and initiate a downloading task.
Downloading and sharing
Users find a torrent of interest on a torrent index site or by using a search engine built into the client, download it, and open it with a BitTorrent client. The client connects to the tracker(s) or seeds specified in the torrent file, from which it receives a list of seeds and peers currently transferring pieces of the file(s). The client connects to those peers to obtain the various pieces. If the swarm contains only the initial seeder, the client connects directly to it, and begins to request pieces. Clients incorporate mechanisms to optimize their download and upload rates.
The effectiveness of this data exchange depends largely on the policies that clients use to determine to whom to send data. Clients may prefer to send data to peers that send data back to them (a "tit for tat" exchange scheme), which encourages fair trading. But strict policies often result in suboptimal situations, such as when newly joined peers are unable to receive any data because they don't have any pieces yet to trade themselves or when two peers with a good connection between them do not exchange data simply because neither of them takes the initiative. To counter these effects, the official BitTorrent client program uses a mechanism called "optimistic unchoking", whereby the client reserves a portion of its available bandwidth for sending pieces to random peers (not necessarily known good partners, so called preferred peers) in hopes of discovering even better partners and to ensure that newcomers get a chance to join the swarm.
Although "swarming" scales well to tolerate "flash crowds" for popular content, it is less useful for unpopular or niche market content. Peers arriving after the initial rush might find the content unavailable and need to wait for the arrival of a "seed" in order to complete their downloads. The seed arrival, in turn, may take long to happen (this is termed the "seeder promotion problem"). Since maintaining seeds for unpopular content entails high bandwidth and administrative costs, this runs counter to the goals of publishers that value BitTorrent as a cheap alternative to a client-server approach. This occurs on a huge scale; measurements have shown that 38% of all new torrents become unavailable within the first month. A strategy adopted by many publishers which significantly increases availability of unpopular content consists of bundling multiple files in a single swarm. More sophisticated solutions have also been proposed; generally, these use cross-torrent mechanisms through which multiple torrents can cooperate to better share content.
Creating and publishing
The peer distributing a data file treats the file as a number of identically sized pieces, usually with byte sizes of a power of 2, and typically between 32 kB and 16 MB each. The peer creates a hash for each piece, using the SHA-1 hash function, and records it in the torrent file. Pieces with sizes greater than 512 kB will reduce the size of a torrent file for a very large payload, but is claimed to reduce the efficiency of the protocol. When another peer later receives a particular piece, the hash of the piece is compared to the recorded hash to test that the piece is error-free. Peers that provide a complete file are called seeders, and the peer providing the initial copy is called the initial seeder. The exact information contained in the torrent file depends on the version of the BitTorrent protocol.
By convention, the name of a torrent file has the suffix
.torrent. Torrent files have an "announce" section, which specifies the URL of the tracker, and an "info" section, containing (suggested) names for the files, their lengths, the piece length used, and a SHA-1 hash code for each piece, all of which are used by clients to verify the integrity of the data they receive. Though SHA-1 has shown signs of cryptographic weakness, Bram Cohen did not initially consider the risk big enough for a backward incompatible change to, for example, SHA-3. As of BitTorrent v2 the hash function has been updated to SHA-256.
In the early days, torrent files were typically published to torrent index websites, and registered with at least one tracker. The tracker maintained lists of the clients currently connected to the swarm. Alternatively, in a trackerless system (decentralized tracking) every peer acts as a tracker. Azureus was the first BitTorrent client to implement such a system through the distributed hash table (DHT) method. An alternative and incompatible DHT system, known as Mainline DHT, was released in the Mainline BitTorrent client three weeks later (though it had been in development since 2002) and subsequently adopted by the μTorrent, Transmission, rTorrent, KTorrent, BitComet, and Deluge clients.
After the DHT was adopted, a "private" flag – analogous to the broadcast flag – was unofficially introduced, telling clients to restrict the use of decentralized tracking regardless of the user's desires. The flag is intentionally placed in the info section of the torrent so that it cannot be disabled or removed without changing the identity of the torrent. The purpose of the flag is to prevent torrents from being shared with clients that do not have access to the tracker. The flag was requested for inclusion in the official specification in August 2008, but has not been accepted yet. Clients that have ignored the private flag were banned by many trackers, discouraging the practice.
BitTorrent does not, on its own, offer its users anonymity. One can usually see the IP addresses of all peers in a swarm in one's own client or firewall program. This may expose users with insecure systems to attacks. In some countries, copyright organizations scrape lists of peers, and send takedown notices to the internet service provider of users participating in the swarms of files that are under copyright. In some jurisdictions, copyright holders may launch lawsuits against uploaders or downloaders for infringement, and police may arrest suspects in such cases.
Various means have been used to promote anonymity. For example, the BitTorrent client Tribler makes available a Tor-like onion network, optionally routing transfers through other peers to obscure which client has requested the data. The exit node would be visible to peers in a swarm, but the Tribler organization provides exit nodes. One advantage of Tribler is that clearnet torrents can be downloaded with only a small decrease in download speed from one "hop" of routing.
i2p provides a similar anonymity layer although in that case, one can only download torrents that have been uploaded to the i2p network. The bittorrent client Vuze allows users who are not concerned about anonymity to take clearnet torrents, and make them available on the i2p network.
Private torrent trackers are usually invitation only, and require members to participate in uploading, but have the downside of a single centralized point of failure. Oink's Pink Palace and What.cd are examples of private trackers which have been shut down.
Seedbox services download the torrent files first to the company's servers, allowing the user to direct download the file from there. One's IP address would be visible to the Seedbox provider, but not to third parties.
Virtual private networks encrypt transfers, and substitute a different IP address for the user's, so that anyone monitoring a torrent swarm will only see that address.
On 2 May 2005, Azureus 220.127.116.11 (now known as Vuze) was released, introducing support for "trackerless" torrents through a system called the "distributed database." This system is a Distributed hash table implementation which allows the client to use torrents that do not have a working BitTorrent tracker. Instead just bootstrapping server is used (router.bittorrent.com, dht.transmissionbt.com or router.utorrent.com). The following month, BitTorrent, Inc. released version 4.2.0 of the Mainline BitTorrent client, which supported an alternative DHT implementation (popularly known as "Mainline DHT", outlined in a draft on their website) that is incompatible with that of Azureus. In 2014, measurement showed concurrent users of Mainline DHT to be from 10 million to 25 million, with a daily churn of at least 10 million.
Current versions of the official BitTorrent client, μTorrent, BitComet, Transmission and BitSpirit all share compatibility with Mainline DHT. Both DHT implementations are based on Kademlia. As of version 18.104.22.168, Azureus also supports Mainline DHT in addition to its own distributed database through use of an optional application plugin. This potentially allows the Azureus/Vuze client to reach a bigger swarm.
Another idea that has surfaced in Vuze is that of virtual torrents. This idea is based on the distributed tracker approach and is used to describe some web resource. Currently, it is used for instant messaging. It is implemented using a special messaging protocol and requires an appropriate plugin. Anatomic P2P is another approach, which uses a decentralized network of nodes that route traffic to dynamic trackers. Most BitTorrent clients also use Peer exchange (PEX) to gather peers in addition to trackers and DHT. Peer exchange checks with known peers to see if they know of any other peers. With the 22.214.171.124 release of Vuze, all major BitTorrent clients now have compatible peer exchange.
Web "seeding" was implemented in 2006 as the ability of BitTorrent clients to download torrent pieces from an HTTP source in addition to the "swarm". The advantage of this feature is that a website may distribute a torrent for a particular file or batch of files and make those files available for download from that same web server; this can simplify long-term seeding and load balancing through the use of existing, cheap, web hosting setups. In theory, this would make using BitTorrent almost as easy for a web publisher as creating a direct HTTP download. In addition, it would allow the "web seed" to be disabled if the swarm becomes too popular while still allowing the file to be readily available. This feature has two distinct specifications, both of which are supported by Libtorrent and the 26+ clients that use it.
The first was created by John "TheSHAD0W" Hoffman, who created BitTornado. This first specification requires running a web service that serves content by info-hash and piece number, rather than filename.
In September 2010, a new service named Burnbit was launched which generates a torrent from any URL using webseeding. There are server-side solutions that provide initial seeding of the file from the web server via standard BitTorrent protocol and when the number of external seeders reach a limit, they stop serving the file from the original source.
A technique called broadcatching combines RSS feeds with the BitTorrent protocol to create a content delivery system, further simplifying and automating content distribution. Steve Gillmor explained the concept in a column for Ziff-Davis in December 2003. The discussion spread quickly among bloggers (Ernest Miller, Chris Pirillo, etc.). In an article entitled Broadcatching with BitTorrent, Scott Raymond explained:
I want RSS feeds of BitTorrent files. A script would periodically check the feed for new items, and use them to start the download. Then, I could find a trusted publisher of an Alias RSS feed, and "subscribe" to all new episodes of the show, which would then start downloading automatically – like the "season pass" feature of the TiVo.— Scott Raymond, scottraymond.net
The RSS feed will track the content, while BitTorrent ensures content integrity with cryptographic hashing of all data, so feed subscribers will receive uncorrupted content. One of the first and popular software clients (free and open source) for broadcatching is Miro. Other free software clients such as PenguinTV and KatchTV are also now supporting broadcatching. The BitTorrent web-service MoveDigital added the ability to make torrents available to any web application capable of parsing XML through its standard REST-based interface in 2006, though this has since been discontinued. Additionally, Torrenthut is developing a similar torrent API that will provide the same features, and help bring the torrent community to Web 2.0 standards. Alongside this release is a first PHP application built using the API called PEP, which will parse any Really Simple Syndication (RSS 2.0) feed and automatically create and seed a torrent for each enclosure found in that feed.
Throttling and encryption
Since BitTorrent makes up a large proportion of total traffic, some ISPs have chosen to "throttle" (slow down) BitTorrent transfers. For this reason, methods have been developed to disguise BitTorrent traffic in an attempt to thwart these efforts. Protocol header encrypt (PHE) and Message stream encryption/Protocol encryption (MSE/PE) are features of some BitTorrent clients that attempt to make BitTorrent hard to detect and throttle. As of November 2015, Vuze, Bitcomet, KTorrent, Transmission, Deluge, μTorrent, MooPolice, Halite, qBittorrent, rTorrent, and the latest official BitTorrent client (v6) support MSE/PE encryption.
In August 2007, Comcast was preventing BitTorrent seeding by monitoring and interfering with the communication between peers. Protection against these efforts is provided by proxying the client-tracker traffic via an encrypted tunnel to a point outside of the Comcast network. In 2008, Comcast called a "truce" with BitTorrent, Inc. with the intention of shaping traffic in a protocol-agnostic manner. Questions about the ethics and legality of Comcast's behavior have led to renewed debate about net neutrality in the United States. In general, although encryption can make it difficult to determine what is being shared, BitTorrent is vulnerable to traffic analysis. Thus, even with MSE/PE, it may be possible for an ISP to recognize BitTorrent and also to determine that a system is no longer downloading but only uploading data, and terminate its connection by injecting TCP RST (reset flag) packets.
Another unofficial feature is an extension to the BitTorrent metadata format proposed by John Hoffman and implemented by several indexing websites. It allows the use of multiple trackers per file, so if one tracker fails, others can continue to support file transfer. It is implemented in several clients, such as BitComet, BitTornado, BitTorrent, KTorrent, Transmission, Deluge, μTorrent, rtorrent, Vuze, and Frostwire. Trackers are placed in groups, or tiers, with a tracker randomly chosen from the top tier and tried, moving to the next tier if all the trackers in the top tier fail.
Torrents with multiple trackers can decrease the time it takes to download a file, but also have a few consequences:
- Poorly implemented clients may contact multiple trackers, leading to more overhead-traffic.
- Torrents from closed trackers suddenly become downloadable by non-members, as they can connect to a seed via an open tracker.
As of December 2008, BitTorrent, Inc. was working with Oversi on new Policy Discover Protocols that query the ISP for capabilities and network architecture information. Oversi's ISP hosted NetEnhancer box is designed to "improve peer selection" by helping peers find local nodes, improving download speeds while reducing the loads into and out of the ISP's network.
The BitTorrent specification is free to use and many clients are open source, so BitTorrent clients have been created for all common operating systems using a variety of programming languages. The official BitTorrent client, μTorrent, qBittorrent, Transmission, Vuze, and BitComet are some of the most popular clients.
Some BitTorrent implementations such as MLDonkey and Torrentflux are designed to run as servers. For example, this can be used to centralize file sharing on a single dedicated server which users share access to on the network. Server-oriented BitTorrent implementations can also be hosted by hosting providers at co-located facilities with high bandwidth Internet connectivity (e.g., a datacenter) which can provide dramatic speed benefits over using BitTorrent from a regular home broadband connection. Services such as ImageShack can download files on BitTorrent for the user, allowing them to download the entire file by HTTP once it is finished.
The Opera web browser supports BitTorrent, as do Wyzo and Brave. BitLet allows users to download Torrents directly from their browser using a Java applet. An increasing number of hardware devices are being made to support BitTorrent. These include routers and NAS devices containing BitTorrent-capable firmware like OpenWrt. Proprietary versions of the protocol which implement DRM, encryption, and authentication are found within managed clients such as Pando.
A growing number of individuals and organizations are using BitTorrent to distribute their own or licensed works (e.g. indie bands distributing digital files of their new songs). Independent adopters report that without using BitTorrent technology, and its dramatically reduced demands on their private networking hardware and bandwidth, they could not afford to distribute their files.
Some uses of BitTorrent for file sharing may violate laws in some jurisdictions (see legal issues section).
Film, video, and music
- BitTorrent Inc. has obtained a number of licenses from Hollywood studios for distributing popular content from their websites.
- Sub Pop Records releases tracks and videos via BitTorrent Inc. to distribute its 1000+ albums. Babyshambles and The Libertines (both bands associated with Pete Doherty) have extensively used torrents to distribute hundreds of demos and live videos. US industrial rock band Nine Inch Nails frequently distributes albums via BitTorrent.
- Podcasting software is starting to integrate BitTorrent to help podcasters deal with the download demands of their MP3 "radio" programs. Specifically, Juice and Miro (formerly known as Democracy Player) support automatic processing of .torrent files from RSS feeds. Similarly, some BitTorrent clients, such as μTorrent, are able to process web feeds and automatically download content found within them.
- DGM Live purchases are provided via BitTorrent.
- VODO, a service which distributes "free-to-share" movies and TV shows via BitTorrent.
- In 2008, the CBC became the first public broadcaster in North America to make a full show (Canada's Next Great Prime Minister) available for download using BitTorrent.
- The Norwegian Broadcasting Corporation (NRK) has since March 2008 experimented with bittorrent distribution, available online. Only selected works in which NRK owns all royalties are published. Responses have been very positive, and NRK is planning to offer more content.
- The Dutch VPRO broadcasting organization released four documentaries in 2009 and 2010 under a Creative Commons license using the content distribution feature of the Mininova tracker.
Cloud Service Providers
- The Amazon AWS's Simple Storage Service (S3), until April 29, 2021, had supported sharing of bucket objects with BitTorrent protocols. As of June 13, 2020, the feature is only available in service regions launched after May 30, 2016. The feature for the existing customers will be extended for an additional 12 months following the deprecation. After April 29, 2022, BitTorrent clients will no longer connect to Amazon S3.
- Blizzard Entertainment uses BitTorrent (via a proprietary client called the "Blizzard Downloader", associated with the Blizzard "BattleNet" network) to distribute content and patches for Diablo III, StarCraft II and World of Warcraft, including the games themselves.
- Wargaming uses BitTorrent in their popular titles World of Tanks, World of Warships and World of Warplanes to distribute game updates.
- CCP Games, maker of the space simulation MMORPG Eve Online, has announced that a new launcher will be released that is based on BitTorrent.
- Many software games, especially those whose large size makes them difficult to host due to bandwidth limits, extremely frequent downloads, and unpredictable changes in network traffic, will distribute instead a specialized, stripped down BitTorrent client with enough functionality to download the game from the other running clients and the primary server (which is maintained in case not enough peers are available).
- Many major open source and free software projects encourage BitTorrent as well as conventional downloads of their products (via HTTP, FTP etc.) to increase availability and to reduce load on their own servers, especially when dealing with larger files.
- Resilio Sync is a BitTorrent-based folder-syncing tool which can act as an alternative to server-based synchronisation services such as Dropbox.
- The British government used BitTorrent to distribute details about how the tax money of British citizens was spent.
- Florida State University uses BitTorrent to distribute large scientific data sets to its researchers.
- Many universities that have BOINC distributed computing projects have used the BitTorrent functionality of the client-server system to reduce the bandwidth costs of distributing the client-side applications used to process the scientific data. If a BOINC distributed computing application needs to be updated (or merely sent to a user), it can do so with little impact on the BOINC server.
- The developing Human Connectome Project uses BitTorrent to share their open dataset.
- Academic Torrents is a BitTorrent tracker for use by researchers in fields that need to share large datasets
- Facebook uses BitTorrent to distribute updates to Facebook servers.
- Twitter uses BitTorrent to distribute updates to Twitter servers.
- The Internet Archive added BitTorrent to its file download options for over 1.3 million existing files, and all newly uploaded files, in August 2012. This method is the fastest means of downloading media from the Archive.
Routers that use network address translation (NAT) must maintain tables of source and destination IP addresses and ports. Because BitTorrent frequently contacts 20–30 servers per second, the NAT tables of some consumer-grade routers are rapidly filled. This is a known cause of some home routers ceasing to work correctly.
Although the protocol itself is legal, problems stem from using the protocol to traffic copyright infringing works, since BitTorrent is often used to download otherwise paid content, such as movies and video games. There has been much controversy over the use of BitTorrent trackers. BitTorrent metafiles themselves do not store file contents. Whether the publishers of BitTorrent metafiles violate copyrights by linking to copyrighted works without the authorization of copyright holders is controversial. Various jurisdictions have pursued legal action against websites that host BitTorrent trackers.
High-profile examples include the closing of Suprnova.org, TorrentSpy, LokiTorrent, BTJunkie, Mininova, Oink's Pink Palace and What.cd. The Pirate Bay torrent website, formed by a Swedish group, is noted for the "legal" section of its website in which letters and replies on the subject of alleged copyright infringements are publicly displayed. On 31 May 2006, The Pirate Bay's servers in Sweden were raided by Swedish police on allegations by the MPAA of copyright infringement; however, the tracker was up and running again three days later. In the study used to value NBC Universal in its merger with Comcast, Envisional examined the 10,000 torrent swarms managed by PublicBT which had the most active downloaders. After excluding pornographic and unidentifiable content, it was found that only one swarm offered legitimate content.
In the United States, more than 200,000 lawsuits have been filed for copyright infringement on BitTorrent since 2010. In the United Kingdom, on 30 April 2012, the High Court of Justice ordered five ISPs to block BitTorrent search engine The Pirate Bay. (see List of websites blocked in the United Kingdom)
One concern is the UDP flood attack. BitTorrent implementations often use μTP for their communication. To achieve high bandwidths, the underlying protocol used is UDP, which allows spoofing of source addresses of internet traffic. It has been possible to carry out Denial-of-service attacks in a P2P lab environment, where users running BitTorrent clients act as amplifiers for an attack at another service. However this is not always an effective attack because ISPs can check if the source address is correct.
Several studies on BitTorrent found files available for download containing malware. In particular, one small sample indicated that 18% of all executable programs available for download contained malware. Another study claims that as much as 14.5% of BitTorrent downloads contain zero-day malware, and that BitTorrent was used as the distribution mechanism for 47% of all zero-day malware they have found.
- Anonymous P2P
- Anti-Counterfeiting Trade Agreement
- Cache Discovery Protocol
- Comparison of BitTorrent clients
- Comparison of BitTorrent sites
- Comparison of BitTorrent tracker software
- Glossary of BitTorrent terms
- Magnet URI scheme
- Simple file verification
- Torrent poisoning
- Cohen, Bram (October 2002). "BitTorrent Protocol 1.0". BitTorrent.org. Archived from the original on 8 February 2014. Retrieved 1 June 2020.
- Van der Sar, Ernesto (4 December 2009). "Thunder Blasts uTorrent's Market Share Away - TorrentFreak". TorrentFreak. Archived from the original on 20 February 2016. Retrieved 18 June 2018.
- "迅雷-全球共享计算与区块链创领者". www.xunlei.com. Retrieved 21 November 2019.
- "UB Engineering Tweeter". University at Buffalo's School of Engineering and Applied Sciences. Archived from the original on 11 November 2013.
- Cohen, Bram (2 July 2001). "BitTorrent – a new P2P app". Yahoo eGroups. Archived from the original on 29 January 2008. Retrieved 15 April 2007.
- "Merge pull request #59 from the8472/new-hash-algos". BitTorrent. 15 May 2017. Retrieved 13 September 2021.
- Cohen, Bram. "The BitTorrent Protocol Specification v2". BitTorrent.org. BitTorrent. Retrieved 28 October 2020.
- "Bittorrent-v2". libbittorrent.org. libbittorrent. Retrieved 28 October 2020.
- "Application Usage & Threat Report". Palo Alto Networks. 2013. Archived from the original on 31 October 2013. Retrieved 7 April 2013.
- Marozzo, Fabrizio; Talia, Domenico; Trunfio, Paolo (2020). "A Sleep-and-Wake technique for reducing energy consumption in BitTorrent networks". Concurrency and Computation: Practice and Experience. 32 (14). doi:10.1002/cpe.5723. ISSN 1532-0634. S2CID 215841734.
- Wang, Liang; Kangasharju, J. (1 September 2013). "Measuring large-scale distributed systems: Case of Bit Torrent Mainline DHT". IEEE P2P 2013 Proceedings. pp. 1–10. doi:10.1109/P2P.2013.6688697. ISBN 978-1-4799-0515-7. S2CID 5659252. Archived from the original on 18 November 2015. Retrieved 7 January 2016.
- "BitTorrent and μTorrent Software Surpass 150 Million User Milestone". Bittorrent.com. 9 January 2012. Archived from the original on 26 March 2014. Retrieved 9 July 2012.
- "UB Engineering Tweeter". University at Buffalo's School of Engineering and Applied Sciences. Archived from the original on 11 November 2013.
- "Bittorrent-v2". libbittorrent.org. libbittorrent. Retrieved 28 October 2020.
- Menasche, Daniel S.; Rocha, Antonio A. A.; de Souza e Silva, Edmundo A.; Leao, Rosa M.; Towsley, Don; Venkataramani, Arun (2010). "Estimating Self-Sustainability in Peer-to-Peer Swarming Systems". Performance Evaluation. 67 (11): 1243–1258. arXiv:1004.0395. doi:10.1016/j.peva.2010.08.013. S2CID 9361889. by D. Menasche, A. Rocha, E. de Souza e Silva, R. M. Leao, D. Towsley, A. Venkataramani.
- Urvoy-Keller (December 2006). "Rarest First and Choke Algorithms Are Enough" (PDF). SIGCOMM. Archived (PDF) from the original on 23 May 2012. Retrieved 9 March 2012.
- Ernesto (12 July 2009). "PublicBT Tracker Set To Patch BitTorrent' Achilles' Heel". Torrentfreak. Archived from the original on 26 March 2014. Retrieved 14 July 2009.
- Chwan-Hwa (John) Wu, J. David Irwin. Introduction to Computer Networks and Cybersecurity. Chapter 5.4.: Partially Centralized Architectures. CRC Press. 4 February 2013.ISBN 9781466572133
- Zeilemaker, N., Capotă, M., Bakker, A., & Pouwelse, J. (2011). "Tribler P2P Media Search and Sharing." Proceedings of the 19th ACM International Conference on Multimedia - MM ’11.
- "DecentralizedRecommendation –". Tribler.org. Archived from the original on 2 December 2008. Retrieved 9 July 2012.
- Wong, Bernard; Vigfusson, Ymir; Gun Sirer, Emin (2 May 2007). "Hyperspaces for Object Clustering and Approximate Matching in Peer-to-Peer Overlays" (PDF). Cornell University. Archived (PDF) from the original on 17 June 2012. Retrieved 7 April 2013.
- Wong, Bernard (2008). "Cubit: Approximate Matching for Peer-to-Peer Overlays". Cornell University. Archived from the original on 31 December 2012. Retrieved 26 May 2008.
- Wong, Bernard. "Approximate Matching for Peer-to-Peer Overlays with Cubit" (PDF). Cornell University. Archived (PDF) from the original on 29 October 2008. Retrieved 26 May 2008.
- "Torrent Exchange". Archived from the original on 5 October 2013. Retrieved 31 January 2010.
The torrent sharing feature of BitComet. Bitcomet.com.
- Tamilmani, Karthik (25 October 2003). "Studying and enhancing the BitTorrent protocol". Stony Brook University. Archived from the original (DOC) on 19 November 2004. Retrieved 6 May 2006.
- Kaune, Sebastian; et al. (2009). "Unraveling BitTorrent's File Unavailability: Measurements and Analysis". arXiv:0912.0625 [cs.NI].
- D. Menasche; et al. (1–4 December 2009). Content Availability and Bundling in Swarming Systems (PDF). CoNEXT'09. Rome, Italy: ACM via sigcomm.org. ISBN 978-1-60558-636-6. Archived (PDF) from the original on 1 May 2011. Retrieved 18 December 2009.
- Kaune, Sebastian; et al. "The Seeder Promotion Problem: Measurements, Analysis and Solution Space" (PDF). Queen Mary's University London. Archived (PDF) from the original on 9 August 2014. Retrieved 20 July 2017.
- "BitTorrent Specification". Wiki.theory.org. Archived from the original on 26 June 2013. Retrieved 9 July 2012.
- "» BitTorrent v2". Retrieved 27 September 2020.
- Jones, Ben (7 June 2015). "BitTorrent's DHT Turns 10 Years Old". TorrentFreak. Archived from the original on 11 June 2015. Retrieved 5 July 2015.
- "Unofficial BitTorrent Protocol Specification v1.0". Archived from the original on 14 December 2006. Retrieved 4 October 2009.
- Harrison, David (3 August 2008). "Private Torrents". Bittorrent.org. Archived from the original on 24 March 2013. Retrieved 4 October 2009.
- "BitComet Banned From Growing Number of Private Trackers". Archived from the original on 26 March 2014. Retrieved 4 October 2009.
- "I2P Compared to Tor - I2P". Archived from the original on 22 December 2015. Retrieved 16 December 2015.
- "I2PHelper HowTo - VuzeWiki". Archived from the original on 20 October 2017. Retrieved 16 December 2015.
- "Bittorrent over Tor isn't a good idea - The Tor Blog". Archived from the original on 13 October 2016. Retrieved 2 October 2016.
- Inc., The Tor Project. "Tor Project: FAQ". Archived from the original on 22 October 2016. Retrieved 2 October 2016.
- "This Website Could Be The Ultimate All-In-One Torrent Machine". 8 April 2016. Archived from the original on 8 April 2016.
- "Torrent From the Cloud With Seedr - TorrentFreak". 17 January 2016. Archived from the original on 19 April 2016. Retrieved 8 April 2016.
- "Vuze Changelog". Azureus.sourceforge.net. Archived from the original on 1 December 2006.
- "DHT Bootstrap Update | The BitTorrent Engineering Blog". engineering.bittorrent.com. Retrieved 21 November 2019.
- GitHub - bittorrent/bootstrap-dht: DHT bootstrap server, BitTorrent Inc., 11 November 2019, retrieved 21 November 2019
- Wang, Liang; Kangasharju, Jussi. (2013). "Measuring Large-Scale Distributed Systems: Case of BitTorrent Mainline DHT" (PDF). IEEE Peer-to-Peer. Archived (PDF) from the original on 12 May 2014. Retrieved 15 May 2014.
- "Khashmir.SourceForge.net". Khashmir.SourceForge.net. Archived from the original on 2 July 2012. Retrieved 9 July 2012.
- "plugins.vuze.com". plugins.vuze.com. Archived from the original on 1 August 2012. Retrieved 9 July 2012.
- "HTTP-Based Seeding Specification". BitTornado.com. Archived from the original (TXT) on 20 March 2004. Retrieved 9 May 2006.
- John Hoffman, DeHackEd (25 February 2008). "HTTP Seeding – BitTorrent Enhancement Proposal № 17". Archived from the original on 13 December 2013. Retrieved 17 February 2012.
- "HTTP/FTP Seeding for BitTorrent". GetRight.com. Archived from the original on 28 December 2009. Retrieved 18 March 2010.
- Michael Burford (25 February 2008). "WebSeed – HTTP/FTP Seeding (GetRight style) – BitTorrent Enhancement Proposal № 19". Bittorrent.org. Archived from the original on 13 December 2013. Retrieved 17 February 2012.
- "Burn Any Web-Hosted File into a Torrent With Burnbit". TorrentFreak. 13 September 2010. Archived from the original on 9 August 2011. Retrieved 9 July 2012.
- "PHP based torrent file creator, tracker and seed server". PHPTracker. Archived from the original on 19 December 2013. Retrieved 9 July 2012.
- Gillmor, Steve (13 December 2003)."BitTorrent and RSS Create Disruptive Revolution". EWeek.com. 14 December 2003. Retrieved 22 April 2007.
- Miller, Ernest (2 March 2004)."BitTorrent + RSS = The New Broadcast". Archived from the original on 23 October 2013.. The Importance of... Corante.com.
- Raymond, Scott (16 December 2003). "Broadcatching with BitTorrent". scottraymond.net. Archived from the original on 13 February 2004.
- "MoveDigital API REST functions". Move Digital. 2006. Archived from the original on 11 August 2006. Retrieved 9 May 2006. Documentation.
- "Prodigem Enclosure Puller(pep.txt)". Prodigem.com. Archived from the original (TXT) on 26 May 2006. Retrieved 9 May 2006. via Internet Wayback Machine.
- "Encrypting Bittorrent to take out traffic shapers". Torrentfreak.com. 5 February 2006. Archived from the original on 26 March 2014. Retrieved 9 May 2006.
- "Comcast Throttles BitTorrent Traffic, Seeding Impossible". Archived from the original on 11 October 2013., TorrentFreak, 17 August 2007.
- Broache, Anne (27 March 2008). "Comcast and BitTorrent Agree to Collaborate". News.com. Archived from the original on 9 May 2008. Retrieved 9 July 2012.
- Soghoian, Chris (4 September 2007). "Is Comcast's BitTorrent filtering violating the law?". Cnet.com. Archived from the original on 15 July 2010. Retrieved 9 July 2012.
- "BEP12: Multitracker Metadata Extension". BitTorrent Inc. Archived from the original on 27 December 2012. Retrieved 28 March 2013.
- "P2P:Protocol:Specifications:Multitracker". wiki.depthstrike.com. Archived from the original on 26 March 2014. Retrieved 13 November 2009.
- Johnston, Casey (9 December 2008). "Arstechnica.com". Arstechnica.com. Archived from the original on 12 December 2008. Retrieved 9 July 2012.
- Van Der Sar, Ernesto (4 December 2009). "Thunder Blasts uTorrent's Market Share Away". TorrentFreak. Archived from the original on 7 December 2009. Retrieved 15 September 2011.
- "uTorrent Dominates BitTorrent Client Market Share". TorrentFreak. 24 June 2009. Archived from the original on 3 April 2014. Retrieved 25 June 2013.
- "Windows Public File Sharing Market Share 2015". opswat. Archived from the original on 14 April 2016. Retrieved 1 April 2016.
- Henry, Alan. "Most Popular BitTorrent Client 2015". lifehacker. Archived from the original on 9 April 2016. Retrieved 1 April 2016.
- "Torrent Server combines a file server with P2P file sharing". Turnkeylinux.org. Archived from the original on 7 July 2012. Retrieved 9 July 2012.
- Anderson, Nate (1 February 2007). "Does network neutrality mean an end to BitTorrent throttling?". Ars Technica, LLC. Archived from the original on 16 December 2008. Retrieved 9 February 2007.
- Mark (7 May 2020). "How to Stream Movies and Download Torrent Files in Brave Browser". Browser Pulse. Retrieved 6 October 2020.
- See, for example,"Why Bit Torrent". Archived from the original on 28 January 2013.. tasvideos.org.
- "Sub Pop page on BitTorrent.com". Archived from the original on 14 January 2007. Retrieved 13 December 2006.
- "DGMlive.com". DGMlive.com. Archived from the original on 11 November 2013. Retrieved 9 July 2012.
- "VODO – About...". Retrieved 15 April 2012. (WebCite).
- Cory Doctorow (15 October 2009). "Vodo: a filesharing service for film-makers". Boing Boing. Happy Mutants LLC. Retrieved 15 April 2012. (WebCite)
- Ernesto. "Pioneer One, The BitTorrent Exclusive TV-Series Continues". TorrentFreak. Retrieved 15 April 2012. (WebCite)
- "CBC to BitTorrent Canada's Next Great Prime Minister". CBC News. 19 March 2008. Archived from the original on 14 June 2010. Retrieved 19 March 2008.
- "Bittorrent" (in Norwegian). Nrkbeta.no. 2008. Archived from the original on 24 October 2013. Retrieved 7 April 2013.
- "Torrents uploaded by EeuwvandeStad". MiniNova. 2009. Archived from the original on 4 November 2013. Retrieved 7 April 2013.
- Denters, M. (11 August 2010). "Tegenlicht – Download California Dreaming". VPRO.nl. Archived from the original on 26 March 2014. Retrieved 7 April 2013.
- Bol, M. (1 October 2009). "Tegenlicht – VPRO gemeengoed" (in Dutch). VPRO.nl. Archived from the original on 26 March 2014. Retrieved 7 April 2013.
- "Announcements about S3 BitTorrent discontinuation shouldn't be buried in the commit history · Issue #27 · awsdocs/amazon-s3-userguide". GitHub. Retrieved 30 September 2021.
- "Periodic update - 2021-05-13 · awsdocs/amazon-s3-userguide@0d17598". GitHub. Retrieved 30 September 2021.
- "Using BitTorrent with Amazon S3 - Amazon Simple Storage Service". 13 June 2020. Archived from the original on 13 June 2020. Retrieved 30 September 2021.
- "Blizzard Downloader". Curse Inc. 4 November 2010. Archived from the original on 26 March 2014. Retrieved 4 November 2010.
- "World of Tanks FAQ". Wargaming. 15 December 2014. Archived from the original on 18 December 2014. Retrieved 15 December 2014.
- MJ Guthrie (11 March 2013). "EVE Online reconfiguring launcher to use BitTorrent". Massively.joystiq.com. Archived from the original on 13 February 2014. Retrieved 7 April 2013.
- CCP Games (20 July 2010). "All quiet on the EVE Launcher front? – EVE Community". Community.eveonline.com. Archived from the original on 13 March 2013. Retrieved 7 April 2013.
- "Complete Download Options List – BitTorrent". Ubuntu.com. Archived from the original on 24 April 2010. Retrieved 7 May 2009.
- "BitTorrent Sync technology". Archived from the original on 30 August 2013. Retrieved 29 August 2013.
- HM Government (4 September 2012). "Combined Online Information System". Data.Gov.Uk Beta. Controller of Her Majesty's Stationery Office. Archived from the original on 26 March 2014. Retrieved 7 September 2012.
- Ernesto (4 June 2010). "UK Government Uses BitTorrent to Share Public Spending Data". TorrentFreak. Archived from the original on 27 October 2013. Retrieved 7 September 2012.
- "HPC Data Repository". Florida State University. Archived from the original on 2 April 2013. Retrieved 7 April 2013.
- Costa, Fernando; Silva, Luis; Fedak, Gilles; Kelley, Ian (2008). "Optimizing the data distribution layer of BOINC with Bit Torrent". 2008 IEEE International Symposium on Parallel and Distributed Processing. IEEE International Symposium on Parallel and Distributed Processing, 2008. IPDPS 2008. IEEE. p. 1. doi:10.1109/IPDPS.2008.4536446. ISBN 978-1-4244-1693-6. S2CID 13265537.(registration required)
- "Torrents Help Researchers Worldwide to Study Babies' Brains". Torrent Freak. 3 June 2017. Archived from the original on 5 January 2018. Retrieved 4 January 2018.
- "Academic Torrents Website". Retrieved 4 May 2020.
- Miccoli, Fräntz (2014). "Academic Torrents: Bringing P2P Technology to the Academic World". MyScienceWork. Retrieved 6 May 2020.
- Ernesto (25 June 2010). "Facebook Uses BitTorrent, and They Love It". Torrent Freak. Torrent Freak. Archived from the original on 19 April 2014. Retrieved 7 September 2012.
- Ernesto (10 February 2010). "Twitter Uses BitTorrent For Server Deployment". Torrent Freak. Torrent Freak. Archived from the original on 26 March 2014. Retrieved 7 September 2012.
- Ernesto (16 July 2010). "BitTorrent Makes Twitter's Server Deployment 75x Faster". Torrent Freak. Torrent Freak. Archived from the original on 26 March 2014. Retrieved 7 September 2012.
- Ernesto (7 August 2012). "Internet Archive Starts Seeding 1,398,875 Torrents". TorrentFreak. Archived from the original on 8 August 2012. Retrieved 7 August 2012.
- "Hot List for bt1.us.archive.org (Updated August 7, 2012, 7:31 pm PDT)". Archived from the original on 3 August 2012. Retrieved 8 August 2012.. Archive.org.
- "Welcome to Archive torrents". Archived from the original on 19 January 2016. Retrieved 22 December 2015.. Archive.org. 2012.
- "AT&T Patents System to 'Fast-Lane' BitTorrent Traffic". TheStack.com. 8 May 2006. Archived from the original on 23 February 2015. Retrieved 5 March 2015.
- "FAQ:Modems/routers that are known to have problems with P2P apps". uTorrent.com. Archived from the original on 13 September 2008. Retrieved 7 April 2013.
- Halkes, Gertjan; Pouwelse, Johan (2011). Jordi Domingo-Pascual; et al. (eds.). UDP NAT and Firewall Puncturing in the Wild. NETWORKING 2011:10th International IFIP TC 6 Networking Conference, Valencia, Spain, May 9–13, 2011, Proceedings. Springer. p. 7. ISBN 9783642207976. Archived from the original on 9 May 2013. Retrieved 7 April 2013.
- "Is torrenting safe? Is it illegal? Are you likely to be caught?". 29 November 2018. Archived from the original on 6 October 2018. Retrieved 5 October 2018.
- "The Piratebay is Down: Raided by the Swedish Police". TorrentFreak. 31 May 2006. Archived from the original on 16 April 2014. Retrieved 20 May 2007.
- "Technical report: An Estimate of Infringing Use of the Internet" (PDF). Envisional. 1 January 2011. Archived (PDF) from the original on 25 April 2012. Retrieved 6 May 2012.
- "BitTorrent: Copyright lawyers' favourite target reaches 200,000 lawsuits". The Guardian. 9 August 2011. Archived from the original on 4 December 2013. Retrieved 10 January 2014.
- Albanesius, Chloe (30 April 2012). "U.K. High Court Orders ISPs to Block The Pirate Bay". PC Magazine. Archived from the original on 25 May 2013. Retrieved 6 May 2012.
- Adamsky, Florian (2015). "P2P File-Sharing in Hell: Exploiting BitTorrent Vulnerabilities to Launch Distributed Reflective DoS Attacks". Archived from the original on 1 October 2015. Retrieved 21 August 2015.
- Berns, Andrew D.; Jung, Eunjin (EJ) (24 April 2008). "Searching for Malware in Bit Torrent". University of Iowa, via TechRepublic. Archived from the original on 1 May 2013. Retrieved 7 April 2013.(registration required)
- Vegge, Håvard; Halvorsen, Finn Michael; Nergård, Rune Walsø (2009), "Where Only Fools Dare to Tread: An Empirical Study on the Prevalence of Zero-Day Malware" (PDF), 2009 Fourth International Conference on Internet Monitoring and Protection, IEEE Computer Society, p. 66, doi:10.1109/ICIMP.2009.19, ISBN 978-1-4244-3839-6, S2CID 15567480, archived from the original (PDF (orig. work + pub. paper)) on 17 June 2013
- Pouwelse, Johan; et al. (2005). "The Bittorrent P2P File-Sharing System: Measurements and Analysis". Peer-to-Peer Systems IV. Lecture Notes in Computer Science. 3640. Berlin: Springer. pp. 205–216. doi:10.1007/11558989_19. ISBN 978-3-540-29068-1. Retrieved 4 September 2011.
|Wikimedia Commons has media related to BitTorrent.|
- Official website
- BitTorrent at Curlie
- Interview with chief executive Ashwin Navin
- Unofficial BitTorrent Protocol Specification v1.0 at wiki.theory.org
- Unofficial BitTorrent Location-aware Protocol 1.0 Specification at wiki.theory.org
- Czerniawski, Michal (20 December 2009). "Responsibility of Bittorrent Search Engines for Copyright Infringements". SSRN. doi:10.2139/ssrn.1540913. SSRN 1540913. Cite journal requires
- Cohen, Bram (16 February 2005). "Under the hood of BitTorrent". Computer Systems Colloquium (EE380). Stanford University.
Media files used on this page
Author/Creator: Wikiadd, Licence: CC-BY-SA-3.0
The BitTorrent protocol: In this animation, the colored bars beneath all of the 7 clients in the upper region above represent the file, with each color representing an individual piece of the file. After the initial pieces transfer from the seed (large system at the bottom), the pieces are individually transferred from client to client. The original seeder only needs to send out one copy of the file for all the clients to receive a copy.