Measure the right direction
A cloud backup sends data from your device to a remote destination, so enter upload speed in the calculator. A plan’s prominent download figure can have a separate, lower upload counterpart. Check the details and a representative speed measurement rather than copying its largest number.
Confirm what the application means by remaining data. It might be scanning files, processing changes or preparing a transfer before sending them. A changing estimate does not necessarily mean the connection stopped. Read its status message and documentation before changing several settings at once.
Calculate the uninterrupted lower bound
For decimal gigabytes, ideal seconds equal GB × 8,000 ÷ upload Mbps. Sending 200 GB at a constant 20 Mbps takes 80,000 seconds, about 22 hours 13 minutes. At 10 Mbps, that ideal time doubles to roughly 44 hours 27 minutes.
With an illustrative 85% efficiency assumption, the 20 Mbps example needs about 26 hours 9 minutes of active transfer time. This does not include every service-specific preparation step. Large numbers of tiny files can behave differently from a few large files, even when their combined size is similar.
Turn active hours into calendar time
The computer may only send while it is awake, connected and permitted to run the backup. Backblaze’s documentation notes that initial backups can take substantial time and recommends keeping the computer available during that stage. Other products have their own schedules and power-management behaviour.
If 26 active hours are required and eight hours are available nightly, allow four nights. Interruptions or slower periods can extend that plan. Do not assume closing the laptop lid leaves the backup running. Choose a schedule compatible with how the device is used, and check the completion status afterwards.
Estimate the work after the first upload
After the starting copy exists, many backup products send new or changed data rather than every original file again. Your rate of change then matters more. Adding 2 GB daily is different from generating 100 GB of new video each day. Check the app’s actual handling of large files that change repeatedly.
At 20 Mbps, 2 GB takes about 13 minutes 20 seconds ideally, or 15 minutes 41 seconds with the same 85% assumption. That is much easier to fit into a routine than the first 200 GB. A simple daily data estimate helps identify when the backup could begin falling behind.
Choose the starting set deliberately
Prioritise files you could not comfortably replace: recent projects, documents and personal media. Check the folders and attached drives the service includes. A long upload is not helpful if it concentrates on replaceable material while omitting the current work you need to protect.
If the service allows staged selections, record what is included and what remains. Keep another current copy while the remote backup is incomplete. Watch for a completed status rather than only a declining file count. Do not delete local originals to make the upload appear simpler or faster.
Plan the return journey
Restore a small folder to a separate location, open the files and note the required account details or encryption password. Review how the provider makes large restores available and how long retained versions last. A quick document recovery and a full photo-library recovery may have different practical requirements.
A sync folder can propagate deletions or unwanted changes, so check its recovery history before treating it as independent protection. Once a backup and restore rehearsal succeed, keep checking excluded folders, completion dates and changes in daily data production. A reliable routine matters more than an optimistic initial progress bar.
Sources & further reading
Backblaze — File backup and restoration time frames ↗Backblaze — Backup schedule ↗CRTC — Internet performance and reliability ↗This guide is based on the sources linked above, with original explanations and examples. Software interfaces and service features can change. A documentation-based guide is not a hands-on product review. Read our editorial policy or report a correction.