file.io
file.io · 3 records in Storage · JSON
Records 3
- fails: quotaFile.io
Storagefree tieridentity institution?card?limit per-ip-shapingevidence reportedstale on 2026-11-05disagrees
- fails: quotafile.io (now limewire)
Storageidentity email?card?evidence reportedstale on 2026-11-05disagrees
- deadfile.io (documented api path)
Storageidentity email?card?evidence reportedchecked 2026-10-21disagrees
File.io
StorageSibling records disagree:
- verdict:
storage/file-iosays fails-quota, storage/file-io-2 says dead - identity_kind:
storage/file-iosays institution, storage/file-io-2 says email - identity_kind:
storage/file-iosays institution, storage/file-io-3 says email
- Free allowance
- No account; 4 GB per transfer ('file transfers are limited to a total of 4 GB')
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-ip-shapingtransfer ('file transfers are limited to a total of 4 GB') 4 GB/transfer
- 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 | no account; 4 GB per transfer ('file transfers are limited to a total of 4 GB') unit GB; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
4 GB/transfer; default 14-day expiry, override with ?expires=N[day|w|M|y]; file is DELETED after the first download ('after it is downloaded, the file is completely deleted'). |
| Identity | institution (inferred, not read) not published |
| Egress | unmetered direct link, but files self-destruct on first download |
| Per-object cap | not stated |
| Retention | 4 GB/transfer; default 14-day expiry, override with ?expires=N[day|w|M|y]; file is DELETED after the first download ('after it is downloaded, the file is completely deleted'). (14 days) |
| Interface | rest rest |
| Tooling | documented REST: curl -F 'file=@x' https://file.io/?expires=1w -> {"success":true,"link":...,"expiry":"7 days"} |
| Composes with | none — one-download-then-delete semantics make it anti-storage by design. |
| Reliability | Docs still describe a working API, but both the apex and www return 301/405 today. The 405 comes from an object-store front end, so the API has been re-plumbed and the documented POST is stale. Would need browser/session cookies to find the new path. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.file.io/about | 'file transfers are limited to a total of 4 GB', expires syntax, sample JSON responses |
| 2026-10-21 | file.io/ | probe: POST -> 301; POST https://www.file.io/ -> 405 MethodNotAllowed (ResourceType: OBJECT) |
More fields 2
| dead end | {"failure_class": "quota","why": "no account; 4 GB per transfer ('file transfers are limited to a total of 4 GB')","retry_when": null,"first_recorded": "2026-10-21"} |
|---|---|
| probe reported | POST https://file.io/ -> 301 to https://www.file.io/; POST https://www.file.io/ -> 405 MethodNotAllowed from an S3-style backend ('ResourceType: OBJECT'). The documented endpoint no longer accepts uploads from a user. Upload path FAILED. |
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
file.io (now limewire)
StorageSibling records disagree:
- verdict:
storage/file-io-2says dead, storage/file-io-3 says fails-quota - identity_kind:
storage/file-iosays institution, storage/file-io-3 says email
- Free allowance
- File.io redirects into LimeWire.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | file.io redirects into LimeWire. Free plan is 40 GB storage with a 4 GB upload cap and files expire after 3 days; 20 downloads per file per day. Retention makes it unusable as storage, and… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.file.io/plans | the text of Free tier, above |
| 2026-10-21 | limewire.com/pricing | cited as the basis of the rejection: file.io redirects into LimeWire. Free plan is 40 GB storage with a 4 GB upload cap and files expire after 3 days; 20 downloads per file per day. Retention makes it unusable as storage, and t |
| 2026-10-21 | www.file.io/developers | cited as the basis of the rejection: file.io redirects into LimeWire. Free plan is 40 GB storage with a 4 GB upload cap and files expire after 3 days; 20 downloads per file per day. Retention makes it unusable as storage, and t |
More fields 1
| dead end | {"failure_class": "retention","why": "file.io redirects into LimeWire. Free plan is 40 GB storage with a 4 GB upload cap and files expire after 3 days; 20 downloads per file per day. Retention makes it unusable as storage, and…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field
Sibling records disagree:
- verdict:
storage/file-io-2says dead, storage/file-io-3 says fails-quota - verdict:
storage/file-iosays fails-quota, storage/file-io-2 says dead - identity_kind:
storage/file-iosays institution, storage/file-io-2 says email
- Free allowance
- The REST flow printed in its own /about page no longer works: POST to both file.io and www.file.io returns 405 MethodNotAllowed from an S3-style object store.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- checked 2026-10-21checked 2026-10-21 (inherited)
| Free tier | The REST flow printed in its own /about page no longer works: POST to both file.io and www.file.io returns 405 MethodNotAllowed from an S3-style object store. unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
| Parsed numbers |
|
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.file.io/ | the text of Free tier, above |
More fields 1
| dead end | {"failure_class": "dead-service","why": "The REST flow printed in its own /about page no longer works: POST to both file.io and www.file.io returns 405 MethodNotAllowed from an S3-style object store.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field