DaVinci Resolve GoPro Hero 12 Footage Won't Import: The Fix

Which HERO12 recording mode were you shooting in when the clip failed?

This single question eliminates most of the branches on this page immediately. Not every HERO12 recording produces the file type that causes the most common import failure.

According to GoPro's own HERO12 Black specs page, the camera records "H.265 (HEVC)" as its compression standard, offers a choice of "standard 8-bit recording and 10-bit (4K and higher)," supports resolutions up to "5.3K (16:9) 60fps" and "4K (16:9) 120/100/60/50/30/25/24 fps," and includes both an "HDR Video" mode at select frame rates and "GP-Log encoding with LUT" for advanced grading.

A HERO12 shooting Standard color at 4K and a HERO12 shooting GP-Log at 4K aren't recording the same kind of file with a different look. Once you cross into 10-bit, you've changed codecs in every way that matters to a decoder, even though the file extension stays identical. Standard 8-bit HEVC decodes almost everywhere. 10-bit HEVC from GP-Log or HDR needs real decoder support that Resolve's free Windows build frequently doesn't provide out of the box.

If your rejected clip was shot in Standard color at 2.7K or 1080p, the 10-bit wall covered in the next two sections almost certainly isn't your problem. Skip ahead to the chaptering, sidecar file, or recovery sections instead. If you had GP-Log or HDR switched on, or manually set 10-bit color at 4K or 5.3K, keep reading, because you've likely found your cause.

Why does 10-bit HEVC from GP-Log or HDR fail to import on Windows?

This is the wall that generates the most confused forum posts, and it's almost entirely a free-version, Windows-specific problem rather than a bug in your footage.

The root cause is bit depth stacked on top of codec, the same combination that trips up 10-bit HEVC from recent iPhones and DJI drone footage. Writer Robin Parmar, covering exactly this limitation in Resolve's free tier, put it plainly: "Resolve (free) restricts you to 8-bit colour," he wrote in a breakdown of Resolve's codec limitations, even when a 10-bit intermediate file sits directly in the timeline. That restriction bites hardest on Windows, where the operating system doesn't ship a built-in HEVC decoder at all, layering a missing system decoder on top of a free-tier color depth ceiling.

Editor Brady Betzel, reviewing the HERO12 for postPerspective, tested the camera's footage directly inside Resolve and noted the codec choice matters in practice, not just on paper: "As I was working with the GoPro Hero12 Black footage in Blackmagic's DaVinci Resolve 18.6.5, I was monitoring the footage on a large OLED monitor through a Blackmagic DeckLink 4K Extreme over HDMI," he wrote in his hands-on review, a workflow that assumes the footage decoded and played cleanly in the first place, something not every Windows machine can promise without the right decoder installed.

1. Check MediaInfo's Bit depth field on the rejected clip. If it reads 10-bit, this is very likely your cause.
2. If you're on Windows and haven't installed the HEVC Video Extensions from the Microsoft Store, do that first and restart your PC completely, not just Resolve.
3. If the extension is already installed and the clip still fails, move to the next section, since you've hit a second, separate wall.

Why does the same clip still fail after you install the HEVC extension?

Here's the part that trips up people who did everything right and are still stuck. Installing the Windows HEVC extension isn't the end of this road, it's the halfway point.

The extension buys you standard, 8-bit HEVC decoding. Whether 10-bit HEVC decodes cleanly on top of that depends on your specific GPU generation and driver version, exactly the kind of variable that makes this problem inconsistent between two people running what looks like an identical setup on paper.

Installing the HEVC extension and still getting rejected on the exact same codec isn't a sign the extension failed. It's a sign you've hit a second wall stacked directly behind the first one. Standard HEVC decoding and 10-bit HEVC decoding are not the same capability, and having one doesn't guarantee the other on a given Windows machine.

Three real paths through it once 10-bit is confirmed as the cause:

1. Edit on a Mac instead, where the free version of Resolve doesn't carry the same Windows-specific HEVC limitation, since macOS ships system-level HEVC decoding Windows doesn't.
2. Upgrade to Resolve Studio, which includes broader native HEVC decoding across the pipeline, 10-bit included, on supported systems.
3. Transcode before you import, converting the clip to DNxHR or ProRes with a free tool like Shutter Encoder, sidestepping the GPU-dependent HEVC decode path entirely and handing Resolve a codec it never struggles with.

