What's the file size limit?
2 GB per file. The cap is enforced both client-side (so you see an error before the upload even starts) and server-side (so the presigned URL refuses oversized uploads). If your file is bigger, compress it — for video, try our video compressor tool; for everything else, split it into 2 GB chunks or use real cloud storage.
How long do files last?
Exactly 48 hours from when the upload finishes. After that the file is deleted from storage and the share link returns a "no longer available" page. There are no extensions, no "renew" button — these links are deliberately not renewable, by design. If you need permanence, this isn't the tool.
Is the link private?
Your choice. By default anyone with the link can download — the slug is short and random, so it's effectively unguessable, but treat the link like a password. If you need real gating, switch the share to "specific people" and list their emails: only those people, signed in with that email, can open it. That's the same restricted-sharing model Clipy recordings use.
Do I need an account?
Yes — a free one, sign-in with Google takes one click. Requiring an owner is what makes restricted sharing possible (someone has to control the access list) and keeps the tool from being abused as an anonymous distribution channel. Downloading a public share needs no account; only restricted shares ask the RECIPIENT to sign in, so we know their email matches the access list.
Can I delete my file before the 48 hours are up?
Not yet via the UI. If you uploaded something by mistake, email us and we'll delete it manually — but the simpler answer is: don't share the link with anyone and it'll expire on its own in 48 hours. The slug is random enough that nobody is going to stumble onto an unshared link.
What happens if my upload fails halfway?
Nothing visible to the recipient. The share link is only minted after the upload finishes successfully, so a half-uploaded file never produces a usable URL. The partial bytes get cleaned up by Backblaze's multipart-upload TTL. Just retry the upload.
Is this safer than just emailing the file?
Different trade-offs. Email attachments live in someone's inbox forever, get backed up to whatever cloud their employer uses, and are capped at 25 MB. This tool is the opposite: zero retention past 48 hours, no inbox copy, 2 GB cap. For sensitive files use neither — use real end-to-end-encrypted file transfer. This tool doesn't scan file contents or claim to.
Why 2 GB and 48 hours and not more generous?
Storage and bandwidth cost real money, and "free file host" failure modes are predictable: piracy mirrors, malware distribution, backup parasites. These limits are the smallest pair that still cover the actual use case (one-off file handoffs) without turning the tool into something we have to police. If your use case needs more, real cloud storage is the right tool, not this.
