- Free allowance
- 1 TB permanent handed out as claimable promo codes that are repeatable and stackable: '加上之前的活动，有 2t 了' and '都是永久'.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- country-phoneno card, phone required
- Binding limit
- per-object-cap1 GB per file on a free account
- Evidence
- reported8 sources; a third party said so
- Freshness
- stale on 2026-11-19checked 2026-11-04 (inherited); stale on 2026-11-19
| Free tier | 1 TB permanent handed out as claimable promo codes that are repeatable and stackable: '加上之前的活动，有 2t 了' and '都是永久'. A separate 1 TB plus 10 GB baseline per a 2026 comparison post unit TiB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) 1 GB per file on a free account source
- per-ip-shaping free downloads reported at 300 to 400 KB/s source
- write-gated the OpenList driver is cookie-based, and the netdisk-fast-download auth table requires a logged-in cookie for UC source
|
|---|
| Binding | per-object-cap The per-file cap is what closes it, not the quota or the identity. |
|---|
| Identity | country-phone an Alibaba account, which is +86-bound in practice, and the SVIP tier needs a Chinese identity document |
|---|
| Egress | Free downloads are throttled hard, with reports of 300 to 400 KB/s for video: 'UC网盘之前宣称不限速，现在下载视频三四百k'. The paid tier advertises 上传下载不限速 as an SVIP benefit |
|---|
| Per-object cap | 1 GB per file on a free account: 'UC网盘2t,但单文件就1G，相当难用' (1000000000 bytes) |
|---|
| Retention | Promo capacity is permanent once claimed. No retention clock on stored files is published |
|---|
| Interface | rest |
|---|
| Tooling | No public API. A reverse-engineered client mounts it: the OpenList UC driver takes a pasted browser cookie, root folder id 0. A separate UC TV driver pairs by QR code from the mobile app and supports list and download only. Same backend family as Quark. No official S3 or WebDAV |
|---|
| Composes with | Codes are batch-minted, a hundred a month per one poster, and shared in threads, so one account can stack several to 2 TB. Each account is a +86 identity, and the 1 GB per-file ceiling makes the capacity useless as a dataset store |
|---|
| Reliability | Promo capacity is permanent once claimed, but the 1 GB per-file ceiling makes it a media-hoarding pan and not a dataset store. Download tickets are IP-bound on the shared Quark backend, so a harvested cookie dies on the first replay |
|---|
| Notes | The two together are the finding: the capacity is real, permanent and pointless because of a 1 GB ceiling. |
|---|
| Parsed numbers | - has-free-tier 1
- per-object-cap 1 GB
- per-ip-shaping 400 KB
|
|---|