Uploading Large Files and Resumable Uploads

Uploading a 3 GB video over a shaky connection is exactly where ordinary file uploads fail. StretchDrive is built for this: large files upload in chunks, can resume after an interruption, and are checksum-verified end to end. This guide explains how it works and how to get reliable results.

How large uploads work

When you upload a big file, StretchDrive doesn't send it in one shot. It:

1. Starts an upload session that records the file name, destination, and total size.
2. Sends the file in chunks, tracking exactly how many bytes have been received.
3. Verifies each chunk with a checksum as it arrives.
4. Completes the upload, then verifies the whole file's checksum before the file becomes available.

Because the session tracks a byte cursor, if the transfer is interrupted it knows precisely where to pick back up.

Resuming after an interruption

If your connection drops or you close the tab mid-upload, you don't have to start over:

1. Return to Drive and re-initiate the upload of the same file.
2. StretchDrive resumes from the last confirmed byte rather than re-sending everything already received.
3. Re-sending a chunk that already arrived is harmless — the system recognizes it and won't duplicate data.

Upload sessions remain valid for 24 hours, so you have a generous window to finish an interrupted transfer.

Integrity guarantees

Every chunk carries a checksum, and the completed file is checked against its expected checksum before it's stored. If anything is corrupted in transit, the upload is rejected rather than silently saving a damaged file. This means a file that lands in Drive is guaranteed to be an exact copy of what left your computer.

Size limits and quota

• A single file can be up to 5 GB.
• The upload is checked against your organization's storage quota before it starts, so you're told up front if it won't fit rather than after a long transfer.

If a large upload would exceed your quota, free space (empty Trash) or ask an owner about upgrading the plan, then retry.

A realistic example

You need to upload a 2.5 GB product demo video into the Marketing → Video folder. You open that folder, drag the file in, and the upload begins chunk by chunk with a progress indicator. Halfway through, your Wi-Fi drops. Instead of losing 1.2 GB of progress, you reconnect and start the same upload again — StretchDrive resumes right where it stopped and finishes the remaining portion. When it completes, the whole-file checksum is verified, and the video appears in the folder, guaranteed intact.

Tips

• Use a wired or stable connection for very large files when you can — but rest assured resume has your back if it drops.
• Don't delete the local file until the upload fully completes and appears in Drive.
• Check the Storage meter before a big upload so you know it will fit.
• If an upload stalls, simply retry it — resume avoids re-sending what already succeeded.
• Finish interrupted uploads within 24 hours while the session is still valid.

Troubleshooting

"Upload exceeds the maximum allowed size." The file is larger than the 5 GB single-file limit. Split it or compress it before uploading.

"Drive quota would be exceeded." The upload won't fit in your remaining storage. Empty Trash to reclaim space or upgrade the plan, then retry.

My resumed upload says it's out of order. Chunks must continue from where the session left off. Re-open the upload so the client resumes from the correct byte position rather than sending from the wrong offset.

Upload failed with a checksum error. The data was corrupted in transit. Retry the upload; the integrity check exists precisely to stop damaged files from being stored.

I abandoned an upload yesterday — can I still finish it? Sessions last 24 hours. If it's older than that, start the upload fresh.