EP 21: LOCALSEND: FREE CROSS-PLATFORM FILE TRANSFER TOOL
DESCRIPTION
"Moving a file three feet shouldn't require a round trip to a distant server. LocalSend is a free, open source app that moves files, folders, and text directly over your own network with end-to-end TLS and no accounts, ads, or tracking. If you live with a mix of Windows, macOS, Linux, Android, and iOS, it's the rare tool that treats every platform like a first-class citizen.
I start with the familiar pain: emailing yourself photos, juggling cloud links, hitting the wall when AirDrop meets Windows. Then the design that fixes it: local discovery, a small HTTPS server on each device, and direct encrypted transfers at LAN speed. No relays, no Bluetooth handshakes, and the no-internet requirement is sometimes a feature, like on a travel router when hotel Wi-Fi is garbage.
I also cover the failure modes honestly, because "devices don't see each other" has real causes: mismatched SSIDs, AP isolation, strict firewalls, and VPNs hijacking local subnets. There's a short checklist that fixes most of it. If you know someone who still emails themselves attachments, send them this one."
TRANSCRIPT — EP 21
Here's a question that really shouldn't be that hard in 2026. You just walked off of a transmitter site. Your phone is full of photos, antenna connections, transmission line routing, the inside of a combiner cabinet that you've been trying to document for the last three months, maybe some wiring diagrams, how things are currently hooked up. Your laptop is sitting right there, right next to you. They're on the same Wi -Fi and somehow the default answer for most people is either email it to yourself or upload it to Dropbox, OneDrive, Google Drive and download it on the other side. You literally just bounce the photo of your transmission line
to another state just to get it from your phone to your laptop. And look, if you're in the Apple world, AirDrop handles this and handles it pretty well. But most engineers I know are not fully in one ecosystem. They're not fully in the Apple world, Windows world, what have you. Maybe you've got a Windows machine at the shop, a Linux box in the rack, an Android phone in your pocket, and whoever you're working with that day just so happens to have an iPhone. The second anything non -Apple shows up, AirDrop just stops, doesn't try, doesn't negotiate, just done. This is the
Tyler Woodward Project, and today I want to talk about a tool that solves this without asking you to pledge your allegiance to any one ecosystem. The app is called Localsend. It's free, it's open source, and it moves files directly between devices on your local network. Windows, macOS, Linux, Android, iOS, All of them, same app, same experience, no cloud provider in the middle, no accounts. No, please update your payment method before you can share this PDF. Just your devices talking to each other on whatever network you're on. I'm going to walk you through how it actually works, where it's actually useful for broadcast engineering, where it might fall a little short.
Why I think this is one of those quiet tools that deserves Way more attention in this industry than it currently gets So let's start with the basics local send is a peer -to -peer file transfer app You can install it on all your devices and as long as they're on the same local network They show up in a list and you can send stuff between them. That's the entire pitch But the details, I mean, they do matter. Because the details are what makes this different from just another file sharing app. First, it's genuinely cross -platform. Windows, macOS, Linux, Android,
iOS, all supported as equals. Linux is not an afterthought here. You get Debian packages, app images, arm builds for raspberry pi the whole spread all of it that matters if you're running a mixed shop which in broadcast is everyone second it's fully offline not offline with an asterisk not offline but we ping a server for discovery there is no local send cloud your data goes from the you know your device device a to device b over your local area network. And that's where the story ends. Third, it's open source. No ads,
no tracking, no data collection. The code and the protocol are both on GitHub. If you want to know exactly what it's doing, you can read it for yourself. Now, let me walk you through what actually happens when you tap send. Because once you understand it, you'll also understand why it breaks when it breaks. Both devices need to be on the same local network, same Wi -Fi SSID, same ethernet segment, or a setup where those share a subnet. If your phone is on the shop Wi -Fi and your laptop is on the guest SSID, they might feel close, but they're invisible
to each other. Different VLANs, different broadcast domains, local SIN, can't send across that. From there, each local send instance runs a small HTTPS server, typically on port 53317, and uses local network announcements so other devices can find it. From your side, you just see a list of friendly device names. Tyler PC, Tyler Pixel, Tyler ThinkPad. Behind the scenes, That's IP addresses and service discovery doing the work When you pick a target and send the file local send opens a direct HTTPS connection between
the two you know the two devices and Streams the data across it no relay. No middleman speed is basically whatever your land can handle on decent Wi -Fi 6 or ethernet people regularly You know, see 20 to 50 plus megabytes per second. The bottleneck is your hardware and your disk, not some cloud rate limit. All transfers are wrapped in TLS with self -signed certificates that each device generates locally. So even on a shared network, someone passively sniffing traffic just sees encrypted blobs. And because it's open source, this isn't trust us. You can
look at the protocol spec. You can read the code, build it from source if you're the paranoid type. And that's not a criticism. Being paranoid is kind of, well, you're doing the correct thing in this industry nowadays. Okay. So let's talk about where this actually fits in the broadcast workflow. Because the use cases are different from, I just want to send a photo. to my wife. Site documentation. This is probably the biggest one for me. You go out to a site, you shoot some photos of a rack layout, the coax runs, the grounding system, the antenna connections. You've got maybe let's say 40, 50 photos on your phone by the
time you leave. Getting those onto your laptop to actually label them, organize them, put them in a folder. maybe add them to whatever site documentation setup you have, that friction, it's real. If you're an Android to Windows person, you're either plugging in a USB cable or bouncing everything through Google Photos or a cloud drive and hoping the upload didn't compress them in the garbage. Local send, you open the app, you... see your laptop in the list, select all the photos, they land in your download folder at full resolution, zero compression, and about 10 seconds on a really
good hotspot. Let's talk about manuals and PDFs. This one, I use it for, I use this constantly. You've got a PDF of an Orban 8500 manual on your laptop. You're standing at the rack. and you want to reference the AGC parameter table, whatever, without going back to your laptop constantly. Or you've got a spec sheet. Your colleague just emailed you on your phone and you need it on the machine that's actually connected to the equipment. LocalSend makes that a five second problem instead of let me email this to myself and hope the attachment. you know, doesn't get eaten by the virus scanner or whatever on your
email hosting service. Firmware and config files. This is where cross -platform matters most. Picture this. You've got a config backup from a Telo system on your Windows machine. You need to move it to a MacBook because that's what the other engineer on the project is using. Or you've got a firmware update on your Linux workstation and you need to get it onto USB Drive that's formatted on a Windows laptop. LocalSend handles all those transfers cleanly without you having to care what OS either device is using. I got a couple more, stick with me here. iOS to Windows. We
know how painful that can be. If you have an iPhone and a Windows machine, There is genuinely no good native way to move files between them. You can use iCloud. Sure, but that requires everyone to have an Apple ID and a cloud subscription. You can plug in a USB cable, but then you're dealing with iTunes or the Windows Photos app, which is its own nightmare. LocalSend makes iOS and Windows talk to each other. like they were designed to do that from the start. Which, well, we clearly know they weren't. And again, couple more. Android to Mac, same problem, different
direction. Apple doesn't support Android file transfer natively on any meaningful way. LocalSend, again, is the answer. Install it on the Pixel, install it on the MacBook, same network, done. Linux. to anything This one. Oh my god. I feel this one personally If you run Linux, you know the routine most consumer filed tools either don't support Linux at all or They throw you a half -baked web UI and pretend that counts in some meaningful way KDE connects is great if you're in the KDE desktop environment world,
but it gets rough on non -KDE setups and basically doesn't exist on Apple platforms. Except maybe the iPhone, I think. LocalSend treats Linux like a first -class citizen. There are Debian packages, app images, arm builds, same app, same features, same flow as every other platform. For a community that's used to being an afterthought, That actually means a lot to us. You have no idea. Let me also talk about what this looks like in the field. You're at a remote site. You got no internet connection or maybe some garbage DSL connection out in the boonies. Maybe you're on hotel wifi,
a cellular hotspot, whatever. You throw up a travel router. You tether your phone. Now you've got a tiny little local network. Locosyn works perfectly on that. You're not depending on upload bandwidth. You're not waiting for a cloud sync. It's just your devices, your little network bubble and direct transfers at whatever land speed it can support. That's where the no internet required thing stops being a bullet point and becomes an actual useful thing. You're at a transmitter site, let's say at 11 o 'clock at night. Trying to document what you just fixed before you drive home. The last thing you want to do is have to
wait for your cloud drive to sync through a weak cell signal. I've done that way too many times. Now, let's be honest about where this goes sideways, because yeah, I'm not just going to give you the benefits. I'm also going to give you the pitfalls as well. The number one complaint you'll see is my devices don't see each other. And almost every time, the answer is not that local send is broken, it's that your network is doing exactly what someone configured it to do. Different SSIDs, maybe different VLANs, your phone is on the guest Wi -Fi, laptop is on the main Wi -Fi. They can't find each other. Pretty straightforward, right? Move them to the same Wi -Fi network, the same SSID or the same VLAN. AP isolation, some routers.
especially in default configurations, prevent devices on the same SSID from talking to each other directly. That kills local send discovery instantly. Usually you can fix that by turning off client isolation. VPN interference. If you're running a VPN tunnel that's routing all your traffic through a tunnel, your device might not treat the local network as actual local anymore. LocalSend discovery, you know, the packets are getting swallowed by that tunnel. So that's not going to work. Check that firewall on Windows, especially if you denied the allow this app on private networks prompt, you've blocked it on
Linux. If your inbound ports are locked down with IP tables or UFW, same deal. LocalSend needs to listen on port 53317. What else is there? Mobile OS background restrictions. Both Android and iOS aggressively will kill apps in the background to save battery. If local send isn't in the foreground, it might not be discoverable. So check that. Make sure you actually have it open right there on your screen. My mental model kind of goes to this. First, you know, check the SSID, check the VLAN, check VPN, check firewall. In really that order, then you can blame the app. Here's
the quick setup checklist if you want to hit the ground running. Install from the official sources, the app store on iPhone, Google Play on Android, the project's own download page or your distro's package manager. Don't grab random clones from sketchy mirror sites. Name your device as something useful like Tyler -PC, Tyler -Pixel, Tyler -ThinkPad. Future you is really going to appreciate it when you're in a hurry and there are four unnamed devices in the list and you're trying to figure out which one's which. Verify your network. Make sure all devices are on the same SSID or subnet. Turn off IP isolation, client isolation if your router has that sort of stuff
enabled on the network you're trying to use. If you're on a VPN, either disconnect it or set up a split tunnel for local traffic. Allow it through your firewall on the device. On Windows, say yes to the private network prompt. On Linux, make sure port 53317, TCP, and UDP are open. And on macOS, accept the incoming connections dialog. Set a same download folder that you can remember. On desktop, point it somewhere you'll actually be able to get to or look or remember. On mobile, know where files land so they don't feel like they just disappeared into a black hole somewhere. And then, tell people you work with that this exists. It's a hundred times more useful when the whole team is using it. After
all that, here's where I land on this. You don't need to be locked into Apple's ecosystem or or even Google's or anyone to get fast and reliable nearby file sharing. LocalSyn proves that the basic networking your Wi -Fi already does is more than capable of handling this. And it does it all with encryption without the cloud and without asking for a dime. AirDrop is fine if it works for you. keep using it i got no problem with that i'm just trying to give you some alternatives but if you're an engineer who runs a mixed shop and honestly that's probably most of us and you're tired of the friction of moving files between
oses local send is a really good answer to that frustration pick pick the two devices that give you the most trouble install local send on both give it a few minutes I think you'll be surprised at how fast this becomes the way you do it going forward. That's the whole show. If you want more episodes like this, visit TylerWoodward .me for show notes, links and the ways to support the show. Follow me at TylerWoodward .me on threads, blue sky, Instagram. You can also reach me on matrix if you want matrix .TylerWoodward .me and subscribe and rate the show on your favorite podcast platform. If you know another engineer. who's still emailing site photos to themselves,
just get them off the phone. Do them a favor, send them this episode. I'll catch you next week.