Large File Uploads: Send up to 20 GB Without a Subscription

Most file-sharing services pretend you don't need big-file support until you're paying. WeTransfer caps the free tier at 2 GB. Dropbox Transfer caps free at 100 MB. Mega gives you 20 GB but expects an account and prefers their desktop client. Email attachments still die at 25 MB.

You're moving real things — design exports, raw video, builds, datasets — and you want it done in a browser without paperwork. Here's how big you can actually go on Zippd and why the upload is fast.

The actual limits

20 GB is roughly four hours of 4K video, a few hundred RAW photos, or an entire Xcode build folder. Enough headroom for any realistic single transfer.

How big files actually upload fast

Naïve uploaders send a file as one HTTP request and pray. A blip in the connection mid-upload kills the whole thing. A 1 GB file at the wrong moment becomes a 1 GB retry.

Zippd splits every upload into 8 MB chunks. Each chunk encrypts with AES-256 client-side, then PUTs directly to our S3-compatible storage. We upload up to 8 chunks in parallel. If a chunk fails, only that 8 MB retries. The connection can hiccup repeatedly and the file still arrives.

On a typical home fiber connection you'll see effective throughput approaching your raw upload speed. On a 1 Gbps line, a 20 GB file uploads in about three minutes. That's not theoretical — open DevTools and watch the parallel PUTs land.

Why the browser handles it (no desktop app required)

Older services tell you to install their desktop client for files over a few GB. The reason: browser uploads were historically slow because of single-stream limitations. That hasn't been true for years.

Modern browsers expose:

• The Streams API — encrypt chunks as they're read, no need to hold the whole file in memory.
• fetch() with multiple parallel requests — saturate the connection.
• Web Crypto API — hardware-accelerated AES-256 with no library overhead.
• CompressionStream — optional gzip before encryption, native and fast.

Stack those together and a 20 GB browser upload performs within 5–10% of a native desktop client. We didn't bother building a desktop app because the browser does the job.

Resumable, partial, and parallel

The chunked design gives you three free properties:

• Resumable. A failed chunk retries. The whole file doesn't restart.
• Partial. You see live progress as each chunk lands.
• Parallel. Up to 8 chunks in flight at once for registered users.

What about REALLY big files?

The 20 GB cap exists for sane reasons:

• S3-multipart has a 10,000-part hard limit. At our 8 MB chunk size, that's 80 GB ceiling regardless of policy.
• Browser RAM gets unhappy assembling decryption output above ~20 GB on consumer hardware.
• Above 20 GB, dedicated cloud-storage workflows (Mega, S3 direct, Backblaze) become more appropriate. Comparison with Mega here.

If you regularly need to ship 50+ GB files, talk to us — we'll discuss a higher-tier setup.

Tips for fast big-file uploads

• Use a wired connection where possible. Wi-Fi caps you well below your ISP plan.
• Close other upload-heavy tabs. Browser TCP fairness will throttle each tab.
• Don't compress already-compressed files first. A .zip of a .mp4 won't shrink and adds time. Zippd auto-skips gzip on incompressible types.
• For sensitive payloads, register an account. Higher concurrency = faster overall.

FAQ

What's the biggest file I can send free?

20 GB per file with a registered account. 2 GB anonymous. Free forever.

Do I need to install anything?

No. Any modern browser does the entire upload. No desktop app. No browser extension.

What happens if my upload fails halfway?

Failed chunks retry automatically. You won't lose progress on the successfully-uploaded chunks. If the whole tab crashes, we abort the multipart upload on the storage side so you're not charged for orphaned bytes.

Are large files less secure?

No. Encryption is per-chunk. A 20 GB file gets the same AES-256-GCM treatment as a 1 MB file, just more chunks.

How does the recipient download a 20 GB file?

Same way: their browser fetches each chunk, decrypts, decompresses, and assembles. They click one button. No special software.

Send a big one

Drop a file on the homepage — including the giant ones. Watch the parallel chunks fly.