The wedding was three hours long and it lives entirely on a microSD card that came out of a HERO11 helmet mount at the reception. The card is bent. Or the GoPro has been sitting on a workbench for two days after being pulled off a drone that crashed into a lake, and when you insert the microSD into a card reader, macOS wants to initialize it. Or you were filming a ski run in Utah, the battery died in the cold before you got to the bottom, and the last chapter file — the good part of the run — is a 3.8 GB .MP4 that no player will open. Or your GoPro shows “SD Error” on the front LCD, refuses to record another clip, and the four hours of surf footage from this morning is either on the card or is not — you can’t tell without pulling it and reading it somewhere else, and every article you find online tells you to reformat, which is the exact thing your instincts are screaming at you not to do.

Gillware recovers data from GoPro cameras and the microSD cards that record them — physically damaged cards, cards that show “SD Error” or “Card Error,” cards where files are missing or won’t play, and clips where the recording ended abruptly and the .MP4 is broken. This is one of the spokes under our broader video recovery hub. If your recovery is on a Micro Center-purchased microSD, a professional cinema card, or another manufacturer’s action camera, that hub will route you to the right page.

How GoPros record — and why that matters for recovery

Every current GoPro model records to a microSD card. Modern HERO cameras require U3 or V30-rated cards at minimum for 4K recording, and V60 or V90 cards for the highest 5.3K and 5K bitrate modes. The GoPro Max and Fusion 360-degree cameras use two cards, one per lens, with an internal stitching layer that combines the two recordings.

The file structure on the card is where a lot of the recovery-relevant detail lives. GoPro splits long recordings into “chapter files” that are typically capped around 4 GB each — a limit that originated in FAT32 filesystem constraints and persists for compatibility. A single continuous recording of a bike race, a surf session, or a wedding ceremony may show up on the card as a chain of files: GOPR0001.MP4, GP010001.MP4, GP020001.MP4, and so on. The naming convention encodes the chapter order — GP01 is the second chapter of clip 0001, GP02 is the third, and so forth. A recovery that returns some chapters but not others produces footage that appears to cut off abruptly and resume elsewhere without continuity.

Every recorded clip also produces two supporting files: a low-resolution .LRV proxy that the GoPro app uses for quick preview, and a .THM thumbnail. These files often survive when the main .MP4 does not — which means that in a bad recovery scenario, we can sometimes prove the shot existed even if reconstructing the full-resolution version requires more work.

Recording format matters too. HERO7 and later cameras can record in HEVC (H.265) as well as H.264. The two codecs have different container behaviors when a file is truncated, and the recovery approach for a broken HEVC clip is not identical to the recovery approach for a broken H.264 clip. Cameras recording in HyperSmooth, TimeWarp, or 360-degree modes produce additional metadata that has to be preserved for the file to play correctly after recovery.

Physical damage to GoPro microSD cards

GoPro cards come in with a physical damage profile that ordinary SD card recoveries rarely see. Because GoPros ride on helmets, chests, handlebars, dashboards, surfboards, ski helmets, and drones, the cards that hold their footage get exposed to failure modes that a card in a desktop camera never faces.

The patterns:

• Crushed cards from impact. A helmet cam in a motocross crash. A chest mount hit by a fall in a bike race. A GoPro on a race car that flipped. The card itself — which is millimeters thick — can be physically bent, cracked, or crushed by the impact even if the camera looks salvageable from the outside.
• Water damage. GoPros are marketed as waterproof, and they usually are — until they aren’t. A housing seal fails during a dive. A drone hits a lake. A surf session ends with water inside the camera body. The card comes out wet, and the electronics can be damaged even if the plastic looks fine.
• Snapped cards from drone crashes. Drone-mounted GoPros in crashes produce card damage patterns of their own — the card can be ejected from the slot during impact and land somewhere in the wreckage bent or broken.
• Cards ejected mid-recording. A quick-swap workflow that pulls the card while the GoPro is still processing, or a slot door that pops open in a fall, can leave the card physically fine but the last recording incomplete on the media.
• Heat damage. A GoPro left in a hot car, or one that stayed in recording mode long enough to reach thermal shutdown, can produce card-controller failures that don’t manifest until you try to read the card in a different device.

Physical recovery of a damaged microSD card involves reading the raw NAND flash chips directly, bypassing the card’s own controller entirely. Where the controller is dead or the card is too damaged to power up, we perform chip-off recovery: the NAND chip is desoldered from the card substrate, read on dedicated NAND reader hardware, and the raw contents are then processed through a controller-emulation stage that reconstructs how the card’s firmware would have arranged the data if it were still operational. This is precision work — the pads on modern microSD NAND are extremely small — and it happens in the same lab in Madison that handles hard drive platter transplants and RAID reconstructions.

Logical corruption — files missing, “SD Error,” broken .MP4

The other half of GoPro recovery cases involves cards that are physically fine but logically broken. The card reads in a computer, the filesystem mounts, and the data appears to be either partly there or partly wrong.

“SD Error” or “Card Error” on the GoPro display. This is the message that turns up on the GoPro’s front LCD when the camera’s firmware refuses to write to the card. It does not always mean the card has failed. Sometimes it means the filesystem has developed inconsistencies that the GoPro’s firmware doesn’t tolerate — inconsistencies that a computer would happily read past. Sometimes it means the card’s write speed has degraded below what the current recording mode requires. Sometimes it does mean the card is failing. In every case, the wrong response is to accept the GoPro’s suggestion to reformat: reformatting overwrites the filesystem structures that hold every file on the card, in exchange for a card the GoPro will consider healthy again but that no longer holds the footage you were trying to save.

