Why large file uploads fail, and how to stop it happening

Why big files fail more often than small ones

Size mostly means time. A twelve megabyte photo uploads in a couple of seconds, so a brief network hiccup barely registers. A full RAW shoot or a wedding video project can take an hour or more, and an hour is long enough for something to go wrong somewhere in the middle: a wifi drop, a laptop that decides to sleep, a VPN that reconnects.

The real problem is how most upload tools handle that failure. A lot of them treat the whole file as one long request. Break the connection once, anywhere in that hour, and you start the whole thing over from zero. That's the part that actually wastes your evening, not the file size itself.

The usual suspects

• Unstable wifi, hotel and venue networks especially. A signal that's fine for browsing can still drop the sustained connection a big upload needs.
• Your laptop or phone falling asleep. Most devices dim, lock, or suspend background activity after a few idle minutes, and that's enough to kill an upload mid transfer.
• Switching away mid upload on a phone. Moving to another app can pause or stop the browser tab doing the work.
• A file that's still syncing from a cloud folder. If a RAW file lives in Dropbox or Google Drive and hasn't finished downloading locally, the browser can lose access to it partway through.
• Running into your plan's file size limit partway through adding files, instead of checking before you start.

Set yourself up before you hit upload

Most of what actually prevents a failed upload takes thirty seconds and happens before you ever click upload.

• Plug in. A wired connection is more stable than wifi for anything over a few gigabytes, and plugging in power skips your laptop's own sleep settings too.
• Check the total against your plan's limit first. Free accounts cap at 5 GB per transfer, Pro at 50 GB, Max at 250 GB. The exact numbers per plan are in the file size limits guide. Trim the file list before you start rather than partway through.
• Keep the tab open and the device awake for the whole upload, especially on a phone.
• If a source file is still syncing from a cloud drive, wait for the sync icon to clear before adding it. RAW files and layered exports are exactly the ones this catches.

What should happen when your connection drops anyway

Network drops happen even with all of that. What matters is whether the tool you're using treats that as the end of the upload or as a pause. ZappFiles uploads large files in chunks rather than one long request, and if your connection drops, it automatically resumes from where it left off instead of starting over. A chunk that fails to send gets retried automatically, up to three attempts, before it needs your attention at all. You don't need to babysit it, but you do need to keep the tab open. Close it and the browser loses the file it was reading from.

Stuck near 100% isn't the same as failed

A progress bar that stalls right at the end usually isn't broken, it's finishing. Once every byte has arrived, ZappFiles switches from uploading to assembling and saving the transfer, and that step can take a moment on a large file. Closing the tab during that step is the one thing that actually loses the transfer, so give it those last few seconds.

A separate error, the file can't be read from your device, means something different: the browser lost access to the file itself, not the connection. That happens when a file is still downloading from a cloud folder or got moved after you selected it. Resuming won't fix that one, you have to remove the file and add it again. The full breakdown of every error and fix is in the upload troubleshooting guide.

A checklist for your next big upload

• Wired connection and power plugged in for anything over a few gigabytes.
• Total size checked against your plan before you start, not after.
• Cloud synced files fully downloaded locally first.
• Tab open and device awake until you see the confirmation screen.
• Naming and folders sorted beforehand too, so the upload doesn't get held up while you reorganize on the fly. Our guide to organizing client project files covers a structure that holds up on any project.