Video upload speed and time
Upload time is file size divided by upload speed, and upload speed is the number nobody checks. Here are the sums, a reference table and the few changes that really help.
Upload time is the file size in megabits divided by the upload speed in megabits per second. A 2 GB file at 10 Mbps upstream takes about 27 minutes with the connection to itself. To shorten it, use a wired connection, pause other traffic and export a smaller file. Nothing in the browser makes the pipe wider.
Speed tests report two numbers, and everyone reads the first. Download is what the connection was sold on and what most use depends on. Upload is the second, smaller number. For anyone sending video, it is the only one that matters. On many home connections it is a tenth of the download figure, and on some it is less. Once you know it, upload time stops being a mystery and becomes a simple division.
This guide gives the arithmetic and a reference table for common file sizes and speeds. It explains why real uploads run slower than the table. It lists the few changes that actually cut the wait. It ends with what to do when the connection is simply too slow for the file. The uploading video hub links the other upload guides, from export settings to failed transfers.
The arithmetic
File sizes are given in bytes: megabytes and gigabytes. Connection speeds are given in bits per second, usually megabits per second (Mbps). There are 8 bits in a byte. So a 2 GB file is 2,000 megabytes, or 16,000 megabits. On a 10 Mbps upstream connection it takes 16,000 divided by 10. That is 1,600 seconds, or just under 27 minutes. That figure assumes the connection is all yours and the server accepts data as fast as you can send it. Real uploads carry protocol overhead and share the connection with everything else in the building. They also pass through a network path that varies. So treat the result as a floor, not a promise. A reasonable rule of thumb is to add a quarter to a third for a real-world estimate.
Upload time at common upstream speeds
Ideal figures: size times 8, divided by speed. Add 25 to 35 percent for a realistic estimate.
| Upload speed | 500 MB | 1 GB | 2 GB | 4 GB |
|---|---|---|---|---|
| 2 Mbps | 33 min | 67 min | 2 h 13 min | 4 h 27 min |
| 5 Mbps | 13 min | 27 min | 53 min | 1 h 47 min |
| 10 Mbps | 7 min | 13 min | 27 min | 53 min |
| 20 Mbps | 3 min | 7 min | 13 min | 27 min |
| 50 Mbps | 1 min | 3 min | 5 min | 11 min |
| 100 Mbps | 40 s | 80 s | 3 min | 5 min |
| 500 Mbps | 8 s | 16 s | 32 s | 64 s |
Why uploads are so much slower than downloads
Most residential and small-office connections are asymmetric by design. Cable and older copper technologies give far more capacity to the download direction, because that is where most traffic flows. A connection sold as 100 Mbps may provide 10 or 20 Mbps upstream. Fibre connections are often symmetric. That is why an upload that takes half an hour in one place can take three minutes in another with the same advertised download speed. Mobile connections vary enormously and change from minute to minute. None of this is under your control, but knowing which kind of connection you have explains the number the speed test gives you. Video hosting costs uses the same bits-and-bytes conversion on the delivery side, where it determines what viewers consume.
What eats into the ideal figure
Several things sit between the speed test's number and the upload's. Wi-Fi rarely delivers its advertised rate. Its real throughput drops with distance, walls and interference, and a laptop two rooms from the router may see a third of the wired figure. Other devices and apps share the upstream. Cloud photo backups, sync clients, video calls and a second person's upload all take a share of the scarce direction. A VPN adds encryption overhead and routes traffic through a gateway that may be far away or busy. And the upload itself has overhead. Each chunk in a resumable upload is an HTTP request with headers and replies, a small but real cost. Why video uploads fail deals with the point where slow becomes stopped.
What helps and what does not
Changes that reduce upload time, against changes people try that make no difference.
Helps
- Plugging into Ethernet instead of Wi-Fi
- Pausing backups, sync clients and other uploads
- Disconnecting a VPN that is not required
- Exporting a smaller file at a sensible bitrate
- Uploading from a location with symmetric or faster upstream
- Uploading at a time when the connection is otherwise idle
Does not help
- Changing browsers
- Opening the upload in several tabs at once
- Renaming or zipping the file
- Upgrading a plan advertised by download speed without checking upstream
- Restarting an upload that is progressing, however slowly
- Reducing resolution when reducing bitrate would suffice
The one lever you fully control: file size
Bandwidth is largely fixed by where you are. File size is not. A 1080p export at 12 Mbps and the same export at 8 Mbps look nearly identical after the host transcodes them. But the second uploads in two thirds of the time. If a file is large because it was exported as a master, a delivery-quality re-export at a moderate bitrate can cut the upload several times over. The free video compressor can do the re-export for you: pick a target size in megabytes or a compression strength. Do not go too far, though. A heavily compressed source degrades every rendition made from it. Prepare video for upload gives the settings, and the bitrate guide explains where the visible floor is. Removing resolution is the last resort. The host produces every lower rung itself, so sending 720p instead of 1080p gains you nothing but a worse top rendition.
Estimating before you start
- Run a speed test and note the upload figure in Mbps.
- Read the file's size in MB from the file manager.
- Multiply the size by 8 and divide by the upload speed; the result is seconds.
- Add a third for a realistic figure, and more on Wi-Fi.
- If the result is longer than the computer will stay awake or the connection will stay up, set the machine not to sleep and plug it in. Or accept that the upload will resume across interruptions.
When the connection is simply too slow
Some connections cannot reasonably move a 4 GB file. At 2 Mbps upstream it is a four-and-a-half-hour job with nothing else running. You have three options. First, reduce the file with a delivery-quality export, or split a long recording at a natural break. Second, move the upload to a better connection: an office, a library, a friend's fibre or a phone on a strong mobile network. Third, run it overnight with sleep disabled and let the resumable uploader ride through any breaks. You can upload in the background while working. But the upload will take everything the upstream has, and video calls in particular will suffer. What does not work is hoping the browser can somehow send bits faster than the line carries them.
Frequently asked questions
Why does the estimated time keep changing during upload?
The uploader measures current throughput and projects from it. Throughput varies as other traffic starts and stops, Wi-Fi conditions change and the network path shifts. The estimate is a moving average, not a promise. Over a long upload it tends to settle, and brief jumps are normal.
Is it faster to upload several videos at once?
No. They share the same upstream bandwidth, so the total time is the same or slightly worse due to overhead. Uploading them one after another gets the first video processed and available sooner, which is usually what you want. Processing starts as soon as each file lands. The help page on encoding times after upload says how long that part takes. Parallel uploads only help when the bottleneck is somewhere other than your connection.
Does a faster computer upload faster?
Not meaningfully. Reading the file from disk and sending chunks is light work for any modern machine; the bottleneck is the network. An old laptop on Ethernet will out-upload a new one on a weak Wi-Fi signal every time. Free memory and a wired connection matter far more than processor speed.
What upload speed do I need for a 4 GB file in under an hour?
A little over 9 Mbps in ideal conditions: 4,000 MB times 8 is 32,000 megabits, divided by 3,600 seconds. Allowing for real-world overhead, a sustained 12 Mbps upstream is a safer figure. Many cable connections fall below that, which is why a 4 GB upload from home is often a job to start and leave.
Sources
- tus resumable upload protocol — Why an interrupted slow upload does not restart.
- MDN: Blob.slice() — The chunking mechanism whose overhead is discussed above.
- FFmpeg documentation — Re-encoding to reduce file size before upload.
- YouTube Help: Recommended upload encoding settings — A bitrate reference for delivery-quality exports.
Related guides
How to upload 2 GB video files
Large uploads fail for boring reasons: a sleeping laptop, a flaky Wi-Fi hop, a file that was never going to be accepted. Here is how to get a big file up in one go, and what to do when it stops.
Prepare video for upload
The right export is smaller, uploads faster, is accepted without complaint and transcodes cleanly. It is not the highest possible quality and it is not the smallest file. Here is the middle.
Why video uploads fail
An upload that stops, stalls, restarts or is rejected is almost always one of a short list of causes. Learn to tell them apart from what the browser shows you, and fix the right one.
Video hosting costs: storage and bandwidth
Video costs money in two places: keeping it and sending it. Both can be estimated from numbers you already have. This guide shows the arithmetic and where the surprises hide.