Files that are missing from the card entirely. The card was in the camera through the shoot, footage was clearly recorded (the GoPro showed a recording time counter, the LCD confirmed clips were saving), but on the computer the card shows a nearly empty DCIM folder. This is usually filesystem-level damage — the file allocation table has been overwritten, or the card was reformatted after recording, or an interrupted write left the directory structure inconsistent. The underlying data blocks are typically still on the card, unallocated but present, and recoverable through free-space scanning and file carving.

Broken .MP4 with no moov atom. When a GoPro recording ends abruptly — battery died, camera was violently shut off, card was pulled while recording — the final .MP4 file on the card is missing its “moov atom,” the internal metadata structure at the end of every MP4 that tells players where every frame lives. Players open the file, don’t find the moov, and refuse to play. The video data itself is almost always intact; it just needs a moov atom to be usable. In many cases we can reconstruct the moov from a sibling recording made in the same session with the same settings and re-attach it to the broken file, producing a playable clip.

Chapter file discontinuity. If some chapter files are lost from the middle of a long recording, the surviving chapters may play individually but the recording as a whole appears to have gaps. Recovery involves both salvaging the missing chapters where possible (from free space on the card) and rebuilding the chapter chain metadata so that the recovered files chain together correctly in editing software.

Files that play as garbage or freeze mid-clip. A clip that appears intact but drops out partway through, or plays as green/pink/scrambled video, usually indicates that the file’s data blocks were partially overwritten — often because the card was used for additional shooting after the original event but before recovery was attempted. Even in these cases, we can typically extract the surviving portions frame-by-frame.

Camera-side vs card-side vs file-side failures

When someone calls in a GoPro emergency, the first thing to figure out is which of three zones the failure is actually in — because the recovery path is different for each.

A camera-side failure means the GoPro itself is damaged, but the card is fine. The card reads perfectly on a computer, all files play, and the customer just needs to get their footage off. This isn’t really a recovery case — it’s an easy card read. If the card mounts and the files play, the recovery is done before it starts.

A card-side failure means the card is damaged (physical or logical) but the recording itself was successful. Physical damage requires chip-off or controller emulation. Logical damage requires filesystem repair and file carving. This is where most GoPro recovery cases actually land.

A file-side failure means the card and camera are both fine, but the recording itself is broken — an incomplete .MP4, a missing chapter, a garbled clip. This requires file-level repair, moov atom reconstruction, or chapter chain rebuilding. This is often where the “battery died mid-run” or “the good take of the day” scenarios end up.

What not to do while you’re waiting to call us

• Don’t reformat the card when GoPro says “SD Error.” The message is not a diagnostic — it’s the GoPro’s firmware declining to work with the card. Reformatting overwrites exactly the metadata we need to recover files.
• Don’t use the GoPro’s “Repair File” or in-camera formatting options on a card holding important footage. These functions modify the card. In some scenarios they help; in most scenarios they reduce recoverability.
• Don’t keep inserting a damaged or wet card back into the GoPro. A dead short from a damaged card can propagate to the camera’s own electronics. If the card is physically damaged or has been exposed to water, keep it out of the camera until it’s been evaluated.
• Don’t dry a wet card in rice, in the sun, on a heat vent, or in an oven. Water damage in a microSD card is not fixed by drying alone — the corrosion continues on the internal traces even after visible moisture is gone. A wet card should be sealed and shipped as-is.
• Don’t clone the card with generic disk imaging tools. Consumer imaging tools don’t understand NAND-level flash behavior. If the card is degrading, a full-image read with the wrong tool can accelerate the failure and reduce what’s recoverable.
• Don’t shoot new footage on the card. Even if the card appears to work again after an error, any new writes overwrite unallocated blocks where the previous recording’s data still lives — data that could have been carved out.
• Don’t run consumer “GoPro recovery” utilities. Many are legitimate for simple deleted-file scenarios, but on a card with mixed physical and logical damage they can make the underlying data harder to reach. If the footage matters, image the card professionally first.

How Gillware works on GoPro cases

Gillware has recovered data from every generation of GoPro currently in the field and the microSD cards they record to — HERO9 and HERO10 cases from wedding videographers, HERO11 and HERO12 cases from adventure sports, Max and Fusion cases where 360-degree stitching adds a recovery layer, older HERO7 and HERO8 cards from long-term consumer projects, and Sessions and Silvers from every generation. Our lab in Madison, Wisconsin operates NAND-level flash recovery equipment for chip-off work, controller-emulation hardware for cards where the physical NAND is intact but the controller is dead, and an ISO 5 (Class 100) cleanroom for cases where other storage in the same case (a hard drive backup, an offload SSD) also needs physical intervention.

Single-card recoveries — one microSD from one GoPro — run on our risk-free evaluation model: no charge if we can’t recover your data. Cases involving multiple cards, offload drives, or additional storage components carry evaluation on a per-piece basis, and every case gets a specific quote before the paying work begins.

For deadline-sensitive cases — a wedding delivery, a client edit due, a legal or insurance requirement — tell us the deadline when you open the case. GoPro recoveries typically move through the lab quickly compared to multi-drive arrays or complex forensic cases, and we can prioritize the queue where the physics of the recovery allow.

Cross-references for related cases: the general SD card data recovery page covers card physics that apply here too. For B-roll or multicam productions that use GoPro alongside cinema cameras, the video production data recovery hub covers the editing-side considerations. To return to the routing hub for other camera and video failures, see our video recovery hub.