GoPro Not Showing Up on Mac/PC: How to Fix It (2026)

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

You plug in the cable, the charge light blinks on, and the computer keeps showing nothing. The footage is right there on the card, but "GoPro not showing up on Mac/PC" is where a lot of owners get stuck — and many of the published fixes send them chasing a driver that doesn't exist or a menu that isn't there.

The core mistake is treating the GoPro like a USB stick. A directly connected GoPro does not behave like a classic mass-storage drive: depending on generation and mode it speaks MTP, GoPro Webcam/GoPro Connect, or a newer USB control interface. Add Apple silicon's accessory security and Windows' portable-device layer, and "it charges but nothing shows" can have half a dozen different causes.

This guide works symptom-first. You'll separate power from data, rebuild the physical chain, work through the macOS path (Image Capture, Photos, accessory approval) and the Windows path (This PC, Device Manager, Media Feature Pack), then match your specific HERO model — because a HERO9 and a HERO13 do not behave the same way. Finally, you'll learn the card-reader bypass that gets footage off even when direct USB stays stubborn.

It's written for owners of the HERO8 through HERO13 on macOS Ventura, Sonoma, or Sequoia, or Windows 11, and it reflects the current GoPro software lineup — including the fact that Quik Desktop is gone.

Quick Reference: Match Your Symptom First

Before following fixes in order, find the row that matches what you're actually seeing. "Charges but no data" and "detected but empty" are different problems with different first checks.

Start Here: Separate Power From Data

The single most important concept in GoPro transfer troubleshooting is that charging is not proof of data. A USB-C cable can carry power while its data conductors are damaged, missing, or rejected by the host. GoPro's own USB documentation warns that poor-quality cables and adapters can cause communication failures — and some defective cables even behave differently depending on which way the connector is flipped.

That means the first rebuild is physical, in this order:

1. Turn the camera fully on before connecting it. Owners repeatedly connect a powered-off unit, see a charge light, and assume the USB link is up when the camera is not actually enumerating for data.
2. Use a known-good data cable. Test it with another device that transfers files, not just charges. A cable that charges a phone is not evidence it carries data.
3. Connect directly to the computer. Remove USB hubs, docks, monitor ports, and adapters from the chain. A native motherboard or laptop port is the diagnostic baseline.
4. Try a second physical port and, ideally, a second computer. A cable/port combination that fails on one host but works on another immediately moves the problem away from the camera.

Only after that chain is rebuilt should you go OS-specific — because every software fix below assumes the physical layer is sound.

macOS Fixes: Image Capture, Photos, and Accessory Approval

On a Mac, stop expecting a directly connected GoPro to mount in Finder like an external SSD. Direct-camera imports go through Apple's camera-import layer, not classic disk mounting.

First, open Image Capture or Photos. Apple's current Image Capture documentation covers Ventura, Sonoma, and Sequoia and supports importing from connected cameras. Connect the camera, turn it on, then look under Devices in Image Capture — or in Photos' import view. The GoPro appearing there is a successful connection, even if Finder shows nothing.

Next, check Apple silicon accessory security. On Mac laptops with Apple silicon, macOS can require explicit approval before granting a USB accessory data access. The control is under System Settings > Privacy & Security > Accessories. Critically, choosing Don't Allow can block data access while the accessory keeps charging — which reproduces the exact "it charges but nothing shows" symptom. If the GoPro charges but never appears, this setting is a prime suspect.

Finder becomes relevant when the card leaves the camera. With the microSD card mounted through a reader, the card behaves as external removable storage and can appear in Finder normally.

Fallback: OpenMTP. OpenMTP is a free, open-source MTP transfer app with Apple silicon and Intel support, and there are GoPro-owner reports of it succeeding where native Mac transfer struggled on large-file cases. It belongs after Image Capture and the card-reader route — not above the free, built-in Apple tools. MacDroid is a paid alternative that explicitly lists GoPro among supported MTP devices, but it's not mandatory: physically removing the microSD is usually a cleaner bypass than buying a transfer utility.

Windows Fixes: This PC, Device Manager, and Media Feature Pack

On Windows, a GoPro that enumerates correctly appears as a portable device under This PC — it does not always receive a conventional removable-drive letter like E:. That distinction alone explains a large share of "it's not showing up" reports.

Check This PC first. If the camera appears under portable devices with no browsable media, you're past the cable stage and into a media-indexing or mode problem (covered in the next sections).

Use Device Manager, not driver downloads. Windows includes its own Windows Portable Devices/MTP class driver; a separate downloadable "GoPro USB driver" should not normally be required. If the device shows as failed or unknown in Device Manager, uninstall it, rescan for hardware changes, and restart. Reinstalling Microsoft's own inbox driver is the correct repair — downloading unsigned third-party driver packages is not.

