Home / Storage
ZeroFS
zerofs.linkAnonymous dumpstorage/zerofsJSONcomparereport an errorprovider JSON
- Free allowance
- Unlimited storage for active files; no file size limit.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymous?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Unlimited storage for active files; no file size limit. unit unlimited; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | anonymous (inferred, not read) not published |
|---|
| Egress | No stated bandwidth cap; no speed limit claimed on the uploader. |
|---|
| Per-object cap | not stated |
|---|
| Retention | Files inactive for 15 days are deleted — the shortest retention of any live host (15 days) |
|---|
| Interface | s3, rest, webdav, rclone rest |
|---|
| Tooling | Anonymous browser uploader plus a region selector; no published API. Optional account ID (no email) to track files. No rclone/webdav/S3 backend found. |
|---|
| Composes with | Account-less uploads, so unlimited identities; the binding constraint is the 15-day inactivity deletion, which needs a re-access cron per file. At unlimited file size this is >= 500 GB per 'unit' trivially. |
|---|
| Reliability | Very new, looks like a Buzzheavier-style clone (same 'we only act on local court orders' posture, same lost-ID-never-recovered model). 15-day inactivity window makes it unusable for cold archive without active touching; untested for sustained throughput. |
|---|
| Parsed numbers | |
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-21 | zerofs.link/faq/ | 'File size limit? None.' / 'How much storage? Unlimited for active files.' / 'Are files deleted? Yes. If a file is inactive for 15 days, it's gone.' |
| 2026-10-21 | zerofs.link/ | probe: GET -> 200 |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read