If you'd rather avoid this fight after the fact, and you're editing on a Windows machine without the HEVC extension or a Studio license, shoot Standard color instead of GP-Log or HDR for anything time-sensitive. You'll lose some dynamic range you could have graded back in later. You'll also never see this specific rejection on that footage.

Why did your HERO12 clip split into two files with GX01 and GX02 in the name?

If your clip imported fine, decoded fine, and plays fine, but a long recording shows up as two or three separate files instead of one continuous clip, you haven't hit a Resolve problem at all. This one happened entirely on the camera, before Resolve ever saw the footage.

GoPro calls this File Chaptering, and GoPro's own file naming documentation lays out the exact pattern: files follow a GXzzxxxx.MP4 or GHzzxxxx.MP4 structure, where xxxx is the file number shared across chapters and zz is the chapter number that increments first. A recording that splits twice produces GX010123.MP4 followed by GX020123.MP4, both belonging to the same underlying clip.

This is where HERO12 genuinely differs from older GoPros and from most drones. Have Camera Will Travel's breakdown of GoPro's chaptering behavior explains that for years the ceiling was 4GB per chapter, a limit tied to the FAT32 filesystem many small SD cards used. With the release of the HERO11, HERO12, and HERO13, GoPro raised that native ceiling to roughly 12GB per chapter, well past what most single clips ever reach. A ten-minute 5.3K60 recording that would have split three times on a HERO9 often finishes as one unbroken file on a HERO12. Long enough recordings, particularly at the highest bitrate settings, will still eventually cross even the higher 12GB line and chapter exactly the way older cameras did.

A chaptered recording isn't two clips. It's one clip that hit an internal size ceiling the camera can't see past, then kept recording into a new file without missing a frame. The footage itself isn't damaged and nothing was lost between chapters. Resolve just sees each numbered chapter as a separate clip, because as far as the file structure is concerned, they are.

To handle a chaptered recording in Resolve:

1. Import every chapter from that recording into the same bin. Resolve will not detect or rejoin them for you.
2. Place the chapters in sequence on the timeline, lowest chapter number first. They should cut together with no visible gap if the split happened cleanly.
3. If you need one continuous file for a client delivery or an external tool, join them at the file level first with a lossless tool like FFmpeg's concat demuxer before you import, rather than trying to force Resolve to treat two files as one clip.

What are the .LRV and .THM files sitting next to every GoPro clip?

If you've browsed your HERO12's DCIM folder directly instead of importing through the Quik app, you've probably noticed a much smaller file sitting next to each real clip, sharing the same file number with a different extension. Neither of these is a second angle or a backup copy.

Author Max Hayman, explaining exactly what these files do, writes that LRV stands for "low-resolution video," a reduced-quality copy the camera builds automatically alongside every recording. In his breakdown of the format, he explains why the camera bothers creating it at all: "streaming a video this large from your GoPro onto your phone will is limited by the WiFi connection between the two devices, and it'll also burden the phone's CPU," so GoPro's Quik app previews the small LRV file over Wi-Fi instead of pulling the full original. THM is simpler still, a single 160x120 thumbnail JPEG used for gallery previews and loaded instantly instead of decoding a frame from the real video every time you scroll past a clip.

An LRV file next to your GoPro clip is a phone-app preview copy, not a video Resolve needs, and a THM file is a thumbnail image, not a second recording. Neither belongs on your timeline. Hayman is direct about this for anyone editing rather than just browsing on a phone: "if you are going to view your footage only on your PC, or edit your GoPro footage with a video editing software like Premiere Pro or DaVinci Resolve, you may not require the .LRV and .THM files."

You can't disable GoPro from writing them in the first place, and they take up minimal card space, so there's no real reason to delete them either. Just import the .MP4 files into your Media Pool and ignore the rest of the folder. If Resolve's file browser shows the LRV or THM files at all, they'll typically appear with no thumbnail or a broken one, since Resolve isn't built to decode either format as video.

What does a "recovered" or corrupted GoPro file actually mean, and can you fix it?

If a clip imports but looks glitchy, freezes partway through, or won't play past a certain point in VLC either, you're not looking at a codec gap. You're looking at genuine file damage, usually from the recording getting cut off before the camera finished writing it.

HERO12, like other GoPros, watches for this on its own. When the camera boots up and detects a file with damaged or incomplete metadata, most commonly caused by a battery dying mid-recording or a card pulled before the file finished writing its index, it shows a recovery icon on the LCD screen. Pressing any button on the camera triggers an automatic attempt to rebuild the file's structure, with the camera's red status light blinking while it works. EaseUS's guide to repairing corrupted GoPro files confirms this on-camera process handles common, moderate corruption reasonably well, rebuilding the file header, technically the MP4's moov atom, that players and editors need to read the file at all.

