Quick answer
Updated 15 November 2026. Product details and calculation inputs checked today. The timings below are illustrative calculations, not HeftySend speed tests.
You have finished the shoot, the editor wants the footage, and the progress bar barely moves. Before cancelling hours of work, separate two questions: is the upload slower than your connection should allow, or is the delivery simply too large for the deadline?
Is the upload slow, or has it stopped?
Note the progress and time, then check again a few minutes later. A percentage that changes slowly can still represent a lot of data on a large transfer. Record any error message separately. A stalled progress display is not enough to identify whether the problem is the browser, connection or service.
Keep an active HeftySend upload tab open and the device awake. Do not refresh or change networks just to see what happens: you may lose the current attempt. Use the HeftySend upload troubleshooting instructions if progress has stopped. This guide focuses on diagnosis and planning the delivery around the connection you actually have.

Which speed should you compare with the upload?
Use the upload result, not the larger download figure on an internet advert. Check the units too: 20 Mbps is 20 megabits per second, equivalent to 2.5 megabytes per second before overhead. A transfer showing around 2 MB per second is not necessarily far below that connection’s capacity.
Run a speed test before starting a large delivery, or after an attempt has stopped. Running one during an upload makes the two compete for capacity. A speed test uses its own servers and workload, so its result is a reference rather than a promise of the same speed to every service.
Cloudflare’s network quality guidance considers upload speed alongside latency, packet loss and other measurements. A strong download result alone does not tell you whether a long outgoing transfer will be stable.
How can you narrow down the bottleneck?
Change one thing at a time before your next attempt. Keep a short note of the file size, connection, browser and result so you can compare like with like.
| What you observe | Useful next check | What it can tell you |
|---|---|---|
| Upload tests are slow across devices | Pause other large uploads you control and retest | Whether shared outgoing traffic is using the connection |
| Performance changes with location | Test nearer the router or over Ethernet | Whether the local wireless link is contributing |
| Only one browser struggles | Try a current supported browser with the same small sample file | Whether the problem is specific to that browser setup |
| Speed tests are healthy but one service is consistently slow | Record the time, errors and results for support | The service, route or application may need investigation; the test alone does not prove which |
Ethernet can help isolate wireless interference, but it cannot make a 20 Mbps internet upload line deliver 200 Mbps. Cloudflare also recommends checking signal strength and contacting your internet provider when problems persist on a good local connection.
Google’s Chrome guidance recommends keeping the browser current and reducing unused tabs and extensions. Save work before restarting it. On a managed work computer, ask IT about required extensions or network restrictions rather than disabling company protections.
How can you estimate upload and download time?
Use the HeftySend file transfer time calculator twice: once with your upload speed and once with the recipient’s download speed. Add both results when the recipient starts collecting the complete delivery after your upload finishes.
- Enter the complete package size. Include every file being delivered. Select the correct unit rather than treating 10 MB and 10 GB as interchangeable.
- Select Upload and enter your outgoing speed. Use a realistic measured upload figure, not your internet plan’s headline download rate. The calculator accepts Mbps, MB/s and Gbps.
- Choose whether to add the tool’s 10% allowance. This multiplies the ideal duration by 1.10. It is a planning assumption, not a measured overhead for your transfer or a guarantee of finishing on time.
- Select Download and enter the recipient’s speed. Keep the same package size. Record this second duration separately.
- Add preparation, waiting and checking time. Exporting, packaging, the recipient being away and verifying the downloaded files do not disappear into the transfer estimate.
The calculation uses decimal units: 1 GB is 1,000,000,000 bytes and 1 Mbps is 1,000,000 bits per second. There are eight bits in a byte. The ideal duration in seconds is therefore size in GB × 8,000 ÷ speed in Mbps. Divide seconds by 60 for minutes or by 3,600 for hours. NIST’s SI prefix reference explains the decimal prefixes. If a file utility gives you bytes, divide that number by 1,000,000,000 before entering GB.
A measured file transfer rate in MB/s may already reflect protocol costs. Do not automatically add the same overhead again. Use a separate contingency for uncertainty, and increase it when the connection is unreliable. A short speed test is not proof that the same rate will hold for hours.
What time should you start to meet a delivery deadline?
Work backwards from the time the recipient needs the downloaded files, subtracting upload time, download time and a deliberate buffer. The worksheet below is reusable: replace the example inputs with your own figures.
| Worksheet item | Illustrative value |
|---|---|
| Complete package size | 10 GB |
| Sender’s upload speed | 20 Mbps |
| Recipient’s download speed | 100 Mbps |
| Extra time applied to each ideal transfer | 10% |
| Upload: 10 × 8,000 ÷ 20 × 1.10 | 4,400 seconds, or 1 hour 13 minutes 20 seconds |
| Download: 10 × 8,000 ÷ 100 × 1.10 | 880 seconds, or 14 minutes 40 seconds |
| Preparation, waiting and verification buffer | 30 minutes chosen for this example |
| Total time to reserve | 1 hour 58 minutes |
| Files needed locally by | 17:00 in the agreed time zone |
| Latest planned start | 15:02, preferably earlier |
This is arithmetic, not a HeftySend benchmark. The calculator displays rounded durations; the worksheet uses the exact seconds before adding them. Thirty minutes is an illustrative buffer, not a universal recommendation. If the recipient cannot start downloading immediately, add that wait too.
Copy this into your delivery notes: Package size ___ GB. Upload ___ Mbps. Download ___ Mbps. Extra transfer allowance ___%. Preparation and checking ___ minutes. Files needed locally by ___, time zone ___. Upload and download together ___ minutes. Planned start ___.
For your own worksheet, calculate each ideal duration, multiply it by 1 + allowance percentage ÷ 100, then add the two durations and your buffer using the same units. If that total does not fit before the deadline, reduce the agreed first delivery, arrange a faster suitable connection or agree a later deadline. Do not turn an optimistic estimate into a promise.
What does 300 GB at 20 Mbps mean for a client deadline?
Suppose you have 300 GB of footage and can sustain 20 Mbps upstream. Using decimal units, the ideal upload takes 120,000 seconds, or 33 hours and 20 minutes. If the editor then downloads the complete delivery at 100 Mbps, that adds at least 6 hours and 40 minutes. Sequential upload and download therefore need about 40 hours before overhead, interruptions or verification.
These are planning assumptions, not measured results. If everything is needed tomorrow morning, leaving that connection running overnight does not solve the arithmetic. Agree which files are genuinely urgent, find a faster permitted connection, or compare the total time to copy, transport and verify a drive. Our large footage delivery guide explains the broader capacity and cost choices.
What can you send first from a location with poor internet?
- Ask what enables the next task. The editor might need a small set of selected originals or an agreed viewing copy before the complete footage. Do not choose a reduced version without confirming its purpose.
- Prepare a separate urgent package. Label its contents and list what will follow. For illustration, 3 GB at 20 Mbps takes at least 20 minutes to upload, before overhead and download time.
- Finish that transfer before sharing it. Do not promise access to files that are still uploading. Check the completed link and tell the recipient exactly what it contains.
- Give the full delivery its own timetable. Preserve the complete originals and organise the remaining transfer from a suitable connection. Keep the device powered and allow time to check the recipient’s download.
A useful message is: “This first link contains the agreed selects. The full footage is a separate delivery. I will confirm its completion and collection deadline once the upload has finished.” For deciding which video version to include, see our guide to sending video without losing quality.
How do you deliver event selects before the full footage is ready?
Make the urgent selects a separate, complete delivery with its own contents note. The editor can work from that finished package while the remaining footage uploads separately. This does not mean the editor can download files from an unfinished transfer: HeftySend’s upload instructions say the shareable link is generated once all files in that transfer have uploaded.
For a same day event edit, agree the specific moments needed first, such as the opening, speaker highlights and closing shot. Confirm whether the editor needs selected camera originals, review exports or proxies. A small viewing copy may be enough to choose shots but unsuitable for the final edit. Our proxy delivery guide covers matching proxies to originals when that is the agreed workflow.
Use one delivery manifest to distinguish what is ready from what is still coming. The following is an illustrative planning example, not a real event or a tested transfer. Replace every count, size and deadline with the actual package details.
| Manifest field | Urgent selects | Full footage |
|---|---|---|
| Package name | Event selects v01 | Event full originals v01 |
| Contents | 12 selected camera clips, 3 GB total | Complete camera folders, 300 GB total |
| Relationship | Original filenames retained; clip list identifies each source folder | Includes the same 12 selects, so they are not 12 additional shots |
| Purpose | Agreed clips for the urgent edit | Complete footage for the later edit and handover |
| Availability | Add the working link only after this transfer completes | Pending until its separate transfer completes |
| Collection check | Editor confirms all 12 clips saved and usable | Editor checks the complete manifest and reports missing items |
| Expiry | Copy this transfer’s actual expiry and time zone | Record separately when its link is ready |
At a sustained 20 Mbps, the example 3 GB selects need at least 20 minutes to upload. A subsequent download at 100 Mbps needs at least four minutes. If uploading starts at 15:00, the earliest calculated local delivery is 15:24, before overhead, waiting or checking. Do not promise 15:24 as a completion time. The separate 300 GB upload still needs at least 33 hours and 20 minutes at that upload rate.
Those figures assume the urgent upload has the stated capacity available to itself. Two uploads sharing one connection compete for its capacity, so starting a second one does not preserve either estimate. Plan the selects first where possible. If the full upload is already moving, keep it open and reassess the deadline; do not cancel it blindly or assume the service offers a priority control. An independently available, permitted connection may help with the urgent package, but check its own upload speed and data allowance.
Event selects v01 is ready: [completed link]. It contains the 12 agreed camera clips listed in the manifest. Please confirm that all 12 are saved and usable for today’s edit. The full footage is a separate delivery and includes these clips. Its upload is still running; my next progress update is [time and time zone]. The selects link expires [actual expiry].
Send a progress update at the agreed time even if the full upload has not finished. State what is complete, what remains and the revised estimate. When the second link is ready, update the same manifest and ask for confirmation of the complete set. For other ways to organise a delivery, see one large transfer versus smaller batches.
Where does HeftySend fit into the delivery?
HeftySend gives you a completed download link, supported media previews and an easy recipient experience without requiring the recipient to create an account. Free transfers allow up to 100 GB with three days for collection, which suits the smaller urgent package in this example.