Windows N editions get a dedicated callout. Windows 10/11 N editions omit media components, including the Windows Portable Devices infrastructure, until the optional Media Feature Pack is installed. Microsoft states that without those components, media synchronization, image acquisition, and file browsing can be affected. If you're on an N edition, installing the Media Feature Pack and rebooting is often the real fix — skip it and every other step can look broken.

One baseline note: Windows 10 reached end of support in October 2025, so Windows 11 is the sensible current troubleshooting target.

Step 4: Camera Detected but Shows No Files

"Recognized but empty" is its own failure class, distinct from a cable or no-device problem. Windows users have reported HERO11 units appearing in This PC as an MTP device with storage capacity visible, yet no browsable media.

In this state, the connection itself is working; the camera's media exposure layer is not. The highest-value moves:

1. Power-cycle the camera fully, then reconnect. Wait for it to boot completely before attaching the cable.
2. Reconnect the USB cable while the camera is on, and give it a few seconds to enumerate.
3. Pull the card and test it directly in a reader on the same computer. If files appear in the reader, the card and footage are fine — the problem is isolated to the camera's USB/MTP path.
4. On Mac, toggle the Accessory approval once more and re-approve the device, then re-open Image Capture.

Do not reach for formatting here. The footage is likely intact; the issue is how the camera is exposing it.

Step 5: Webcam Works but Media Transfer Doesn't

If the GoPro works as a webcam but won't expose files, the cable and physical connection are confirmed good — you're dealing with a mode or protocol layer, not hardware.

This is the most model-sensitive step in the whole guide:

• HERO9 Black has an officially documented USB Connection choice. The menu path is Preferences > Connections > USB Connection, with MTP for computer media transfer and GoPro Connect for webcam functionality. If webcam works but files won't browse, check that MTP is selected.
• HERO10 through HERO13 are different. Community evidence and the absence of the older selector in newer manuals point to automatic, combined USB handling rather than a manual MTP toggle. If you're on a HERO10 or newer, don't hunt for the HERO9 menu path — it frequently isn't there, and that's expected, not a fault.

The practical takeaway: only the HERO9 gives you a toggle to check here. On newer models, a webcam-works-but-files-don't state points to the host-side paths covered above (This PC, Image Capture, accessory approval, Media Feature Pack) rather than an in-camera setting.

GoPro Model-by-Model USB Behavior (HERO8–HERO13)

Not every generation should be troubleshot identically. Use this matrix to target your model instead of applying generic advice.

A documented HERO11 early-firmware issue produced wired-communication failures that GoPro said could be recovered with Reset Connections plus re-pairing — a useful lever before declaring any HERO10/11 camera dead. One HERO13 isolation case is also instructive: a unit failed on multiple computers while its SD card worked fine in another HERO13, which points to a camera-side USB-port/hardware failure once cables, ports, and hosts have all been ruled out.

The Card Reader Bypass: Fastest Way to Get Footage Off

Whenever the goal is getting the footage now rather than fixing direct USB, remove the microSD and use a reader. This is the single most repeated community recommendation, and GoPro's own manuals for several models suggest a card reader or SD adapter for computer transfer. A reader removes the camera's USB/MTP layer entirely — no drivers, no accessory security, no mode menus.

The reader matters because a cheap adapter reintroduces the same reliability question you're trying to escape. A solid pick is the SanDisk MobileMate USB 3.0 microSD card reader:

• USB-A connector, USB 3.0 (backward-compatible with USB 2.0)
• Up to roughly 170 MB/s transfer capability with compatible cards
• Compact body — about 30.5 × 20.7 × 8.8 mm and roughly 3.4 g
• Two-year limited warranty in applicable regions

Check Price on Amazon

One caveat: the MobileMate is USB-A, so a USB-C-only MacBook needs an adapter or hub — which adds a possible failure point back into the chain. If you're all USB-C, use a known-good adapter and plug the reader directly into it.

If the card itself is the problem, the reader test tells you immediately: a card that works in the reader but not over camera USB isolates the camera side; a card that fails in the reader too points to the card or filesystem — at which point backup and recovery come before any formatting decision.

Camera-Side Fixes: Reset Connections and Firmware Updates

When direct USB fails across every cable, port, and computer, the remaining non-service options are camera-side.

Reset Connections. This is a repeatedly successful community workaround, particularly for HERO10 and HERO11 communication problems, and it was an official recovery step for a documented HERO11 early-firmware issue. The reset clears wireless and pairing state from the camera, which has resolved unexplained USB-recognition failures for many owners. Find it in the camera's connection or wireless preferences, run it, then re-pair and retest the wired connection.

Update firmware — from the microSD card when USB is broken. GoPro supports manual firmware installation from a microSD card on applicable HERO models. This is the recovery path when USB transfer itself is unusable: download the update on a computer, place it on the card per GoPro's instructions, and let the camera update. It runs outside the USB stack entirely, so a firmware-level communication fault doesn't block it.

