WebRTC

by

What is WebRTC? How Peer-to-Peer File Transfer Works in Your Browser

You’ve probably used file transfer tools that upload your files to a server before the other person can download them. But a newer approach — peer-to-peer (P2P) transfer — lets files move directly between two browsers without touching any server at all. This is how BeamQR works, and the technology behind it is called WebRTC.

What is WebRTC?

WebRTC stands for Web Real-Time Communication. It’s an open-source technology built into all modern web browsers — Chrome, Firefox, Safari, and Edge — that allows browsers to communicate directly with each other in real time.

WebRTC was originally developed for video calls and audio streaming in browsers (so you don’t need to install Skype or Zoom to take a call). But it can also be used to transmit data — including files — between two browsers with no server in between.

Because WebRTC is built into the browser itself, no plugin or extension is needed. Any modern browser supports it automatically.

How Traditional File Sharing Works (The Old Way)

In a typical file sharing service:

  1. You upload your file to a company’s server (WeTransfer, Google Drive, Dropbox)
  2. The file is stored on that server
  3. You send a link to the recipient
  4. They download the file from the server

Your file goes: Your device → Server → Recipient’s device

This works, but it means your file passes through and is stored by a third party. It also means the transfer speed is limited by your upload speed, then again by the recipient’s download speed.

How Peer-to-Peer Transfer Works (The New Way)

With WebRTC:

  1. One browser generates a session ID (often displayed as a QR code)
  2. The second browser connects to that session ID
  3. WebRTC establishes a direct communication channel between both browsers
  4. Files flow directly from one browser to the other

Your file goes: Your device → Recipient’s device

No server handles the file content. The file is never uploaded or stored anywhere external.

The Role of the Signaling Server

There’s one small technical caveat worth mentioning. Before two browsers can talk directly, they need to find each other — they need to exchange some initial connection information (called “signaling”).

This does use a server, but only to pass that initial handshake message. Once the connection is established, the server steps out of the way and the file data flows directly between devices.

Think of it like a postal address: you need to know someone’s address before you can send a letter, but the postal service doesn’t open or copy your letter. The signaling server knows that two devices want to connect, but it never sees the files being transferred.

Why P2P Transfer is More Private

When files go through a company’s server:

  • The company has a copy of your file
  • Their privacy policy governs how long they keep it
  • Their security practices determine how well it’s protected
  • If they experience a data breach, your files could be exposed

When files move peer-to-peer via WebRTC:

  • No company ever receives your file
  • Nothing is stored anywhere except on the sender’s and receiver’s devices
  • When the session ends, the connection is gone — there’s nothing to breach
  • Even the service provider cannot see what was transferred

What Makes WebRTC Fast

Because there’s no upload step to a third-party server, WebRTC transfers are often significantly faster than cloud-based alternatives, especially on a shared local network.

Two devices on the same Wi-Fi network can transfer files at speeds close to the local network’s capacity — often 50–100+ Mbps in practice. This means a 1GB file can move in under two minutes on a typical home network.

Over the internet (two devices in different locations), speed depends on both connections, but the direct routing typically outperforms cloud uploads that route traffic through data centres.

Which Tools Use WebRTC?

Several modern file transfer tools use WebRTC technology:

  • BeamQR — QR-based, browser-to-browser, no account
  • Snapdrop — local network only
  • PairDrop — open source, local network
  • ToffeeShare — browser-based P2P

The approach is becoming more common as people become more aware of the privacy implications of uploading files to external servers.

Summary

WebRTC is the technology that makes it possible to transfer files directly between browsers, skipping servers entirely. It’s built into every modern browser, making it accessible without any installation.

The result is a file transfer method that is faster on local networks, more private by design, and requires no account, no storage quota, and no waiting for uploads to complete.

See WebRTC in action: Try BeamQR →