A complete 300 GB transfer exceeds the free allowance. Premium currently costs $9 USD per month and supports up to 1 TB per transfer with up to 365 days of availability using included storage. Paid custom download pages let you present the delivery with your own templates, colours and instructions. Check current HeftySend plans for the right capacity and collection period.
HeftySend does not charge for bandwidth usage. If you connect your own storage, your provider’s storage, request and delivery charges remain separate. Paying for more capacity does not guarantee a faster upload on the same internet line.
Can a delivery network fix a slow upload?
A content delivery network helps serve content to recipients. It does not remove the capacity limit between your device and the internet. Cloudflare’s short explainer gives background on delivery infrastructure; it is not a HeftySend benchmark or a promise about your outgoing connection.
Frequently asked questions
Will upgrading my transfer plan make uploads faster?
More capacity or longer retention can make a delivery possible, but neither increases your internet connection’s upload speed. Diagnose the limiting part before buying a plan for speed alone.
Should I ZIP the footage first?
A ZIP can keep files organised, but already compressed video may shrink very little. Allow time to create the archive and keep the originals. Do not assume packaging 300 GB will make it a small delivery.
Is a mobile hotspot a better option?
It might be, but check the upload result, stability, data allowance and permitted use before starting. A large transfer can use substantial mobile data, and performance can vary during the day.
Should I keep restarting a moving upload?
No. If progress is continuing, repeated restarts can waste completed work. Record the progress, keep the device awake and consult the service’s guidance if it stops or reports an error.
Does splitting the files reduce the total upload time?
Not inherently. The same total data still needs to cross the connection. Separate packages can help prioritise urgent files and organise delivery, but they do not guarantee faster transfer or resumability.
What should I send support if nothing helps?
Send the approximate time and time zone, file size, browser version, connection type and exact error. Explain what you tried. Avoid including passwords, private download links or client files unless support specifically needs them through an appropriate channel.
Make the next transfer easier to collect
Fix or plan around the connection first, then give your recipient a clearly labelled delivery and a realistic collection deadline. Start with a free HeftySend account for transfers up to 100 GB and choose more capacity when the complete project needs it.