Practical advice on sending large files, transferring between devices, and keeping your data private.
Email was never designed for sending large files. Gmail caps attachments at 25 MB. Outlook stops at 20 MB. If you've ever tried to send a video, a high-resolution photo collection, or a software build to a colleague, you've hit this wall. So what are your options?
Email attachment limits exist because email servers store every message — including its attachments — indefinitely on multiple servers. Allowing large attachments would balloon storage costs and slow down global mail delivery. The result is a hard 20–25 MB ceiling that hasn't meaningfully changed in years.
Workarounds like compressing files, splitting archives, or using WeTransfer require the recipient to jump through extra hoops. And cloud storage solutions like Google Drive or Dropbox require both parties to have accounts and manage folder permissions.
The cleanest solution for one-off file transfers is a link-based approach: upload the file to a temporary server, then share a single URL. The recipient clicks the link and downloads directly — no account, no app, no waiting for an email to arrive.
With SendMaster, the process takes about 30 seconds:
You can upload multiple files in a single transfer. All files are bundled under one share link. Recipients see a list of all files with their sizes and can download them individually or all at once. The total combined size of all files must stay within the 1 GB limit.
Transfer links are active for 24 hours after upload. After that, the link expires and all files are permanently deleted from the server. This is intentional — it means you don't need to remember to clean up after yourself, and recipients who download late aren't left with stale data.
If someone needs access beyond 24 hours, simply upload again and share the new link.
For most day-to-day file sharing needs — sending a project to a client, sharing a video with a friend, or distributing files to a group — a temporary shareable link is faster, simpler, and more private than any alternative.
When both devices are on the same Wi-Fi network — at home, in the office, or at a coffee shop — there's a much faster way to share files than uploading to the cloud and downloading again. SendMaster's LAN mode creates a direct device-to-device connection that bypasses the internet entirely.
LAN stands for Local Area Network — the private network created by your router that connects all devices in your home or office. Instead of sending data from your laptop to a server in a data centre and back down to a phone sitting 2 metres away, a LAN transfer sends data directly between the two devices over your router.
This matters for speed. Your home router might connect devices at 300–1,000 Mbps. Your internet connection might only be 50–100 Mbps. LAN transfers run at the faster local speed, making them anywhere from 5× to 20× faster for large files.
SendMaster uses WebRTC — the same peer-to-peer technology used by video calling apps — to establish a direct encrypted channel between two browsers. Here's how to use it:
LAN transfers have no file size limit. Since files never leave your local network, there's no server storage to worry about. The only practical limit is how much RAM the receiving browser can handle for very large files, but transfers of 10–20 GB work fine in most modern browsers.
WebRTC connections are encrypted end-to-end using DTLS-SRTP — the same encryption standard used by WhatsApp calls and Zoom meetings. Your files cannot be intercepted between devices on the same network. And since nothing is uploaded to a server, there's nothing to delete later.
Every time you upload a file to Google Drive, Dropbox, or OneDrive and share it with someone, that file has a permanent home on a remote server. The link you share may be revoked, but the file itself often lingers — in backups, in the recipient's "Shared with me" section, and in your own storage until manually deleted. For sensitive files, this is a privacy problem worth thinking about.
Cloud storage platforms are designed for long-term retention. That's great for documents you want to access in five years — but for a one-time file transfer, it means you're creating a data residue you probably didn't intend.
A temporary link that automatically expires after 24 hours solves most of these problems by design:
Not every file transfer needs a temporary link. Here's a simple guide:
For the highest level of privacy, the LAN transfer mode is ideal. Files travel directly between devices without touching any server at all. There is no upload, no download from a remote server, and no log entry. The transfer is as private as handing someone a USB drive — except faster and without the need for a cable.
Transferring files between your phone and laptop should be simple, but in practice most people end up wrestling with USB connection modes, Bluetooth pairing failures, or cloud sync delays. This guide covers every realistic method and tells you which one to reach for based on your situation.
A USB cable gives you the highest theoretical throughput — USB 3.0 can push up to 5 Gbps — but real-world speeds are often limited by the phone's internal storage speed rather than the cable. The bigger annoyance is the connection mode selector that pops up on Android when you plug in. If you accidentally tap "Charge only", the phone won't appear as a drive. On iOS, you face an "Allow this accessory" prompt and a dependency on iTunes or Finder on macOS, or the Apple Mobile Device service on Windows.
Best for: Large video files (over 1 GB) where you need the fastest possible transfer and both devices are right next to each other.
Worst for: Quick transfers, cross-platform situations (especially iOS on Windows), or when you don't have the cable handy.
Bluetooth 5.0 has a theoretical data rate of 2 Mbps, but file transfer profiles typically achieve 1–3 MB/s in practice. That means a 100 MB video takes over a minute. Pairing is usually straightforward but can be unreliable across platforms — some Android phones can't reliably send to Windows via Bluetooth without driver issues.
Best for: Contact cards, small documents (under 5 MB), and situations where you have no Wi-Fi or cable.
Worst for: Photos, videos, or anything over 20 MB.
Cloud sync is convenient when you're already in that ecosystem, but it has a hidden cost: your file goes up to a server and then back down. On a 100 Mbps connection, a 500 MB file takes about 40 seconds up and another 40 seconds down — and that's only if both devices are on fast connections. Syncing also doesn't complete instantly; there's a delay between when the file appears on one device and when it's fully synced to the other.
Cloud storage also has a privacy tradeoff. Your file sits on Google's or Apple's servers, subject to their retention policies and law enforcement requests.
Best for: Ongoing access to files from multiple devices, collaboration, archiving.
Worst for: One-time transfers, large files, or sensitive documents you don't want to store long-term in the cloud.
Apps like Nearby Share (Android) and AirDrop (Apple) use Wi-Fi Direct or infrastructure Wi-Fi to transfer files at 10–40 MB/s — much faster than Bluetooth. AirDrop works seamlessly within the Apple ecosystem but requires both devices to have Wi-Fi and Bluetooth on simultaneously and to be within about 9 metres. Android's Nearby Share has a similar range and requires both devices to be logged into a Google account for best results.
Cross-platform (iPhone to Android, or Android to Windows) is where this breaks down. Apple doesn't support AirDrop on non-Apple devices, and Nearby Share on Windows only works with Android phones.
Best for: Fast transfers within the same ecosystem (all Apple or all Android/Google).
Worst for: Cross-platform transfers or transfers to devices without the right software.
This is where tools like SendMaster stand out. As long as both devices are on the same Wi-Fi network, you can upload from your phone's browser and download on your laptop's browser — no app install, no account, no ecosystem dependency. The transfer goes via your local router and stays entirely on your local network (in LAN mode), so speeds are limited only by your router, typically 50–200 MB/s on a modern 5 GHz network.
Alternatively, you can upload from your phone on any connection (4G, 5G, home Wi-Fi) and share the link for your laptop to download — useful when the devices aren't on the same network.
| Method | Speed | Cross-Platform | Setup |
|---|---|---|---|
| USB Cable | Fast | Partial | Medium |
| Bluetooth | Slow | Good | Easy |
| Cloud Sync | Medium | Good | Easy |
| AirDrop / Nearby Share | Fast | Poor | Easy |
| Browser (SendMaster) | Fast | Excellent | None |
The shift to remote and hybrid work created a file-sharing problem that most teams solved by defaulting to whatever cloud storage they already had. Three years later, a lot of those teams are wrestling with sprawling Drive folders nobody can navigate, version conflicts, and a creeping monthly bill that only goes up as storage fills. This guide covers the practical approaches that actually work for distributed teams.
It helps to separate two fundamentally different use cases that often get lumped together:
Most teams use cloud storage for both, which is overkill for the second case. One-time delivery files clog up shared drives, create permission headaches, and stay there forever unless someone manually deletes them.
Temporary file sharing tools — like SendMaster — are a better fit for one-time delivery. You upload, share a link, the recipient downloads it, and the file disappears automatically after 24 hours. There's nothing to clean up, no permissions to manage, and no accumulation of old files in a shared folder.
Common scenarios where this works better than cloud storage:
For collaborative files that do live in cloud storage, consistent naming prevents the "which version is this?" problem. A simple convention that works: [Project]_[Description]_[YYYY-MM-DD]_[Initials]. For example: Acme_Proposal_2026-06-10_CE.pdf. Everyone on the team can sort by date and see who last worked on a file without opening it.
Folder depth matters too. More than three levels deep and people stop navigating and start searching. Keep the structure: Client / Project / Deliverables. Anything that doesn't fit gets a miscellaneous folder at the project level, not a new sub-tree.
Remote workers on residential connections often have asymmetric bandwidth — 500 Mbps down but only 20 Mbps up. A 2 GB video export takes about 13 minutes to upload on a 20 Mbps uplink. During that time, the uploader's entire household internet slows down. There are a few ways to handle this:
Remote work extends your file-sharing attack surface. A few practices that reduce risk:
You have a 500 Mbps internet connection, but uploading a 1 GB file still takes five minutes instead of the theoretical sixteen seconds. File transfer speed is one of the most misunderstood parts of computing, and the gap between the number on your broadband plan and the speed you actually see can be enormous. This article explains why, and what you can do about each cause.
Internet speeds are advertised in megabits per second (Mbps or Mb/s). File sizes and transfer software almost always report in megabytes (MB/s). There are 8 bits in a byte, so a 500 Mbps connection can transfer at most 62.5 MB/s. A file that shows as 1 GB in Explorer is 8 gigabits. The mismatch catches people out constantly.
Quick rule: divide your Mbps speed by 8 to get your MB/s ceiling. A 100 Mbps plan maxes out at 12.5 MB/s. If your speed test shows 100 Mbps and a file uploads at 11 MB/s, you're actually near the ceiling, not experiencing a problem.
Most residential broadband connections are asymmetric — download speed is much higher than upload speed. A plan advertised as "500 Mbps" typically means 500 Mbps download but only 20–50 Mbps upload. When you're sending a file to someone, you're limited by your upload speed, which is usually far slower than what's on the brochure.
Fibre-to-the-premises (FTTP) and most business connections are symmetric or close to it. Cable and ADSL connections are always asymmetric. If you're on cable and find uploads slow, this is often the reason.
Even if your connection is fast, the server you're uploading to might throttle individual connections. Free tiers of cloud storage often cap upload and download speed to encourage upgrades to paid plans. CDN-backed services can help, but only if the nearest CDN node is close to you.
For downloading, the server's outbound bandwidth matters. A file hosted on a residential server with a 100 Mbps uplink caps every downloader regardless of their connection speed. Enterprise-grade hosting uses 10 Gbps or faster uplinks and distributes load across multiple servers.
Wi-Fi adds overhead and interference that can cut your effective throughput by 30–60% compared to a wired connection. The 5 GHz band is faster than 2.4 GHz but has less range. If you're on the far side of a wall from your router, your effective Wi-Fi speed might be a quarter of what it is when you're sitting next to it.
For large file transfers, plugging into ethernet is the single easiest improvement. A gigabit ethernet port on a modern router delivers close to the router's actual capacity, without the interference and congestion of Wi-Fi.
This is the most dramatic performance gap most people don't know about. When you transfer files between devices on the same Wi-Fi or wired network (LAN), the data never touches your internet connection. A modern Wi-Fi 6 (802.11ax) router can transfer between two local devices at 500–1200 MB/s — nearly 10 times faster than a typical internet connection.
Tools like SendMaster's LAN mode take advantage of this. When both devices are on the same network, the transfer goes through the local router at local speeds. A 4 GB video that would take 10 minutes over the internet can transfer in under 30 seconds on the same Wi-Fi network.
Some files compress dramatically; others don't at all. Raw text, source code, uncompressed PSD files, BMP images, and uncompressed video footage can often be reduced by 50–80% with a ZIP or 7z archive. JPEG photos, MP4 videos, MP3 audio, and already-zipped files compress by almost nothing because they're already compressed internally.
If you're regularly sending large uncompressed files, running them through a compressor before upload can save significant time. A 2 GB uncompressed TIF file might ZIP down to 800 MB.
SendMaster uses standard HTTP uploads and Node.js streaming to handle files efficiently. For LAN transfers, the server is running on the local machine, so there is effectively no internet latency. For internet transfers, the server uses streaming to avoid buffering the entire file in memory, which keeps throughput consistent for large files.
The download progress bar shows real-time speed and an estimated time remaining, so you can see immediately whether a slow transfer is a network issue or a file-size issue. If you see speed fluctuating widely, that's usually network congestion. If it's consistently slow, check your connection type (Wi-Fi vs wired) and your upload/download plan speeds.
© 2026 Master Brains Solutions. All rights reserved.