When a GoPro cloud upload failed, the expensive mistake usually happens hours later, and it is not a technical one. The card is full, the shoot is tomorrow, the app said the clips were backed up, and the operator picks Format in the camera to free the space. That single action converts a delayed sync into a permanent loss, and it is entirely avoidable because the cloud copy either exists or does not, and that can be established in about ten minutes.
Treat the card as the only surviving original until you have proved otherwise, and assume it has not been reformatted.
Why a stalled upload is not the same as a failed one
Cloud sync for action cameras is a queue, not a transaction. Files are uploaded in the background, in an order determined by the app, often starting with the smallest items. A connection that drops mid-file leaves a partial object, and the app’s queue logic will retry, resume, or skip depending on the client and the network. From the user’s screen, a stalled upload and a completed upload look similar: a grid of clips with thumbnails.
That similarity is the trap. Assume nothing is backed up until you have tested it, and test with something that costs a download rather than a glance.
Verification method one: count the media, not the thumbnails
The fastest reliable test is an inventory comparison, and the key word is media.
Connect the card to a computer and open the DCIM folder. GoPro cameras write clips into numbered folders, most commonly 100GOPRO, 101GOPRO, and so on, and each recording produces a set of related files with a shared sequence number: a main video named GX01 (or GH01 on older models), a low-resolution proxy with an LRV extension, and a thumbnail with a THM extension.
Count only the main video files. Then open the cloud library and count the videos present for that shoot date. The two numbers should match exactly.
This is where the counterintuitive detail lives. In the cloud library, a clip can appear with a visible thumbnail while the video itself has not uploaded, because the thumbnail is a separate file measured in kilobytes and the video is measured in gigabytes. The upload queue sends the small file first, so a grid full of thumbnails is fully consistent with a cloud library that contains no footage at all. Never accept a thumbnail as evidence.
| What you see in the app | What it actually proves | What to do |
|---|---|---|
| Thumbnail visible for a clip | A small sidecar file arrived | Download the clip and confirm it plays |
| Clip listed with a duration | The client has metadata for the clip, possibly from the card | Compare total sizes, not just counts |
| Upload progress showing 100 percent | The client believes the transfer finished | Download the file back and check the closing seconds |
| Clip plays from the cloud | The media uploaded | Safe to reuse the card for that clip |
| Clip absent from the cloud | Nothing uploaded for that clip | Keep the card untouched until it is copied elsewhere |
Verification method two: download and compare
Counting catches missing clips. It does not catch a clip that uploaded incompletely, which is the failure mode specific to interrupted uploads. For that, compare the artifacts themselves.
Pick the largest and most recent file, download it, and compare it against the original in three ways: size in bytes, duration reported by a player, and the last thirty seconds of playback. Size and duration will agree for a complete file and will rarely both agree for a truncated one, because a container that lost its tail loses its index with it.
If you want a stronger check, generate a checksum of the local original and of the downloaded copy with a tool such as certutil -hashfile on Windows or shasum on macOS and compare the values. Cached, re-encoded, or re-wrapped copies will legitimately fail a byte comparison, so treat a mismatch as a signal to inspect the file rather than as proof of failure.
A second copy that exists on your own drives is a better answer than a cloud copy you cannot test. The offline and on-the-road options are compared on the GoPro backup without a computer page, and the general redundancy pattern is on the drone and action camera backup workflow.
How to hold the card while the question is open
Until the cloud inventory matches the card inventory, the card is the master copy and must be handled accordingly.
- Do not format it in the camera. A camera format is the single action that most reduces what can be recovered later, and it is not needed to answer the question above.
- Do not delete individual clips from it. Selective deletion is nearly as destructive as a format for the clips involved.
- Do not keep recording on it. New recordings consume free space, and a card that is full of new footage is a card where the original data has been overwritten.
- Do not leave it in the camera. Cameras write housekeeping files on power-up; the card is safer in a static, powered-off state.
- Label it physically. A card with a strip of tape reading the shoot date and “do not format” survives a busy week in a way that a verbal agreement does not.
- Copy it somewhere else now, even partially. A local copy on a laptop drive takes minutes and removes the deadline pressure that causes the wrong decision.
If you genuinely must keep shooting on that card, take a sector-level image first, or buy a replacement card. A new 128 GB card costs a fraction of a recovery attempt, and the comparison is the whole argument.
If the card was already reformatted
The first task is to stop treating the clock as a timer, because elapsed time is not what closes the recovery window. What closes it is the amount of new data written to the card. A card formatted two weeks ago and then left in a drawer is in better shape than one formatted an hour ago and used for a 4K session. The second task is to understand which files are at risk first, and the answer is counterintuitive. A camera format rebuilds the file system, and the camera then allocates new recordings from the beginning of the free space. The files written earliest on the card are therefore the ones that new recordings overwrite first, while the last clips of the shoot, which sat at the end of the previously used area, tend to survive longest. If the cloud failure was recent and the lost files are the newest ones, the odds are better than they look. The mechanics of a camera-side format are set out on the recovery after formatting page.
| How the card was used after the format | What is typically still intact | Practical next step |
|---|---|---|
| Not used at all since the format | Nearly everything, subject to normal wear | Image the card and scan the image |
| Used for a short session, a few gigabytes | Most of the older footage; the newest clips at highest risk | Stop using it and scan immediately |
| Used repeatedly for days of recording | Only scattered fragments | Send it to a professional evaluation rather than scanning repeatedly |
| Used and then formatted again | Little that a consumer scan will find | Professional evaluation, and accept that the outcome may be poor |
What no tool or laboratory can do is recover data that has been overwritten. Once new files occupy those clusters, the original bytes are gone, and the honest answer is that the cloud upload that failed is now the only surviving version. That is why the verification step in this article matters more than the recovery step: it is the only part that is entirely within your control. The general handling sequence for a lost-footage situation is set out on the data loss emergency guide.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive.
Frequently Asked Questions
The app says my GoPro clips are backed up. Can I format the card?
Not until you have compared the counts and sizes yourself. Cloud clients have reported clips as backed up when only the sidecar thumbnail had uploaded. Download one large clip, confirm it plays to the end, and only then reuse the card.
Why do clips show in the cloud with a thumbnail but no video?
Because the thumbnail is a separate file of a few kilobytes and uploads far earlier than the multi-gigabyte video. A thumbnail in the library says nothing about whether the media arrived.
Does the GoPro cloud upload LRV and THM files?
Usually not, which matters before you treat a missing proxy file as a sync failure. Compare main video files only, since proxy and thumbnail files are not part of the deliverable.
How long after formatting the card can files still be recovered?
There is no time limit, only a data limit. Files survive until those clusters are overwritten, so a card that has not been used since the format is largely intact regardless of elapsed time, while a card reused for hours of recording may already be beyond a consumer scan.