GoPro Cloud / Quik
gopro.com · Netdisk and pan · 1 record · JSON
GoPro Cloud / Quik (GoPro subscription) Netdisk and pan
caveatemailno cardRwrite-gated
| Free tier | Unlimited cloud storage for GoPro content, meaning footage captured with a GoPro camera excluding Fusion, on any paid tier, plus 100 GB for non-GoPro content on Premium at USD 59.99/yr or 500 GB on Premium+ at USD 99.99/yr unit unlimited; metered on stored-bytes; unlimited applies to provenance, not to bytes: the terms draw the line at content captured with a GoPro camera |
|---|---|
| Price | USD 59.99/yr Premium and USD 99.99/yr Premium+, which is about USD 120/TB/yr on the 500 GB non-GoPro half and approaches zero on the GoPro half |
| Per-object cap | Not published as a byte cap. Non-GoPro storage is restricted to a published file-type list |
| Retention | While the subscription is active. No retention clock published |
| Egress | CDN downloads of originals with no published cap; access is by a bearer token against api.gopro.com |
| Identity | email an email address and a card for the subscription |
| Limits | |
| Binding | write-gated The capacity is unlimited on paper and the gate is a provenance rule plus an upload path nobody has documented. Until one large non-GoPro file is uploaded and accepted, the offer is 100 GB at USD 59.99/yr, which is bad. |
| Interface | rest |
| Tooling | reverse-engineered and read-only in every public wrapper: himewel/gopro-api in Python, dustin/gopro in Go with 139 stars and a push on 2026-10-13, gsora/gpdwn, mvisonneau/gpcd. All of them search, download and sync; none uploads. Auth is a bearer token lifted from a plus.gopro.com web session |
| Composes with | The most valuable unresolved lead in its group and it is one upload experiment, not a research question. The terms draw the line at provenance by device, not by file inspection, so if ingest does not verify capture provenance then unlimited capacity at USD 59.99/yr exists; if it does, the offer collapses to 100 or 500 GB |
| Reliability | No public wrapper implements upload, so the write path is undocumented rather than absent: the Quik app clearly uploads. Treat the write path as unproven. GoPro's own supported-file-type article returned an empty body through the reader, so the type list is unverified |
| Notes | Recorded as an experiment with a design, not as a finding: one account, one test upload of a large file that a GoPro did not capture, and the answer decides between unlimited and 100 GB. The price on the non-GoPro half is about USD 120/TB/yr, so the whole value is in whether provenance is checked. |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| Parsed numbers |
|
Evidence (6)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | gopro.com/en/us/legal/subscriptionterms | 'You receive unlimited cloud storage for content You capture with a GoPro camera (excluding Fusion)' 'up to 100GB of cloud storage for content You capture with a non-GoPro camera'; 'Storage of non-GoPro footage is limited to the file types listed' |
| 2026-10-21 | gopro.com/en/dj/shop/subscriptions | Premium USD 59.99/yr with unlimited GoPro and 100 GB non-GoPro Premium+ USD 99.99/yr with 500 GB |
| 2026-10-21 | github.com/himewel/gopro-api | 'Unofficial Python client for the GoPro cloud / Quik HTTP API at api.gopro.com: search your library and fetch download metadata', download only |
| 2026-10-21 | github.com/dustin/gopro | 139 stars, last push 2026-10-13, sync and download with no upload |
| 2026-10-21 | github.com/gopro/labs/discussions/1400 | GoPro's own forum, users asking for upload functionality, which confirms there is no official upload API |
| 2026-10-21 | community.gopro.com/s/article/What-Content-Is-Supported-In-G | opened but JavaScript-rendered and the body came back empty, so the supported-type list is unverified |
More fields (4)
{
"access_mode": "paid",
"upload_api": "none documented; the Quik app uploads but no wrapper implements it",
"provenance_rule": "by capture device, excluding Fusion",
"test_that_settles_it": "one account, one large non-GoPro upload, then read the quota back through api.gopro.com"
}