- Free allowance
- No account and no published total quota — storage is per-object and unbounded in count.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-object-cap256 GB per single file
- Evidence
- documented10 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21
| Free tier | No account and no published total quota — storage is per-object and unbounded in count. 'Up to 256 GB per single file. No limit on batch uploads as long as each file is under 256 GB.' unit GB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) 256 GB per single file source
- retention-clamped Uploaded files are kept for at least 365 days; files not downloaded for more than 365 days are automatically deleted source
per-object-cap 256 GB. Retention: 'Uploaded files are kept for at least 365 days. Files that have not been downloaded for more than 365 days will be automatically deleted' — a sliding window, not a hard expiry, so a monthly GET sweep keeps everything alive indefinitely. No auth, no rate limit observed: 4 concurrent ranged GETs all returned 200 in 1.7-3.3 s. |
|---|
| Identity | anonymous No registration is required and the vendor states that no email, phone or personal information is needed; uploads are handled anonymously. |
|---|
| Egress | Unmetered. 'No speed limits. Speeds depend solely on your network bandwidth. We don't impose any artificial throttling.' Downloads served from Cloudflare with Cache-Control: public, max-age=3600. |
|---|
| Per-object cap | 256 GB per single file (256000000000 bytes) |
|---|
| Retention | Uploaded files are kept for at least 365 days. Files that have not been downloaded for more than 365 days will be automatically deleted. (365 days) |
|---|
| Interface | rest, rclone rest |
|---|
| Tooling | Undocumented but functional chunked HTTP API, reverse-engineered from the site's own uploader JS: POST https://u1.bigfile.net/v1/upload with header Content-Range: start-end, header Hash: <sha256 of whole file encoded base62>, raw body = the chunk; response {"status":true,"uri":"/d/<base62hash>"}. Read path: GET https://www.bigfile.net/d/<base62hash> (direct octet-stream), plus GET /d/<hash>/list.json for multi-file shares. Uploader parallelises across u1..uN.bigfile.net. No rclone backend. |
|---|
| Composes with | Account-less, so unlimited uploads per IP x 256 GB per object. Chain = N objects x 256 GB with 365-day sliding retention. |
|---|
| Reliability | Genuinely good for a no-account host: upload and read both verified by SHA-256, and the site advertises a 'zero-database architecture' meaning no inventory to lose. The risk is the opposite of the usual one — there is no account, so nobody can enumerate or restore your corpus if you lose the hashes. |
|---|
| Evidence note | documented The page states the number in the record; the claim is documented, not measured. |
|---|
| Parsed numbers | - has-free-tier 1
- per-object-cap 256 GB
|
|---|