<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 5g Chat</title>
    <description>The latest articles on DEV Community by 5g Chat (@5gchat).</description>
    <link>https://dev.to/5gchat</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3955156%2F879f3681-fcce-4b47-94b4-f0e0a5a2ed60.png</url>
      <title>DEV Community: 5g Chat</title>
      <link>https://dev.to/5gchat</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/5gchat"/>
    <language>en</language>
    <item>
      <title>5g.chat – Instant P2P file transfer in your browser, no server, no account</title>
      <dc:creator>5g Chat</dc:creator>
      <pubDate>Wed, 27 May 2026 20:50:53 +0000</pubDate>
      <link>https://dev.to/5gchat/5gchat-instant-p2p-file-transfer-in-your-browser-no-server-no-account-4ki0</link>
      <guid>https://dev.to/5gchat/5gchat-instant-p2p-file-transfer-in-your-browser-no-server-no-account-4ki0</guid>
      <description>&lt;p&gt;I want to share a tool that solves a problem every developer runs into constantly: getting a file from one device to another as fast as possible, without friction.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;You're on your phone and need to get a screenshot to your laptop. Or you need to send a file to someone in the same room. The usual options: AirDrop (Apple only), email it to yourself, upload to Google Drive, or fumble with a USB cable. All slower than they should be.&lt;/p&gt;

&lt;h2&gt;
  
  
  What 5g.chat does
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://5g.chat" rel="noopener noreferrer"&gt;https://5g.chat&lt;/a&gt;&lt;/strong&gt; — open it in any browser, pick your files, get a 6-digit code. Open it on the other device, enter the code. Files transfer directly, device to device. Done.&lt;/p&gt;

&lt;p&gt;No account. No app. No file size limit. Works on Chrome, Safari, Firefox, Edge.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works under the hood
&lt;/h2&gt;

&lt;p&gt;It uses &lt;strong&gt;WebRTC data channels&lt;/strong&gt; — the same technology that powers browser-based video calls, but used here to stream raw file bytes directly between two browsers.&lt;/p&gt;

&lt;p&gt;The architecture:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A lightweight &lt;strong&gt;WebSocket signaling server&lt;/strong&gt; brokers the initial connection (SDP offer/answer + ICE candidate exchange), then steps aside entirely&lt;/li&gt;
&lt;li&gt;Once the RTCPeerConnection is established, the server sees nothing — files go device-to-device&lt;/li&gt;
&lt;li&gt;Files are chunked at &lt;strong&gt;16 KB&lt;/strong&gt; with a &lt;strong&gt;256 KB bufferedAmount ceiling&lt;/strong&gt; for backpressure management&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;STUN only&lt;/strong&gt; (Google and Cloudflare public servers) — pure P2P, no TURN relay&lt;/li&gt;
&lt;li&gt;Sessions and codes expire after &lt;strong&gt;30 minutes&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Client-side QR code generation for easy mobile pairing&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why this matters for privacy
&lt;/h2&gt;

&lt;p&gt;The server's only involvement is helping two browsers find each other across NAT. It never touches the file payload. Nothing to store, nothing to log, no account to breach.&lt;/p&gt;

&lt;p&gt;WebRTC data channels are encrypted via DTLS — transport-layer encryption, so the connection itself is secure.&lt;/p&gt;

&lt;h2&gt;
  
  
  The use case
&lt;/h2&gt;

&lt;p&gt;Getting a file from point A to point B in under 30 seconds, with nothing to install on either end. That's it.&lt;/p&gt;

&lt;p&gt;Try it: &lt;strong&gt;&lt;a href="https://5g.chat" rel="noopener noreferrer"&gt;https://5g.chat&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Curious to hear feedback — especially from anyone who's hit NAT traversal issues with pure STUN setups.&lt;/p&gt;

</description>
      <category>webrtc</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>privacy</category>
    </item>
  </channel>
</rss>
