Why your transfer shows 0 write speed and what it actually means
A transfer stuck at 0 write speed usually means the data is moving from your source to your destination, but the system isn't recording the speed correctly — or the transfer has genuinely stalled and isn't moving at all. The difference matters because one is a display glitch and the other is a real problem you need to fix.
When you see 0 write speed on a cloud service or file transfer tool, check whether the progress bar is actually advancing. If the percentage or file count is creeping forward, the transfer is working and the speed readout is just broken. If nothing is moving — the percentage stays the same, the file count doesn't change — then the transfer has stopped and you need to intervene.
The most common causes are a stalled network connection, a full destination drive, a permissions problem on the receiving end, or a timeout in the transfer tool itself. Each one requires a different fix.
Key Takeaways
- A stuck transfer showing 0 write speed may still be working if the progress bar is advancing; check the percentage or file count before assuming failure.
- Network interruptions, full destination drives, and permission errors are the three most common reasons transfers stall completely.
- Restarting the transfer, checking your internet connection, and freeing up space on the destination are the first three steps to try.
- Most cloud services and file transfer tools can resume interrupted transfers instead of starting over, but you need to cancel and restart the job correctly.
Check your internet connection first
A transfer showing 0 write speed almost always points to a network problem. Your computer may have lost the connection to the destination server, or the connection is so weak that no data is actually moving.
Open a web browser and load a website you know works — your email, a news site, anything that requires a live connection. If the page loads normally, your internet is working. If it's slow or doesn't load, restart your router by unplugging it for 30 seconds, then plugging it back in. Wait two minutes for it to fully restart before trying the transfer again.
If you're using a wireless connection, move closer to your router or switch to a wired connection if possible. Wireless connections drop packets and lose signal, which can cause transfers to stall. A wired Ethernet connection is more stable for large file transfers.
Free up space on your destination drive
If your destination drive — the place where files are being written — is full or nearly full, the transfer will stop and show 0 write speed because there's nowhere for the data to go. The system can't write what it can't fit.
Check how much free space you have on the destination. On Windows, right-click the drive in File Explorer and select Properties. On Mac, click the Apple menu, select About This Mac, then Storage. If you have less than 10% of the drive's total capacity free, delete files you don't need or move them to another drive.
For cloud services like Google Drive or OneDrive, check your account storage in the settings. If you're at or near your limit, you may need to delete old files or upgrade your storage plan before the transfer can continue.
Check permissions on the destination folder
If you don't have write permission on the folder where files are being transferred, the system will try to write but fail silently, showing 0 speed while nothing actually moves. This is common when transferring to a shared network drive, a cloud folder with restricted access, or an external drive that's set to read-only.
Right-click the destination folder and select Properties (Windows) or Get Info (Mac). Look for a Permissions or Sharing section. Make sure your user account has write access — not just read access. If the folder is on a network drive or cloud service, check the sharing settings to confirm you're listed as an editor or owner, not just a viewer.
If the destination is an external drive, check whether it's set to read-only. On Windows, right-click the drive and select Properties, then uncheck "Read-only" if it's checked. On Mac, select the drive, press Command+I, and check the Sharing & Permissions section at the bottom.
Cancel and restart the transfer correctly
If the transfer has genuinely stalled, canceling and restarting is usually faster than waiting. Most cloud services and file transfer tools can resume from where they stopped instead of starting completely over.
Cancel the current transfer by clicking the Stop or Cancel button in your transfer tool. Wait 10 seconds for it to fully stop. Then restart the transfer. The tool should recognize which files were already sent and skip them, picking up where it left off.
If the tool doesn't resume automatically, you may need to manually remove the files that were already transferred from your source list before starting again. Check your destination folder to see which files arrived, then delete those from your transfer queue.
Increase timeout settings if transfers keep stalling
Some transfer tools have a timeout setting — a limit on how long the tool will wait for a response from the destination before giving up. If your network is slow or your destination server is sluggish, the timeout may be too short, causing the transfer to fail and show 0 speed.
In your transfer tool's settings or preferences, look for options labeled Timeout, Connection Timeout, or Transfer Timeout. If you find them, increase the value — try doubling it. This gives the transfer more time to complete before the tool assumes something went wrong.
If you're using a cloud service's built-in transfer tool and can't find timeout settings, try using a third-party tool instead. Tools like Rclone or Cyberduck give you more control over how long transfers wait and how they handle network interruptions.
Try a different transfer method
If restarting, checking your connection, and freeing up space don't work, the problem may be with the transfer tool itself. Try a different method to move the same files.
If you were using your cloud service's web interface, try downloading the desktop app instead — it often handles transfers more reliably. If you were using the desktop app, try the web interface. If you're transferring between cloud services, try downloading to your computer first, then uploading to the destination, even though it takes longer.
For very large transfers that keep failing, command-line tools like Rclone or rsync give you more detailed error messages and better control over retries. These tools are more technical but are built specifically to handle transfers that fail partway through.
Frequently Asked Questions
Does 0 write speed always mean the transfer failed?
No. Check whether the progress bar or file count is still advancing. If it is, the transfer is working and the speed display is just broken. If nothing is moving after five minutes, the transfer has stalled and needs to be restarted.
Will restarting the transfer make me upload everything again?
Most cloud services and transfer tools skip files that were already sent successfully. When you restart, the tool checks the destination and only transfers files that are missing or incomplete. This is much faster than starting over.
What if my destination drive is full but I can't delete anything?
Move files to an external drive or a different location temporarily to free up space. You only need enough free space for the transfer to complete — you can move files back afterward. Alternatively, transfer to a different destination that has more space available.
Can I transfer while using my internet for other things?
Yes, but it will be slower. Large file transfers use a lot of bandwidth. If you're also streaming video, downloading, or video calling, the transfer may stall because there's not enough bandwidth for everything. Close other applications and pause streaming services during large transfers.
Why does my transfer work sometimes but not others?
Network conditions change throughout the day. Transfers are more likely to fail during peak hours when your internet service provider's network is congested. Try transferring during off-peak hours — early morning or late evening — when there's less traffic on the network.