GoPro's on-camera recovery fixes a broken index, not missing footage. If the actual video data got overwritten or never finished writing, no recovery tool brings back frames that were never recorded. That's the honest limitation worth knowing before you spend an hour on a file that was never going to come back. GoPro's own support material and third-party repair guides both frame this the same way: recovery works well for minor disruptions, and it isn't guaranteed for severe corruption.

If a clip is still glitchy after on-camera recovery, or you've already copied the file to your computer and can't run the camera's recovery process on it directly:

1. Try opening the file in VLC first. VLC's decoder is more forgiving of minor structural damage than Resolve's, and it will often at least partially play a file Resolve refuses entirely.
2. If VLC plays it, even partially, that confirms real video data survived, and a targeted repair tool built for MP4 recovery is worth trying before you give up on the clip.
3. If VLC also refuses or the file plays only silence or a black frame the whole way through, the footage is very likely unrecoverable, and no amount of transcoding or re-encoding brings back data that isn't there.

Why does GP-Log or HDR footage import fine but look grey, flat, or oddly colored?

This one isn't an import failure at all, even though it feels exactly like one the first time you see it. The clip opened. It plays. It just looks wrong, and that's actually expected.

GP-Log is a logarithmic color profile, and by design it compresses contrast and saturation into a flat, low-punch image so the file protects more highlight and shadow detail for you to pull back out later in the Color page. A GP-Log clip that looks vivid and contrasty straight off the card would mean the camera threw away dynamic range you'd never get back, the opposite of the point.

Here's where GoPro footage genuinely differs from footage shot on some cinema cameras: DaVinci Resolve doesn't ship a labeled, built-in "GP-Log" preset inside its Color Space Transform effect or its Resolve Color Management camera list, the way it does for several other manufacturers. A Blackmagic Design forum discussion on color managed workflows and GoPro footage confirms the practical workaround editors land on: shooting GoPro in Protune Flat or GP-Log and letting Resolve's color management transform it toward Rec.709 preserves more usable dynamic range than starting from GoPro's baked-in Standard or Vivid color, even without a camera-specific preset doing the conversion automatically.

Your options for getting from flat GP-Log to a normal-looking starting point:

1. Use a third-party GoPro-specific transform, such as the GP-Tune DCTL, built specifically to convert GP-Log, GP-Log2, and Protune Flat footage into Resolve's working color space with the correct math for GoPro's actual sensor response, not a generic Log curve.
2. Apply GoPro's own downloadable LUT as a starting-point look on the node, treating it the way you'd treat any creative LUT rather than a precise color space conversion.
3. Build a manual Color Space Transform, setting the Input Color Space and Gamma to the closest match Resolve offers and adjusting from there by eye, the least precise option but one that needs no extra install.

GP-Log footage that looks grey and flat right after import isn't broken, and it isn't a sign anything failed. It's raw material waiting for the color step you haven't done yet. The same logic applies to HDR mode footage, though HDR carries its own display considerations on top of the color question, since it's built to be viewed on an HDR-capable screen at full brightness range rather than graded down to a standard Rec.709 delivery by default.

Why does a HERO12 clip show Media Offline instead of importing at all?

If the codec checks out, the file isn't chaptered, and it isn't flagged for recovery, but the clip is still red inside Resolve, you're looking at a broken link between Resolve and the actual bytes on disk, not a decoding rejection.

A handful of causes account for most of these. A failing or cheap microSD card reader is the most common: 5.3K60 footage at HERO12's higher bitrates needs a reliable, fast connection, and a marginal reader or a worn USB port can drop bytes mid-copy without throwing any visible error, leaving a file that looks the right size in Finder or Explorer but is actually incomplete. An interrupted transfer through the Quik app over Wi-Fi, closing the app or losing the connection mid-download, can leave a partial file with a completely normal-looking filename and no obvious sign anything went wrong until Resolve actually tries to decode it. A renamed or moved project folder breaks the link between Resolve's project database and the file path it originally recorded, entirely separate from anything wrong with the footage itself.

