Why Your File Transfer Gets Stuck at 99% (and How to Fix It)

September 13, 2026

It's one of the most universally frustrating moments in computing: a progress bar climbs cleanly to 99%, and then just sits there. Here's what's actually happening, and what genuinely helps.

It's rarely actually 99% done

A progress bar for a chunked transfer usually reflects how much data has been sent, not how much has been fully received and confirmed. The last stretch, the final acknowledgment, assembling the last pieces, cleanly closing out the connection, can take real, disproportionate time compared to the steady climb that got you to 99% in the first place.

A dropped connection the UI hasn't caught up to

The more common culprit is a connection that quietly dropped without the interface noticing yet, a Wi-Fi hiccup, a laptop going to sleep, a phone screen locking, or a browser throttling a tab that's been sitting in the background. The data channel has effectively gone quiet, but the progress bar hasn't been told that yet.

Practical fixes

Keep both devices' tabs in the foreground and screens awake for the duration of a large transfer, background throttling is a common, invisible cause of exactly this stall. If it does stick, retrying is usually faster than waiting it out. And check that both sides still show as connected before assuming the transfer itself is the problem, sometimes the pairing dropped first.

Why a folder can actually help here

Sending a large batch of files as an actual folder, rather than one giant archive, has a real practical advantage: each file gets its own progress and its own retry, so one stalled file doesn't take the rest of the batch down with it; you're not stuck re-sending everything from zero.

If it keeps happening

A stall that repeats on the same network points to that network, not the transfer tool, try switching from Wi-Fi to a mobile hotspot (or the reverse) to see if the pattern follows the connection.

Why this happens more on mobile than desktop

Mobile browsers are considerably more aggressive about suspending background activity than desktop ones, as a battery-saving measure, switching apps, letting the screen lock, or even just the operating system deciding to reclaim resources can pause a browser tab's network activity mid-transfer with little warning. That's part of why a large transfer between two phones, or a phone and a laptop, tends to stall more often than one between two laptops left open and plugged in; it isn't that the transfer method is less reliable on mobile, it's that the platform is more aggressive about managing background tabs by design.

What a stalled progress bar doesn't necessarily mean

A stall at 99% doesn't automatically mean the whole transfer needs to restart from zero. Depending on how far the connection actually got before dropping, a retry can sometimes pick back up close to where it left off rather than truly starting over, particularly for a folder, where most individual files may have already completed successfully before the stall hit. It's worth checking what actually finished before assuming the entire batch needs to be resent from scratch.

The single most common fix, restated plainly

If there's one thing worth doing before troubleshooting anything else: keep both devices awake, unlocked, and with the transfer tab in the foreground until it's actually done. This single habit resolves the majority of stalls before they ever happen, because it removes the background-throttling trigger that causes most of them in the first place.