Gofile

gofile.io · Storage · 1 record · JSON

Gofile Storage

caveatinstitutionno cardRretention-clamped

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

Free tier	no storage figure at all on the free tier — free accounts get temporary storage with a 10,000-content cap per account ('Free accounts are capped at 10,000 stored contents'); free traffic allowance is '100 GB traffic / 30 days' unit GB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	30 days' \| content is deleted after 10 days of inactivity unless it keeps being downloaded; past the storage period content may be moved to cold storage and importing it back requires Premium; most API endpoints (listing, direct links) return error-notPremium; 'Repeatedly exceeding rate limits may result in automatic IP bans' (30 days)
Egress	free plan: '100 GB traffic / 30 days'; 'We never throttle bandwidth' but traffic over the allowance restricts download functionality. Premium removes caps entirely
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: ny-small-file datasets unlimited guest accounts created by API call (no email, no human-verification step) x 10,000 files each — probe-verified; each guest account also brings its own 100 GB/30-day
Limits	retention-clamped deleted after 10 days source content is deleted after 10 days of inactivity unless it keeps being downloaded; past the storage period content may be moved to cold storage and importing it back requires Premium; most API endpoints (listing, direct links) return error-notPremium; 'Repeatedly exceeding rate limits may result in automatic IP bans'
Binding	retention-clamped a clock, not a quota: bytes leave whether or not the client is finished with them
Interface	rest, rclone rest
Tooling	REST API at api.gofile.io (documented, CORS, per-endpoint rate limits); rclone backend 'gofile' (Tier 1) but its docs warn 'if you wish to connect rclone to Gofile you will need a premium account'; guest account creation is a single unauthenticated POST
Composes with	unlimited guest accounts created by API call (no email, no human-verification step) x 10,000 files each — probe-verified; each guest account also brings its own 100 GB/30-day traffic bucket, so fetch load can be sharded by account
Reliability	10-day inactivity expiry plus cold-storage migration makes it storage-with-a-TTL, not a drive; content-count cap (10k) bites hard on many-small-file datasets
Notes	no storage figure at all on the free tier — free accounts get temporary storage with a 10,000-content cap per account ('Free accounts are capped at 10,000 stored contents'); free traffic allowance is '100 GB traffic / 30 days'
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	gofile.io/faq	'Content is kept for 10 days of inactivity', 'Content past its storage period may be moved to cold storage', free traffic counted per IP
2026-10-21	gofile.io/api	'Free accounts are capped at 10,000 stored contents', error-limits/error-notPremium statuses, rate limits per IP and per account
2026-10-21	api.gofile.io/accounts	probe: POST (no auth) -> {"status":"ok","data":{"tier":"guest","token":"DtZGU7IXTjUXIor2UTCc8LwVuuELs1e7"}} (unlimited anonymous identities, one HTTP call each)
2026-10-21	store4.gofile.io/contents/uploadfile	probe: POST (no token) -> 200, file stored, downloadPage https://gofile.io/d/nxWCc29o; later GET api.gofile.io/contents/nxWCc29o with the guest token -> {"status":"error-notPremium"}

Unknown or withheld values (4)

$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.