Frequently asked questions

Everything worth knowing before you upload.

The basics

How big a file can I send?

Up to 10 GB per transfer, spread across as many as 100 files. There is no daily cap for normal use, though we do rate-limit a single connection that starts an unusual number of transfers in one hour.

Do I need an account?

No. There is no signup, no email verification, and no login screen. Drop a file, get a link, share it. That is the whole product.

Is it free?

Yes, completely. There is no paid tier, no ads, and no upsell.

How long are files kept?

15 days by default. You can shorten that to 1, 3 or 7 days in the Options panel before uploading. When a transfer expires, a background job deletes the files from disk and the link stops working — there is no archive and no recovery.

My upload stopped halfway. Do I have to start again?

No. Files are uploaded in 8 MB chunks and the server tracks exactly how much it has received. If your connection drops, the browser retries from the last confirmed byte. Keep the tab open and it will recover on its own.

Privacy and security

Who can access my files?

Anyone holding the link. The address contains 12 characters from a 57-character alphabet — around 70 bits of randomness — so it cannot be guessed or discovered by crawling. Download pages are also excluded from search engines and send no referrer. Still, treat the link like a password: it is the credential.

What does the password option actually do?

It hides everything until the password is entered — filenames, sizes, and your note are not returned by the server to anyone who hasn't unlocked the transfer. Passwords are salted and hashed with scrypt; the plain text is never stored, and we cannot recover it for you.

Are the files encrypted?

Transfers are encrypted in transit over HTTPS, and files are stored outside the web root with generated names that reveal nothing about their contents. They are not end-to-end encrypted — the server holds readable bytes, which is what makes zip-on-the-fly, previews, and resumable uploads possible. For genuinely sensitive material, encrypt it yourself before uploading and share the passphrase separately.

What do you log?

A keyed hash of the uploader's IP address (not the address itself), the browser's user-agent string, timestamps, and download counts. That is enough to handle abuse reports and stop floods, and not enough to build a profile. There are no analytics scripts, no ad trackers, and no third-party requests of any kind on this site.

Can I delete a transfer before it expires?

Yes, from the tab you uploaded in — there is a "Delete now" button on the success screen. The key that authorises deletion is held in that page and never saved, so once you close the tab the transfer can only be removed by its expiry, its download limit, or an abuse report.

Limits and rules

Which file types are blocked?

Directly executable and scriptable formats: .exe .bat .cmd .com .scr .msi .jar .vbs .js .ps1 .apk .dll .deb .rpm and similar. This keeps the domain off malware blocklists so everyone else's links keep working. Wrap them in a .zip and they upload without issue.

What is the download limit option?

You can cap how many times a transfer is downloaded. Set it to 1 for a genuine one-time link — once the cap is reached, the transfer deletes itself on the next cleanup sweep and the link stops working immediately.

Can recipients download everything at once?

Yes. If a transfer has more than one file, the download page offers a ZIP of the whole set. The archive is streamed as it is built, so large transfers start downloading immediately rather than making you wait for it to be assembled.

How do I report abuse?

Every download page has a "Report this transfer" button. Reports go straight to a moderation queue, and confirmed cases have their files erased. You can also email us directly — the address is on the terms page.

Something is broken. What now?

Check the service status first. If the service is up but your upload keeps failing, try a smaller batch — some corporate networks and mobile carriers interrupt long-running uploads in a way retries can't always recover from.

Send a file