Fandom

fandom.com · Storage · 1 record · JSON

Fandom (wiki farm, MediaWiki) Storage

caveatinstitutionno cardRper-object-cap

www.fandom.com · media · storage/fandom · JSON · compare

Free tier	10 MB per file, no file-count cap: 'The maximum size of uploads is 10 MB. The maximum image resolution is 12.5 megapixels.' and 'There is no limit to the number of files you can upload' (with the caveat 'they shouldn't be used just as file stores'). unit MB; metered on stored-bytes
Price	none stated
Per-object cap	10 MB per file (10000000 bytes)
Retention	request-rate: MediaWiki edit-rate limits per IP; anon upload needs a CSRF token (probe returned `badtoken`). Retention: permanent, but Fandom never deletes content even on community request.
Egress	Unmetered, Cloudflare-fronted static CDN. But see the read-path trap below.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: the 9,979-byte original whose sha1 ce3dee8b... matches the API. You must append `&format=original` to get your bytes back. Textbook 'gives you storage but not your bytes'. 10 MB x un
Limits	per-object-cap 10 MB per file source per-object-cap: 10 MB (hard, confirmed live via siteinfo `maxuploadsize` = 10485760). request-rate: MediaWiki edit-rate limits per IP; anon upload needs a CSRF token (probe returned `badtoken`). Retention: permanent, but Fandom never deletes content even on community request.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, rclone rest
Tooling	MediaWiki Action API per wiki (`action=upload`), Pywikibot/mwclient. No rclone backend.
Composes with	10 MB x unlimited files x unlimited free wikis (wiki creation is self-service). 10 MB is small enough that this only matters as a shard layer.
Reliability	Two read-path traps in one host. (1) `static.wikia.nocookie.net` returns `403 Cf-Mitigated: challenge` to any non-browser — a hard read gate. (2) When it does serve, it RE-ENCODES: a request for a .png returned `Content-Type: image/webp`, 6,326 bytes, sha1 ada19fa5... — NOT the 9,979-byte original whose sha1 ce3dee8b... matches the API. You must append `&format=original` to get your bytes back. Textbook 'gives you storage but not your bytes'.
Notes	10 MB per file, no file-count cap: 'The maximum size of uploads is 10 MB. The maximum image resolution is 12.5 megapixels.' and 'There is no limit to the number of files you can upload' (with the caveat 'they shouldn't be used just as file stores').
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 10.0 MB

Evidence (4)

date	source	what it proved
2026-10-21	community.fandom.com/wiki/Help:Uploading_files	'The maximum size of uploads is 10 MB ... There is no limit to the number of files you can upload'
2026-10-21	minecraft.fandom.com/api.php?action=query&meta=siteinfo&sipr	probe: GET -> 200, maxuploadsize = 10485760
2026-10-21	withheld	probe: GET static.wikia.nocookie.net/.../Grass_Block.png/revision/latest (direct and via fetch proxy, browser UA) -> 403 with `Cf-Mitigated: challenge`; via proxy without UA -> 200 but image/webp 6,326 B, sha1 ada19fa5... != API sha1 ce3dee8b...
2026-10-21	withheld	probe: same URL with `&format=original` -> 200, image/png, 9,979 bytes, sha1 ce3dee8bd03c3a66eedef6e710491cf9f4f11e2b == API sha1. Original IS retrievable, but only on the explicit original path.

Unknown or withheld values (5)

$.evidence[2].url private-url
$.evidence[3].url private-url
$.free_tier.notes process
$.per_object_cap.notes 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.