Back to Blog
James Bennett• •6 min read

Why Is My File Upload So Slow? Checks Before You Retry

Diagnose slow uploads, plan a 300 GB footage handover and decide what to send first. Check connection limits before restarting or paying for a bigger plan.

Quick answer

A slow upload usually needs a connection check before another attempt. Compare your measured upload speed with the file size, check whether progress is still moving, and remove competing uploads. For 300 GB at a sustained 20 Mbps, uploading alone takes at least 33 hours and 20 minutes. A different transfer plan cannot remove that connection limit.

Facts checked 3 October 2026. 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.

HeftySend homepage with the file selection area
The HeftySend upload starting point. This genuine product screenshot illustrates where a transfer begins; it is not a speed test or an upload in progress.

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 observeUseful next checkWhat it can tell you
Upload tests are slow across devicesPause other large uploads you control and retestWhether shared outgoing traffic is using the connection
Performance changes with locationTest nearer the router or over EthernetWhether the local wireless link is contributing
Only one browser strugglesTry a current supported browser with the same small sample fileWhether the problem is specific to that browser setup
Speed tests are healthy but one service is consistently slowRecord the time, errors and results for supportThe 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.

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?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

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 20 GB with three days for collection, which suits the smaller urgent package in this example.

HeftySend product demonstration of document and media previews
Supported previews help recipients recognise the delivered files. The public product demonstration is not evidence of transfer speed.

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.

Watch Cloudflare’s CDN explainer on YouTube

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 20 GB and choose more capacity when the complete project needs it.