Snap Store

snapcraft.io · Storage · 1 record · JSON

Snap Store (api.snapcraft.io / snapcraft.io) Storage

caveatemail?card?Rper-object-cap

snapcraft.io/store · paas · storage/snap-store · JSON · compare

Free tier	No published total-storage quota and no published per-snap byte cap; the practical ceiling is what the upload tooling survives. Evidence of real large artefacts: `kicad` stable snap is 1,659.5 MB and `android-studio` is 1,657.8 MB in the channel map (both served fine). A 5.5 GB upload attempt returned HTTP 500 and was diagnosed by Canonical as 'a timeout in the object storage load balancers'. 1.7 GB is documented as working; ~5 GB class uploads fail with a server-side timeout. unit MB; metered on stored-bytes
Price	none stated
Per-object cap	per-object-cap: not documented, empirically ~1.7 GB (1700000000 bytes)
Retention	per-object-cap: not documented, empirically ~1.7 GB works and 5.5 GB 500s (object-storage load-balancer timeout). retention: indefinite, full revision history retained (each revision is a separate stored .snap)
Egress	Free and CDN-backed. Downloads go through api.snapcraft.io -> redirect -> a CDN; no billing, no per-download accounting.
Identity	email (placeholder) not published
Limits	write-gated application/octet-stream` verified) source per-object-cap per-object-cap: not documented, empirically ~1.7 GB source per-object-cap: not documented, empirically ~1.7 GB works and 5.5 GB 500s (object-storage load-balancer timeout). retention: indefinite, full revision history retained (each revision is a separate stored .snap). request-rate: not documented. A 'FATAL ERROR: Data queue size is too large' error hits multi-GB uploads client-side too.
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	`snapcraft upload` / `snapcraft push` (the write path), Snap Store API v2 (`api.snapcraft.io/v2/snaps/info/<name>` with header `Snap-Device-Series: 16`) for metadata, and plain HTTPS GET of the channel-map `download.url` for bytes. No rclone backend; a wrapper would have to speak the snapcraft upload protocol to push.
Composes with	unlimited snaps per publisher account x unlimited revisions per snap (revision history is retained server-side - the forum thread discusses 3 GB across 3 revisions of a 1 GB game). Multiply by unlimited free Ubuntu One accounts. Realistically ~1.6 GB x N revisions x N snaps, but upload reliability degrades well before 5 GB.
Reliability	The write path is the weak link, not storage: multi-GB uploads fail with opaque HTTP 500 ('timeout in the object storage load balancers') and with client-side 'Data queue size is too large'. Bytes are served perfectly once published (`200 77574144 application/octet-stream` verified). Snaps are squashfs images - arbitrary content must be packaged into a snap with a valid snapcraft.yaml, so this is a wrapper-only route.
Notes	No published total-storage quota and no published per-snap byte cap; the practical ceiling is what the upload tooling survives. Evidence of real large artefacts: `kicad` stable snap is 1,659.5 MB and `android-studio` is 1,657.8 MB in the channel map (both served fine). A 5.5 GB upload attempt returned HTTP 500 and was diagnosed by Canonical as 'a timeout in the object storage load balancers'. 1.7 GB is documented as working; ~5 GB class uploads fail with a server-side timeout.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[1].value` limit:per-object-cap 1.7 GB

Evidence (4)

date	source	what it proved
2026-10-21	forum.snapcraft.io/t/snap-package-file-size-limit-on-the-sto	5.5 GB upload 500s; Canonical: 'it seems to be related to a timeout in the object storage load balancers'
2026-10-21	forum.snapcraft.io/t/fatal-error-data-queue-size-is-too-larg	'I'm trying to upload a new version of Kicad, which is 1,7GBytes ... FATAL ERROR: Data queue size is too large'
2026-10-21	api.snapcraft.io/v2/snaps/info/kicad	probe: GET (Snap-Device-Series: 16) -> channel-map download.size 1,659,5xx,xxx bytes (1.66 GB stored and served)
2026-10-21	withheld	probe: GET .../snaps/download/amcUKQILKXHHTlmSa7NMdnXSx02dNeeT_2955.snap with -L -> 200, 77,574,144 bytes, application/octet-stream (core22, real squashfs bytes)

Unknown or withheld values (6)

$.evidence[3].url private-url
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.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.