Gumroad
- Free allowance
- Own help centre: 'If you price your product at any number greater than $0.99, the largest single file that you can upload to a product is 20 GB in size... you can add as many files as you want to each product.' Free/$0 products are capped at 250 MB cumulative.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- per-object-caplargest single file that you can upload to a product is 20 GB
- Evidence
- reported6 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Own help centre: 'If you price your product at any number greater than $0.99, the largest single file that you can upload to a product is 20 GB in size... you can add as many files as you want to each product.' Free/$0 products are capped at 250 MB cumulative. unit MB; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
per-object-cap 20 GB (products >$0.99) / 250 MB cumulative (priced $0). 'Download all' button only appears under 500 MB total content, but a single ZIP sidesteps that. Repo shows MAX_EPUB_READER_ARCHIVE_SIZE = 32 MB and thumbnail cap 5 MB — those are feature caps, not the product-file cap. |
| Identity | email an email address and a password, or a Google or X sign-in, on the signup form. No card and no phone number appear on that form, and uploading files needs no payout profile; withdrawing sales runs a Stripe identity check that asks for a date of birth, phone number and possibly a government ID. |
| Egress | CloudFront in front of S3 (confirmed in their open-source repo: CLOUDFRONT_* + FILE_DOWNLOAD_DISTRIBUTION_URL_PROD). No per-download quota published. |
| Per-object cap | largest single file that you can upload to a product is 20 GB (20000000000 bytes) |
| Retention | not stated |
| Interface | rest Web + documented REST API (products, product_files); the codebase is open source (antiwork/gumroad), so limits are inspectable. |
| Tooling | REST API with access token; the repo exposes /attachments/... presigned paths via SignedUrlHelper. |
| Composes with | The $0.99 pricing gate is the mechanism: price at $1, get 20 GB/file, unlimited files per product, unlimited products. A $1 product that never sells still costs the seller ~nothing after fees. 20 GB x N files. |
| Reliability | Purchases require a payment method on the seller side to withdraw, but uploading does not. Download URLs are presigned CloudFront/S3 and short-lived, so there is no stable hot-link — archive/delivery tier only. |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | gumroad.com/help/article/289-file-size-limits-on-gumroad | '20 GB File size limit' and '250 MB limit' sections, verbatim |
| 2026-10-21 | source not published | raw.githubusercontent.com/antiwork/gumroad/main/app/models/product_file.rb — confirms S3/CloudFront storage classes and that 20 GB is not enforced in this model, i.e. it is a policy cap at the uploader |
| 2026-10-21 | source not published | config/initializers/aws.rb + .env.example in the same repo — CLOUDFRONT_DOWNLOAD_DISTRIBUTION_URL_PROD, FILE_DOWNLOAD_DISTRIBUTION_URL_PROD, S3_BUCKET production 'gumroad' |
| 2026-10-21 | gumroad.com/ | 200, 128,717 B (live, not a dead host) |
| 2026-11-01 | gumroad.com/signup | the signup form offers a Google or X sign-in, or an email address and a password, and asks for nothing else |
| 2026-11-01 | gumroad.com/help/article/289-file-size-limits-on-gumroad | the 20 GB per-file ceiling for a priced product is unchanged |
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