Discord

discord.com · 3 records in Storage · JSON

Records 3

caveatDiscord + ddrive (Discord as a datastore)
Storagefree tieridentity email?card?limit per-object-capevidence reportedstale on 2026-11-05
caveatDiscord free account (attachment CDN)
Storagefree tieridentity institution?card?limit per-object-capevidence reportedstale on 2026-11-05
deaddiscord as a durable cdn origin
Storageidentity email?card?evidence reportedchecked 2026-10-21

Discord + ddrive (Discord as a datastore)

Storage

discord.comMessagingstorage/discord-ddriveJSON compare report an error

Free allowance: No total storage cap on free accounts; 10 MB per file on free (20 MB per Discord's own File Attachments FAQ), 50 MB Nitro Basic, 1 GB Nitro; attachments upload up to 500 MiB per file via the cloud-upload endpoint before the message-time limit applies
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: email?placeholder, not evidence; card unknown, phone unknown
Binding limit: per-object-cap10 MB per file; 500 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	No total storage cap on free accounts; 10 MB per file on free (20 MB per Discord's own File Attachments FAQ), 50 MB Nitro Basic, 1 GB Nitro; attachments upload up to 500 MiB per file via the cloud-upload endpoint before the message-time limit applies unit GB; metered on stored-bytes
Price	none stated
Limits	per-object-cap (binding) 10 MB per file source per-object-cap (binding) 500 MiB per file source 24 MB chunk size in ddrive; 500 MiB per-file ceiling on the cloud-upload path; aggressive per-channel message and upload rate limits (ddrive moves to webhooks specifically to route around them); attachment URLs expire (hex `ex` timestamp) and must be re-fetched
Identity	email (placeholder) not published
Egress	Free and CDN-served; every attachment URL is signed with `ex`/`is`/`hm` params, so links are time-limited but re-mintable via the API at zero cost
Per-object cap	10 MB per file (10000000 bytes)
Retention	not stated
Interface	rest rest
Tooling	forscht/ddrive (533 stars, MIT, active 4.x line, Docker image, OpenAPI 3.1 REST front end, Postgres metadata, webhook-based to avoid rate limits) - explicitly 'unlimited file size and unlimited storage'; also theseyan/distore, iShibi/discord-drive
Composes with	Per-file cap x shard count is irrelevant because ddrive splits into 24 MB chunks. Author reports 'tested with storing 4000 GB of data on single discord channel'. Several free Discord accounts, servers and channels each carry a separate allowance, and a bot token can span many channels.
Reliability	Highest operational risk of the set: Discord rate-limits uploads hard, CDN URLs expire, and the reference demo (ddrive.forscht.dev) is currently down (HTTP 522), so the wrapper is battle-tested but its hosted instance is not.
Parsed numbers	has-free-tier 1 per-object-cap 10 MB per-object-cap 500 MiB

Evidence 4

date	source	what it proved
2026-10-21	support.discord.com/hc/en-us/articles/25444343291031-File-At	'For non-Nitro subscribers, the maximum file upload is 20MB.' (page updated 2026-09-30)
2026-10-21	raw.githubusercontent.com/forscht/ddrive/master/README.md	'Supports an unlimited file size and unlimited storage... Tested with storing 4000 GB of data on single discord channel'; 'splitting the file in 24mb chunks'; 'Now uses webhooks instead of bot/user tokens to bypass the discord rate limit' (the author's own phrase for moving uploads to a webhook, which is outside the per-channel message limit)
2026-10-21	raw.githubusercontent.com/discord-userdoccers/discord-userdo	'upload up a file up to 500 MiB directly to Google Cloud'; reference.mdx documents `ex` as 'Hex timestamp indicating when an attachment CDN URL will expire'
2026-10-21	cdn.discordapp.com/embed/avatars/0.png	probe: GET -> 200 image/png via Cloudflare edge; GET https://ddrive.forscht.dev/ -> 522 (demo down)

Unknown values 3

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

Discord free account (attachment CDN)

Storage

discord.comMessagingstorage/discord-free-accountJSON compare report an error

Free allowance: No total storage cap documented anywhere.
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: institution?placeholder, not evidence; card unknown, phone unknown
Binding limit: per-object-cap20 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	No total storage cap documented anywhere. Per-file only: 20 MiB per attachment on a free account since 2026-09-03 (raised from 10 MiB). 10 files per message. Server Boost tiers raise it for all members in that server: Tier 2 = 50 MB, Tier 3 = 100 MB; Nitro Basic 50 MB, Nitro 500 MB (1 GB per the Nitro marketing page). unit objects; metered on stored-bytes
Price	none stated
Limits	per-object-cap (binding) 20 MiB per file source 20 MiB per file is the hard bite. Message create is ~5 messages / 5 s per channel; global ~50 req/s per token; 10,000 invalid requests per 10 min triggers a 24 h Cloudflare ban. Attachment URLs carry `ex`/`is`/`hm` and stop working after 24 h — see reliability_note.
Identity	institution (inferred, not read) not published
Egress	Unmetered and free — cdn.discordapp.com is Cloudflare-fronted and there is no bandwidth metering or egress billing of any kind. This is the strongest egress position in the whole survey.
Per-object cap	20 MiB per file (20971520 bytes)
Retention	\| Attachment CDN URLs are signed and expire in exactly 24 h; the bytes stay on Discord's servers indefinitely but the link must be re-derived via `POST /api/v10/attachments/refresh-urls` (401 without a token) or by re-reading the message
Interface	rest, rclone rest
Tooling	Official Bot HTTP API (`POST /channels/{id}/messages` with files[], or the two-step cloud-upload path). Mature wrappers: forscht/ddrive (533 stars, Discord-as-filesystem with REST + OpenAPI 3.1), missuo/discord-image (212 stars, Go, refreshes CDN links), ShufflePerson/Discord_CDN (link refresher proxy), DisboxApp/server. No rclone backend.
Composes with	100 servers per free account (200 with Nitro) x 500 channels per server = 50,000 text channels per account, and every channel takes unlimited messages. This is the multiplier: not per-file size but per-message count. ddrive's author reports storing 4,000 GB in a single Discord channel, so the practical ceiling is account count x rate limit, not storage.
Reliability	Attachment CDN URLs are signed and expire in exactly 24 h; the bytes stay on Discord's servers indefinitely but the link must be re-derived via `POST /api/v10/attachments/refresh-urls` (401 without a token) or by re-reading the message. Any un-refreshed link returns 404 'This content is no longer available.'
Parsed numbers	has-free-tier 1 per-object-cap 20 MiB

Evidence 4

date	source	what it proved
2026-10-21	docs.discord.com/developers/change-log	'September 3, 2026 — Default File Upload Limit Increase: The default file upload limit has been increased from 10 MiB to 20 MiB for users, bots, webhooks, and interaction responses'
2026-10-21	docs.discord.com/developers/reference	'Attachments uploaded to Discord's CDN have signed URLs with a preset expiry time'; example `?ex=65d903de&is=65c68ede&hm=...`; 'ex — Hex timestamp indicating when an attachment CDN URL will expire'
2026-10-21	source not published	probe: decoded ex/is from a real signed URL (ex=66424c96, is=6640fb16) -> ex-is = 86400 s = exactly 24.0 h; GET that URL today -> 404; GET the same path with no query string -> 404 'This content is no longer available.'
2026-10-21	support.discord.com/hc/en-us/articles/33694251638295	'Number of servers: 100 \| Number of servers Nitro: 200 \| Channels (includes voice/text/categories): 500 \| Upload Base 10MB, Level 2 50MB for all members, Level 3 100MB for all members'

Unknown values 2

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

discord as a durable cdn origin

Storage

docs.discord.com/developers/resources/message#signed-attachmstorage/discord-as-a-durable-cdn-originJSON compare report an error

Free allowance: Signed attachment URLs expire in exactly 24 hours (measured ex-is = 86400) and unsigned fetches 404.
Verdict: deadthe offer or the service no longer exists
Cost: no price stated
Identity: email?placeholder, not evidence; card unknown, phone unknown
Binding limit: noneno named constraint binds
Evidence: reported1 source; a third party said so
Freshness: checked 2026-10-21checked 2026-10-21 (inherited)

Free tier	Signed attachment URLs expire in exactly 24 hours (measured ex-is = 86400) and unsigned fetches 404. A URL cannot be stored in a catalog and reused; every read needs an authenticated… unit none; metered on none
Price	none stated
Identity	email (placeholder) not published
Egress	not recorded
Interface	unknown
Tooling	not recorded
Parsed numbers	has-free-tier 0

Evidence 1

date	source	what it proved
2026-10-21	docs.discord.com/developers/resources/message#signed-attachm	the text of Free tier, above

More fields 1

dead end	`{"failure_class": "dead-service","why": "Signed attachment URLs expire in exactly 24 hours (measured ex-is = 86400) and unsigned fetches 404. A URL cannot be stored in a catalog and reused; every read needs an authenticated…","retry_when": null,"first_recorded": "2026-10-21"}`

Unknown values 7

chaining: no value was recorded for this field
egress terms: no value was recorded for this field
interface: the access interface was not established
per object cap notes: no value was recorded for this field
per object cap stated: no value was recorded for this field
retention stated: no value was recorded for this field
tooling: no value was recorded for this field