Skip to content

GitHub Gist

gist.github.comPaaSstorage/github-gistJSON compare report an error provider JSON

Free allowance: Unlimited gists per account; each gist is a full Git repo.
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: institutionno card, no phone
Binding limit: per-object-cap100 MiB per single file; 100 MiB per file
Evidence: reported4 sources; a third party said so
Freshness: stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05

Free tier	Unlimited gists per account; each gist is a full Git repo. Hard block at 100 MiB per single file; 2 GB per push. Total repo size is not capped, only 10 GB on-disk is the documented recommendation. unit GB; metered on unstated
Price	none stated
Limits	per-object-cap (binding) 100 MiB per single file source per-object-cap (binding) 100 MiB per file source 100 MiB per file hard block (pre-receive hook); ~80 writes/min, 500/hr, 5000 REST req/hr per token; API truncates file content at 1 MB and files list at 300 unless you clone; 6 pushes/min per repo recommended.
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
Identity	institution not published
Egress	unmetered free downloads from gist.githubusercontent.com; docs state 'We don't limit the total size of the binary files in the release or the bandwidth used to deliver them'. No egress metering observed across repeated 60 MB pulls (~1.3-2.0 s each).
Per-object cap	100 MiB per single file (104857600 bytes)
Retention	not stated
Interface	s3, rest, git, rclone part of the text of Free tier, above
Tooling	git clone/push against gist.github.com/<id>.git, gh gist create, REST POST /gists, github.com/bharatcj/git-unlimited-storage (S3-shaped shim over a repo, MIT, 0 stars), rclone backend 'gist' does NOT exist — use plain git plus a CDN in front.
Composes with	unlimited gists x unlimited free GitHub accounts, each gist 100 MiB/file x as many files as the push allows. Practical unit is 'one gist repo per dataset shard'.
Reliability	Push hook is strict and fires at 100 MiB; pushes into a repo already carrying hundreds of MB start failing before the per-file cap is reached, so keep each shard repo small. Read path was consistently fast and cache-friendly.
Parsed numbers	per-object-cap 100 MiB per-object-cap 100 MiB

Evidence 4

date	source	what it proved
2026-10-21	docs.github.com/en/repositories/creating-and-managing-reposi	'Single object size ... is enforced at 100 MB', 'Push size: This limit is enforced at 2GB', on-disk 10 GB recommendation, 15 reads/s per repo
2026-10-21	source not published	probe: git push of 60,000,000-byte file into gist 8fafc3fc9486dc10c88b24317cffd7e9 -> rc=0, then GET gist.githubusercontent.com/.../raw/big60.bin -> 200, bytes=60000000, 1.3-2.0 s
2026-10-21	source not published	probe: 119.21 MB file push -> 'remote: error: File big125.bin is 119.21 MB; this exceeds GitHub's file size limit of 100.00 MB' / pre-receive hook declined
2026-10-21	source not published	probe: gh gist create of a 90 MB and 95 MB file -> 'failed to collect files for posting: binary file not supported' (CLI path rejects binaries; use git push instead)

Unknown values 4

$.identity_cost.detail boilerplate
$.per_object_cap.notes 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
$.retention.stated the field may be stated in a source that was not read