<?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: Emily Park</title>
    <description>The latest articles on DEV Community by Emily Park (@dropanyfiles).</description>
    <link>https://dev.to/dropanyfiles</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254562%2Ff081a5c5-0f50-4d94-a69d-d7d6bd804215.png</url>
      <title>DEV Community: Emily Park</title>
      <link>https://dev.to/dropanyfiles</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dropanyfiles"/>
    <language>en</language>
    <item>
      <title>Sending Files Phone to PC Without an App: What WebRTC Can and Cannot Do</title>
      <dc:creator>Emily Park</dc:creator>
      <pubDate>Thu, 19 Nov 2026 22:30:57 +0000</pubDate>
      <link>https://dev.to/dropanyfiles/sending-files-phone-to-pc-without-an-app-what-webrtc-can-and-cannot-do-5fh1</link>
      <guid>https://dev.to/dropanyfiles/sending-files-phone-to-pc-without-an-app-what-webrtc-can-and-cannot-do-5fh1</guid>
      <description>&lt;p&gt;Every time I want to move a photo from my phone to my laptop, I go through the same ritual: find a cable, plug it in, wonder why the laptop does not see the phone, then email the photo to myself. It works, but it feels like a workaround for a problem browser APIs solved years ago. Here is what I learned while looking into browser-based transfer tools, and why &lt;a href="https://drop-any.com/" rel="noopener noreferrer"&gt;DropAny&lt;/a&gt; is a decent example of the pattern.&lt;/p&gt;

&lt;h2&gt;
  
  
  The core idea: a DataChannel instead of a server
&lt;/h2&gt;

&lt;p&gt;WebRTC is usually associated with video calls, but &lt;code&gt;RTCDataChannel&lt;/code&gt; is just a bidirectional pipe between two peers. For file transfer you need three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Signaling.&lt;/strong&gt; Two browsers that have never met need to exchange SDP offers and ICE candidates. That requires a tiny server, but the server only relays text — the files never touch it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A pairing step.&lt;/strong&gt; Typing a long room ID on a phone keyboard is miserable, so most tools generate a short one-time code. DropAny uses a 6-digit code or a QR scan, which is single-use and expires after 10 minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chunked sending.&lt;/strong&gt; You cannot push a 500 MB file into a DataChannel in one call. You slice the file with &lt;code&gt;file.slice()&lt;/code&gt; and send chunks, watching &lt;code&gt;bufferedAmount&lt;/code&gt; so the channel does not back up.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What works surprisingly well
&lt;/h2&gt;

&lt;p&gt;Once the channel is open, transfers are fast on a local network because traffic goes device to device instead of across the internet twice. Because the transport is DTLS-encrypted, the sender and receiver are the only parties that see the bytes — which is a real argument when you are moving scans of a passport or a medical letter.&lt;/p&gt;

&lt;p&gt;In my case the win was cross-platform. Sending from an iPhone to a Windows machine is exactly the scenario where the usual ecosystem tools fail loudly, and a WebRTC page does not care about the operating system on either side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it still hurts
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No resume.&lt;/strong&gt; A DataChannel does not survive a network switch. If Wi-Fi drops halfway through a large video, most of these tools restart from zero.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tabs die.&lt;/strong&gt; A backgrounded mobile tab can be frozen by the OS. Keep the screen awake and the tab in front.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not every network allows it.&lt;/strong&gt; Symmetric NATs and some corporate firewalls require a TURN relay; if a tool only ships STUN servers, peers on the same network are fine but anything harder may fail.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The honest summary
&lt;/h2&gt;

&lt;p&gt;If you need reliable, resumable bulk transfer of huge archives, a sync client is still the right tool. If you need to move a handful of files between two devices, once, without installing anything, the browser route is now genuinely good. DropAny leans into that narrow but very common case: no app, no account, no upload to a server, and the files simply go from one device to the other.&lt;/p&gt;

&lt;p&gt;For a web developer, the more interesting takeaway is how little code this takes now. A pairing UI, a signaling socket, and a chunked send loop on top of &lt;code&gt;RTCDataChannel&lt;/code&gt; is a weekend project — and unlike most weekend projects, people actually use it.&lt;/p&gt;

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