fshy

fshy / Storage

file.io

file.io · Storage · 3 records · JSON

File.io Storage

fails: quotainstitutionno cardRper-ip-shapingdisagrees

file.io · anonymous-dump · storage/file-io · JSON · compare

Sibling records disagree:

Free tierno account; 4 GB per transfer ('file transfers are limited to a total of 4 GB')
unit GB; metered on unstated
Pricenone stated
Per-object capnot stated
Retention4 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)
Egressunmetered direct link, but files self-destruct on first download
Identityinstitution derived from the record's prose, not from an identity field, and no signup was executed: ited to a total of 4 GB') 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-p
Limits
  • per-ip-shaping transfer ('file transfers are limited to a total of 4 GB') 4 GB/transfer source
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').
Bindingper-ip-shaping one stream is shaped, and a user's throughput is the shaped rate times the number of streams
Interfacerest rest
Toolingdocumented REST: curl -F 'file=@x' https://file.io/?expires=1w -> {"success":true,"link":...,"expiry":"7 days"}
Composes withnone — one-download-then-delete semantics make it anti-storage by design.
ReliabilityDocs 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.
Notesno account; 4 GB per transfer ('file transfers are limited to a total of 4 GB')
Evidence rungreported One page read moves it to documented.
Checked2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers
  • $.limits[0].value limit:per-ip-shaping 4.0 GB
Evidence (2)
datesourcewhat it proved
2026-10-21www.file.io/about'file transfers are limited to a total of 4 GB', expires syntax, sample JSON responses
2026-10-21file.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_in_seed": "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 for a user. Upload path FAILED."
}
Unknown or withheld values (5)
  • $.extras.dead_end.retry_when process
  • $.free_tier.notes process
  • $.per_object_cap.notes not-extracted
  • $.per_object_cap.stated not-extracted
  • $.retention.notes not-extracted

file.io (now limewire) Storage

fails: quotaemail?card?Rdisagrees

www.file.io/plans · rejected-provider · storage/file-io-3 · JSON · compare

Sibling records disagree:

Free tierfile.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
unit none; metered on none
Pricenone stated
Per-object capnot recorded
Retentionnot recorded
Egressnot recorded
Identityemail (placeholder) not published
Bindingnone no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interfaceunknown
Toolingnot recorded
Composes withnot recorded
Reliabilityfile.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
Notesfile.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
Evidence rungreported
Checked2026-10-21 (inherited); stale on 2026-11-04
Evidence (3)
datesourcewhat it proved
2026-10-21www.file.io/plansfile.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-21limewire.com/pricingcited 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-21www.file.io/developerscited 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 t",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}
Unknown or withheld values (15)
  • $.chaining not-recorded
  • $.confidence_note withheld
  • $.egress.terms not-recorded
  • $.extras.dead_end.retry_when process
  • $.free_tier.notes process
  • $.identity_cost.detail defaulted
  • $.identity_cost.kind identity-defaulted
  • $.interface interface-unknown
  • $.interface_detail withheld
  • $.limits_note process
  • $.per_object_cap.notes not-recorded
  • $.per_object_cap.stated not-recorded
  • $.retention.notes process
  • $.retention.stated not-recorded
  • $.tooling not-recorded

file.io (documented api path) Storage

deademail?card?Rdisagrees

www.file.io/ · rejected-provider · storage/file-io-2 · JSON · compare

Sibling records disagree:

Free tierThe 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. Listed as a dead end for the do
unit none; metered on none
Pricenone stated
Per-object capnot recorded
Retentionnot recorded
Egressnot recorded
Identityemail (placeholder) not published
Bindingnone no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interfaceunknown
Toolingnot recorded
Composes withnot recorded
ReliabilityThe 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. Listed as a dead end for the do
NotesThe 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. Listed as a dead end for the do
Evidence rungreported
Checked2026-10-21 (inherited); stale on 2026-11-04
Evidence (1)
datesourcewhat it proved
2026-10-21www.file.io/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. Listed as a dead end for the do
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. Listed as a dead end for the do",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}
Unknown or withheld values (15)
  • $.chaining not-recorded
  • $.confidence_note withheld
  • $.egress.terms not-recorded
  • $.extras.dead_end.retry_when process
  • $.free_tier.notes process
  • $.identity_cost.detail defaulted
  • $.identity_cost.kind identity-defaulted
  • $.interface interface-unknown
  • $.interface_detail withheld
  • $.limits_note process
  • $.per_object_cap.notes not-recorded
  • $.per_object_cap.stated not-recorded
  • $.retention.notes process
  • $.retention.stated not-recorded
  • $.tooling not-recorded