How to Send Large Files Without Uploading Them Anywhere
Email stops at 25 MB, a free transfer service at 3 GB and three days. Five routes for a big file, and what each one costs you.
The export finished at four in the morning and reported 4.2 GB. The client asked for it by email. Gmail takes 25 MB, so the attachment failed before it started, and the next hour went into signing up for something.
Most people solve it by uploading. The file goes to a server, a link comes back, and the recipient downloads it again. That works, and it costs more than it looks: time at both ends, a copy of your file on somebody else's disk, and a link that stops working when the plan does.
There are five routes for a file that will not fit in an email. They differ in ceiling, speed, and where the file ends up afterwards.
Where the ceilings actually are
Email is the tightest. Gmail allows 25 MB on the way out and 50 MB on the way in, and most mail servers sit in the same range, around 20 to 25 MB. Anything bigger becomes a link to a cloud file, which is a different route wearing an email's clothes.
The transfer services are bigger and stranger. WeTransfer's help pages in October 2026 describe the free plan as 3 GB per transfer, with a rolling allowance of about 10 transfers or 3 GB in total every 30 days, whichever you hit first, and download links that expire after three days. So a 4.2 GB video doesn't fit the free tier at all, and a 2.9 GB one fits once or twice a month before the allowance runs out.
Cloud drives have no fixed ceiling. You pay for storage, and you pay again in the time it takes to push the file up your upstream connection.
Your own network has no ceiling at all. The size of the file stops mattering and only the transfer speed does.
Route one: make the file smaller
Before choosing a pipe, check whether the file needs to be that big. A 4.2 GB screen recording is usually a bitrate decision rather than a length decision. Re-encoding at a lower quality target often halves it with nothing visible lost, and forty minutes of 1080p at a sensible bitrate lands under a gigabyte.
VideoRoast does this without a cloud account. The filmstrip trim converts only the section you keep, so a two minute clip cut from the middle of a long capture never expands to the full length. There is a CRF slider if you want to choose the balance yourself, a target bitrate if you would rather name a number, and resolution presets down to 480p. Hardware acceleration through NVENC or Quick Sync keeps the encode short. Saved presets handle a whole folder the same way.
For stills, TinyImage re-encodes a photo or screenshot smaller and leaves the dimensions alone, so a 12 MB phone photo arrives as a 2 MB one that still looks right in a document. TinyPDF writes a smaller copy of a PDF beside the original and keeps the text selectable. Both are on the menu, and both run on your machine. The compression guide covers the settings in more detail.
Shrinking is the cheapest route when it works. It also fails often enough to matter: raw footage, a disk image, a database export and a print-ready PDF at 300 DPI don't shrink usefully, and no amount of re-encoding will help.
Route two: a cloud link, and what you pay for it
Drive, Dropbox and iCloud all turn a big file into a link. The upload is the cost. On a 20 Mbps upstream connection, 4.2 GB takes about 28 minutes with nothing else using the line. On a 100 Mbps connection it is closer to six. Downstream at the other end is usually faster, but the recipient still waits.
Then there is what you agreed to. The file now sits on a server under a retention policy you probably have not read. The link is often "anyone with the link can view" by default, which is convenient until it is forwarded. And the copy isn't a loan. Deleting it later doesn't reach the version that was already downloaded.
For a wedding video this is fine. For a signed contract, a payslip, a medical letter or a client's financial model, it is a decision about where that document lives tonight, and it is worth making on purpose rather than by reflex.
Route three: a transfer service
Services in this category do one job well: they give a stranger a link with no account needed on their side. The differences between them are almost entirely the free cap, the monthly allowance, and how long the link survives.
That last number matters more than people expect. A three day link is fine when the recipient is at their desk. It fails when they are travelling, when the email lands in a spam folder, or when they open it on Monday. Uploading 4.2 GB twice because the first link expired is a bad afternoon.
Two habits make these services behave: send the link in a message you can follow up on, so you know when it was opened, and pick the shortest expiry that still covers the recipient's week rather than the longest one offered.
Route four: your own network
If both people are in the same building, the file doesn't need the internet at all. A local transfer moves bytes across the Wi-Fi router in the room, at LAN speed, with no server in the middle and no size limit.
FileShipper is the free app for this. Open it and your computer sits at the centre of a radar with the nearby devices around it. Another Mac or PC running FileShipper appears as a bubble; tap it, pick the files, done. Phones join by scanning a QR code, which opens a plain web page in the browser for sending and receiving, so nobody installs anything on the phone.
The arithmetic is the argument. A 4.2 GB file over a decent Wi-Fi 6 link moves at something like 50 to 80 MB a second, which is roughly a minute. The same file over a 20 Mbps upstream connection is half an hour. Same file, same two people, two different physical paths.
The limits are real. Both ends have to be on the same network, so this solves the colleague down the corridor and does nothing for the client in another country. The receiving machine has to be awake and accepting. And on shared Wi-Fi, in a café or an office guest network, turn the PIN on so only the people you trust can connect.
If both computers are Apple, AirDrop does the same job with no app at all. It refuses to talk to Windows, which is why the Mac to Windows transfer guide exists as a separate piece of reading.
Route five: hand over a drive
Past a certain size the network stops being the right tool. Two hundred gigabytes of raw footage, a full photo library, a machine backup: copying to an external SSD and putting it in a courier's hands is faster in wall clock terms than any upload, and it has no ceiling.
Format the drive exFAT if it has to be read on both Windows and a Mac. Copy in one pass rather than several, then compare the two trees before you seal the box. FileSteep lists what is missing from each side, which turns "I think it copied" into a list of filenames.
What each route costs
| Route | Ceiling | Time for 4.2 GB | Where the file lives afterwards |
|---|---|---|---|
| 25 MB | Does not apply | Your sent folder, for the small ones | |
| Shrink first | Whatever you get it down to | Minutes of encoding | Exactly where it already was |
| Cloud link | Your storage plan | 6 to 30 minutes up, then down again | On a server, under their policy |
| Transfer service | 3 GB free, more when paid | Same as cloud, plus the link expiry | On their server, for a few days |
| Your own network | None | About a minute on good Wi-Fi | On the recipient's disk, nowhere else |
| A drive by post | None | Overnight, plus delivery | In the recipient's hand |
The two questions that decide it
Ask where the recipient is, then ask what the file is.
Same building, and the file is nobody else's business: local transfer, every time. Different city: shrink it if you can, then pick a cloud link or a transfer service, knowing the file spends the week on their server.
The second question is the one people skip. A marketing video can sit on someone else's server for a week. A folder of client tax documents should not, and the local route exists precisely because the awkward files are the ones where uploading is the wrong answer.
Where the native apps fit
Every app named here runs on your own machine, and any of them works with the Wi-Fi off.
FileShipper moves files across the room and asks for nothing. VideoRoast and TinyVideo cut a large video down to a size that fits whatever pipe you have. TinyImage and TinyPDF do the same for photos and documents. PressZip splits an archive into parts when a portal upstream refuses anything over a fixed limit, and joins them back at the other end. ChatCafe carries files and messages between machines on one network when you want a conversation alongside the transfer. FileSteep compares two folders so a copy is verified rather than assumed.
What none of them does is replace a transfer service for someone on another continent. There's no server here to hold the file while they sleep, and that's the trade: no account, no upload, no expiry, and the requirement that both ends be reachable at the same time.
A routine that avoids the mess
Keep attachments under 20 MB and email stays reliable. Reach for the local route when the other person is in the building, because it is faster than any upload and leaves no copy behind. Shrink a video before paying to move it. Pick a link expiry that covers the recipient's week, and follow up on the message rather than assuming silence means it arrived. And for anything confidential, ask where the file will be sitting at midnight before you press send.
The file at the end is an ordinary file in a folder you chose, on a disk you can point at. That is the part worth protecting.
One menu, one subscription
The 128 apps on the menu install on macOS, and 106 of them also install on Windows, FileShipper included. Solo Cup is $3.99 a month, or $1.99 a month billed yearly at $23.88. Family Roast covers five computers at $7.99 a month, or $3.99 a month billed yearly at $47.88, and each computer you sign in on takes a slot that is freed the moment you remove that device. The 7-day free trial adds a card when it starts and charges nothing until it ends.
Start the trial or browse the menu first.