To rule this out, check the file's exact byte size on the source card against the copy on your editing machine. If they don't match, or you're not certain, re-copy the file rather than trying to relink Resolve to a copy that was already incomplete. If the file plays fine in VLC but still shows offline specifically inside Resolve, right-click the red clip and try Relink, pointing it explicitly at the file. Our full guide to DaVinci Resolve's Media Offline error covers the general relink workflow and render cache side of this problem in more depth if none of the GoPro-specific causes above match what you're seeing.

How does HERO12 compare to HERO11, HERO13, and older GoPros for this exact problem?

Knowing where HERO12 sits in GoPro's own lineup tells you whether a fix you found in an old forum thread even applies to your camera.

Have Camera Will Travel's dedicated breakdown of GoPro's HEVC-versus-H.264 shift confirms the pattern directly: starting with the HERO11 generation, GoPro moved to HEVC as the default codec across nearly every mode, with H.264 surviving only as a fallback at lower resolutions and frame rates rather than a free choice in every setting. A GoPro Labs GitHub discussion asking specifically whether HERO12 can be forced into H.264 got a blunt answer from GoPro engineer David Newman: "There is no Labs hack for this." If you're chasing a fix built around switching HERO12 to H.264 the way older cameras allowed at any resolution, that specific workaround doesn't exist on this camera outside of dropping to 1080p60 or below.

If you're editing HERO11, HERO12, or HERO13 footage, you're dealing with a fundamentally HEVC-first camera, and every fix on this page assumes that starting point. If you're troubleshooting a HERO10 or earlier and landed here by search, the 10-bit wall almost certainly isn't your issue, since those cameras don't offer a 10-bit recording mode at all. Check your model's actual codec ceiling before spending time on a fix built for a different generation.

What does the full fix look like on a real shoot, start to finish?

Here's the full diagnosis applied to a situation that comes up constantly: a travel vlogger shoots a forty-minute hike on a HERO12 in GP-Log for a punchier grade later, then imports everything into a Resolve project on a Windows laptop that evening.

First, import fails outright on four of the six clips, with no error message, just silence in the import dialog. MediaInfo confirms all four are HEVC, and the Bit depth field reads 10-bit. The other two clips, a short test recording shot earlier in Standard color, imported without any issue.

Second, the Windows HEVC extension is already installed and has handled other HEVC footage before. That rules out the most common single cause immediately, pointing straight at the 10-bit wall rather than a missing decoder entirely.

Third, rather than gamble on an uncertain GPU driver fix mid-edit, the vlogger runs the four GP-Log clips through Shutter Encoder, converting to DNxHR HQ, which preserves the 10-bit color depth intact for later grading rather than flattening to 8-bit and losing the dynamic range the whole point of shooting Log was meant to capture.

Fourth, one of the converted clips turns out to be the second chapter of a longer recording, GX010045.MP4 followed by GX020045.MP4, both importing fine individually and cutting together seamlessly once placed in sequence on the timeline.

Fifth, a fifth clip that looked fine on the camera's own screen plays with a brief visual glitch about two minutes in, right where the vlogger remembers the battery indicator flashing low. Running it through VLC confirms the glitch, not a total failure, and the clip is usable once trimmed around the damaged section rather than discarded entirely.

Sixth, everything imports clean, sits at consistent color depth across the project, and a Color Space Transform node built with a GoPro-specific DCTL brings the flat GP-Log clips to a normal-looking starting point that grades against the two Standard-color clips without a fight.

Does the free version of Resolve handle HERO12 footage differently than Studio?

Yes, and it's worth knowing exactly where that line sits before you assume an upgrade fixes something it won't touch, or skip an upgrade that would have solved your actual problem in one step.

On Windows, the practical gap is 10-bit HEVC, exactly as covered above. Free Resolve needs the Microsoft Store extension for standard HEVC, and even with it installed, 10-bit decoding from GP-Log or HDR can still depend on your specific GPU and driver combination in ways that vary machine to machine. Blackmagic Design's own tech specs page and its Supported Codec List document draw a clear line between free and Studio decode capability that carries directly into how reliably each version handles GoPro's heavier codec modes. Studio includes broader native HEVC handling across the pipeline, 10-bit included, a genuine, practical difference if you regularly shoot GP-Log or HDR for grading rather than delivering straight out of Standard color.

On Mac, this specific wall mostly doesn't exist. macOS ships system-level HEVC decoding that Windows doesn't, so the free version handles GP-Log and HDR footage far more reliably out of the box, without needing an extension install or a Studio upgrade at all.

