A Quick Checklist Before You Send a Large File

October 4, 2026

Large transfers are exactly where small oversights turn into a wasted twenty minutes. A sixty-second check beforehand avoids most of it.

1. Confirm it's actually the file you mean to send

Obvious, but the single most common real mistake. A quick check of the filename, and a preview, if it's a document or image, is worth it, especially for anything with version numbers or similarly-named files nearby.

2. Check both devices' power and screen settings

A transfer that outlives your laptop's sleep timer or your phone's screen lock is asking for a stall. For a genuinely large file, turning off sleep and screen-lock on both ends for the duration is worth the extra step.

3. Pick a stable network over a fast-looking one

A strong Wi-Fi signal indicator isn't the same thing as a stable connection. Given a choice between flaky public Wi-Fi and a slower but steady mobile connection, steady wins for a large, uninterrupted transfer.

4. Decide files vs. one archive upfront

Sending a folder as individual files, rather than zipping it into one archive first, means a hiccup only costs you that one file's retry, not the whole batch starting over from zero.

5. Know roughly how big 'large' is for your connection

There's no universal size limit on a direct transfer, but the honest expectation-setter is your own upload and download speed, a file that feels instant on office fiber can be a real wait on mobile data, and that's normal, not a sign something's wrong.

6. Have a fallback in mind if the transfer stalls partway

Knowing in advance what you'll do if a transfer stalls saves real time in the moment. For a folder, check which individual files actually finished before retrying, rather than restarting the whole batch blind. For a single large file, having a backup plan, a different network, a different device to try from, ready before starting means less scrambling if the first attempt doesn't go smoothly.

7. Tell the recipient roughly what to expect

A quick heads-up, "sending a large video, should take a few minutes", does more than it seems like it should. It means the recipient isn't wondering halfway through whether something's broken, and it sets a rough time expectation that makes an actually-stalled transfer easier to notice, since they'll know it's taking longer than what you said to expect from it.

A note on very large folders specifically

For a folder running into the hundreds of individual files, it's worth doing a rough sanity check on the total count and size before starting, rather than discovering partway through that it's dramatically bigger than expected. A quick look at a folder's properties or file count takes seconds and avoids the surprise of a transfer running far longer than anticipated because of files buried in a subfolder nobody remembered were there.

Why this checklist matters more for a one-shot handoff

All of this matters more for a transfer that genuinely has to work correctly the first time, handing something off in person, on a deadline, or to someone who won't easily be available to retry with later. For a casual, low-stakes send, skipping straight to it is completely reasonable; the checklist earns its keep specifically when getting it right on the first attempt actually matters.