HERO13-specific workaround. One 2026 community thread describes a recovery sequence of disconnecting the cable, removing and reinserting the battery, powering the camera up, then reconnecting — with the original poster confirming success. Treat this as a low-risk workaround rather than an official procedure, but it's worth trying before a GoPro Repair Guide: DIY Fixes & When to Send It In.

When to conclude it's hardware. If no computer recognizes the camera with several known-good data cables and the SD card works fine in a reader on the same hosts, the camera's USB port or data path is the remaining suspect. At that point, service or replacement is a reasonable conclusion rather than another round of software fixes.

Formatting the SD Card: Last Resort Only

Formatting is the most dangerous "fix" in circulation, and it should never appear early in a detection workflow.

The reason is simple: if the card contains unrecovered footage, formatting destroys the exact data you're trying to access. GoPro's own manuals instruct users to save their media before formatting. Reformatting can resolve a genuinely corrupted filesystem, but only after you've backed up anything recoverable through a reader and confirmed the card itself is the problem — never as a first step to make a camera "show up."

The correct order: back up via reader → test the card on another device → only then reformat in-camera, and only if the card is suspected faulty. If a reader can't see the card either, recovery is the priority, not a quick format.

Myths and Dead Ends to Avoid

These are the common pieces of advice that waste time or make things worse — and several still circulate in older guides.

• "If the GoPro charges, the cable is fine." False. Charge-only/damaged data conductors are possible, and Apple silicon can separately allow power while denying data.
• "The GoPro must appear as a Finder/Explorer disk with a drive letter." False. Direct-camera transfer commonly uses MTP/camera protocols rather than classic USB mass storage.
• "Install the GoPro Windows USB driver." Misleading. Windows normally supplies the MTP/WPD class driver itself; third-party driver packages are not the fix.
• "Reinstall Quik Desktop." Obsolete. GoPro retired Quik Desktop at the end of 2024; the planned Windows version was cancelled and never released. Current desktop playback/export goes through GoPro Player, which is not an importer for making a camera appear as storage.
• "Every HERO has Preferences > Connections > USB Connection > MTP." False. That path is documented for the HERO9; newer models handle USB more automatically.
• "Format the SD card to fix detection." Dangerous as an early step, since it destroys the media you're trying to retrieve.
• "A faster microSD card fixes USB enumeration." It won't — unless the existing card or filesystem is itself faulty.

The common thread: advice that starts with "just download" or "just format" skips the isolation steps that actually identify where the failure lives.

Recommended Gear for Reliable Transfers

Beyond the reader above, these are the components that keep GoPro transfers dependable day to day.

SanDisk Extreme 128GB microSDXC UHS-I — the default card for GoPro work. U3 and V30 speed classes, A2 application-performance rating, and a direct "Works with GoPro" compatibility history. Current Extreme family specs advertise write performance up to roughly 130 MB/s depending on capacity.

Check Price on Amazon

SanDisk Extreme PRO 128GB microSDXC UHS-I — transfer headroom. U3/V30/A2, with advertised read speeds up to 200 MB/s and write up to roughly 140 MB/s on applicable versions. It's a faster card, not a recognition fix: don't expect it to solve a detection problem unless the old card is genuinely failing.

Check Price on Amazon

SanDisk High Endurance 128GB microSDXC — U3/V30/Class 10, rated for roughly 10,000 hours of Full HD recording under SanDisk's endurance methodology. It's marketed for continuous dashcam/security workloads rather than action-camera capture, so while it technically meets the speed classes, Extreme and Extreme PRO remain the better default GoPro picks.

Check Price on Amazon

Data cables. For USB-C-equipped Macs and modern PCs, a USB-C-to-USB-C cable that carries both power and data is the standard; GoPro's HERO13 documentation also explicitly supports USB-A-to-USB-C connections. Buy a cable known to transfer data — not a charge-only accessory — and keep one dedicated to camera work.

Check USB-A to USB-C data cables on Amazon

Check USB-C to USB-C data cables on Amazon

Frequently Asked Questions

Conclusion

Most "GoPro not showing up" cases are not hardware failures. They're a mismatch between how the GoPro actually transfers data — MTP and camera protocols rather than a classic drive letter — and how the owner expects it to appear. Rebuild the physical chain with a known-good data cable and a direct port, check the correct OS surface (Image Capture/Photos on Mac, This PC/Device Manager on Windows, and accessory approval on Apple silicon), and match your specific HERO model instead of applying one-size-fits-all menu advice.

When the goal is simply to retrieve footage, the card reader is the shortcut that ends the troubleshooting session in minutes. It removes the camera's USB stack from the equation and answers the diagnostic question immediately: if files appear in the reader, the card and footage are fine, and any remaining problem is isolated to camera-side USB.

Keep formatting as the absolute last resort and never before a backup. Work symptom-first, avoid the driver-download dead ends, and you'll either fix the connection or safely extract the footage regardless — with a reliable reader and a data-rated cable as the two pieces of gear that make the difference.

→ Check the SanDisk MobileMate card reader on Amazon