On Linux, the gap is different and bigger: Blackmagic's free Linux build doesn't decode H.264 or HEVC in any container, a licensing decision entirely separate from bit depth. That restriction hits HERO12 footage exactly as hard as it hits any other H.264 or HEVC source, since it's about the codec itself rather than which camera recorded it.

Chaptering, LRV and THM sidecar files, and on-camera file recovery don't change with your Resolve license at all. Those are camera, card, and file-structure issues that play out identically whether you're on free Resolve or Studio, on Windows, Mac, or Linux. Match the fix to the actual cause, not to whichever upgrade happens to be for sale.

How do you avoid this before your next shoot?

A short list of habits catches nearly everything on this page before it turns into an editing-day problem.

• Know your camera's actual codec behavior before you shoot. On HERO12, GP-Log and HDR mean 10-bit HEVC, full stop, and Standard color at 4K or 5.3K usually stays 8-bit unless you manually changed it. Check which one is active before a shoot that matters, not after you're staring at a rejected import that evening.
• Keep the Windows HEVC extension installed proactively if you shoot Log or HDR regularly, and know that it alone may not clear 10-bit content on every GPU, so have a transcode workflow ready as a fallback rather than discovering you need one mid-project.
• Charge the battery fully before any recording you can't easily reshoot. A dying battery mid-record is the single most common trigger for the file-recovery scenario covered above, and it's the easiest one to prevent entirely.
• Ignore the .LRV and .THM files unless you're specifically working inside the Quik phone app. Their presence in the folder is expected, not a sign something's wrong or missing.
• For very long single recordings at high bitrate, expect chaptering even on HERO12. The 12GB ceiling is far more forgiving than the old 4GB limit, but it still exists, and importing every chapter from a long take is still the correct workflow, not a workaround for a bug.

What if you're new to Resolve and action camera footage is your first hardware wall?

If codec extensions, bit depth, and file chaptering feel like a lot to sort through on top of just learning where things live in DaVinci Resolve, that's a normal place to land. Action camera footage trips up experienced editors too, mostly because the failure modes above sit at the intersection of camera firmware, SD card handling, and Resolve's own codec licensing, three systems that don't talk to each other or share documentation.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS, ask in plain words and Uncle points at the exact control on your screen. Instead of leaving Resolve to hunt through a forum thread written by someone troubleshooting a different GoPro generation on a different operating system, Uncle watches your actual Resolve window and points at the specific menu or setting your footage needs. TryUncle isn't the only AI tool built around Resolve either. Tools like Sottocut, PremiereCopilot, and cutagent.ai automate specific editing tasks such as rough cuts or timeline assembly, and chat-based assistants like heyeddie.ai answer Resolve questions in a separate window disconnected from your actual project. TryUncle's approach is different: it watches your live Resolve session and points at the real control on your screen, rather than automating the edit for you or answering blind in a chat box. It's a paid macOS app on founder pricing, currently $29.99 a month for the first 100 seats, not a free tool, and it's built to guide you while you work in Resolve rather than replace the work. Check TryUncle for current pricing if guided, on-screen help sounds like the faster path through your next action-camera import wall.

What's the fastest path to a fix?

Check MediaInfo first. If the rejected clip reads 10-bit HEVC, and you were shooting GP-Log or HDR mode, that's your cause. Install the Windows HEVC extension if you haven't, restart your PC, and retry. If it still fails, transcode to DNxHR or ProRes, edit on a Mac, or move to Studio.

If instead you're looking at two files sharing a number but different chapter prefixes, like GX010123.MP4 and GX020123.MP4, that's HERO12's own chaptering behavior, not a Resolve problem, and both chapters need importing since Resolve won't rejoin them for you. If a tiny extra file with an .LRV or .THM extension is sitting next to your real clip, that's a phone-app preview or a thumbnail, not a second video, and it's safe to leave alone. If a clip glitches or freezes partway through, check whether the camera flagged it for recovery after a low battery, and know that on-camera recovery fixes a broken file header, not footage that never got recorded. If a clip imports fine but looks grey and flat, that's GP-Log doing exactly what it's designed to do, and it's a color step away, not an import problem at all.

Nine times out of ten, your HERO12 footage isn't broken, and Resolve isn't malfunctioning. Either your Windows machine is missing a real 10-bit decode path, the camera drew a chaptering line its firmware had to respect, or the footage needs a repair pass, a color transform, or a different transfer method rather than another hour of drag-and-drop guessing. Match the exact symptom to the exact cause, and the fix is almost always a single extension, a single transcode, or a five-minute color node, not a lost afternoon.