Your DJI drone video won’t play because it is almost certainly recorded in 10-bit HEVC (H.265) — a codec that Windows does not decode out of the box and that many computer chips cannot decode in hardware. The file is fine. Your computer simply does not know how to read it.
This is one of the most common questions I hear from drone operators, and it is maddening precisely because the footage looks corrupt when it is not. I have spent years moving spatial and video data between machines, and the “it plays on my laptop but the client says it’s a black screen” problem comes up constantly. Let me explain exactly what is happening and how to fix it — first for you, and then, more importantly, for the client you need to send it to.
What codec is DJI drone video actually using?
Almost every current DJI drone — the Mavic 3, Air 3, Mini 4 Pro, Inspire 3, and the Matrice series — defaults to HEVC, also known as H.265. HEVC compresses roughly twice as efficiently as the older H.264, which is why DJI uses it: you get the same visual quality at half the file size, which matters a great deal when you are recording 4K or 5.1K footage onto a microSD card.
The complication is colour depth. Many DJI drones record in 10-bit HEVC (often in the D-Log or HLG colour profiles) rather than the more common 8-bit. Ten bits per channel gives you far more latitude for colour grading and better gradients in skies — genuinely useful for professional work. But it is also the single biggest reason your footage won’t play.
So the file your drone produces is typically:
- Container: MP4 or MOV
- Video codec: HEVC / H.265
- Colour depth: 10-bit
- Profile: Main 10
That “Main 10” profile is the troublemaker.
Why HEVC won’t play on Windows
There are two separate problems, and people constantly confuse them.
Problem 1: Windows has no HEVC codec by default
For licensing reasons, Microsoft does not bundle an HEVC decoder with Windows. HEVC is patent-encumbered, and the licence fees are why the decoder is a separate, paid add-on. When you double-click a DJI clip and Windows Media Player or the Films & TV app shows a black screen, a “codec missing” message, or plays audio with no picture, this is usually why.
The fix is the HEVC Video Extensions from the Microsoft Store — a small download, but one Microsoft charges around £0.79 / $0.99 for. (There is also a free “HEVC Video Extensions from Device Manufacturer” listing that surfaces intermittently and ships the same decoder; whether it appears for you depends on your hardware.)
Problem 2: Your chip may lack 10-bit HEVC hardware decode
This is the deeper problem, and it survives even after you install the codec. Modern video relies on hardware decoding — a dedicated block on your GPU or CPU that decodes the video stream efficiently and without draining the battery. When the hardware block does not support the exact profile your file uses, the system falls back to software decoding on the general-purpose CPU.
Software-decoding 10-bit 4K HEVC is brutally expensive. The result is the stuttering, dropped-frame, “one frame every two seconds” playback that people often mistake for a corrupt file. It plays — just unwatchably.
Many older or lower-tier chips support 8-bit HEVC in hardware but not 10-bit:
| Hardware | 8-bit HEVC decode | 10-bit HEVC decode |
|---|---|---|
| Intel UHD 600-series (Gemini Lake) | Yes | No |
| Intel 7th gen (Kaby Lake) and later | Yes | Yes |
| NVIDIA GTX 900-series | Partial | No |
| NVIDIA GTX 1000-series and later | Yes | Yes |
| AMD pre-Polaris GPUs | No | No |
| AMD Polaris (RX 400/500) and later | Yes | Yes |
| Apple Silicon (M1/M2/M3+) | Yes | Yes |
So a perfectly capable five-year-old office PC can choke on a clip that a brand-new phone plays without blinking.
Why it plays on a Mac but not a PC
This is the question that confuses people most: the same file plays fine on my MacBook but black-screens on the client’s PC.
The answer is straightforward. Apple Silicon Macs (M1, M2, M3 and later) have full 10-bit HEVC hardware decoding built into the chip, and macOS ships with the codec. There is nothing to install and nothing to pay for. The footage just plays.
That single fact explains the entire support headache. You edit on a Mac, everything works, you send the file to a Windows-based client, and on their machine it is a black rectangle. The file never changed. The decoding capability of the two machines did.
This is also why “it works on my computer” is worthless as a test for delivery. Your computer is not your client’s computer.
Quick fixes for your own machine
If you just need to watch or check your own footage, these are the fastest routes.
1. Open it in VLC
VLC bundles its own software HEVC decoder, so it ignores the Windows codec problem entirely. It is free, it is the single most reliable “just play the file” answer, and it is my first recommendation every time. The only caveat: if your hardware lacks 10-bit decode, VLC will software-decode and may stutter on high-resolution clips — but it will at least show you a picture.
2. Install the HEVC Video Extensions
If you want the file to play in the native Windows apps (Films & TV, Photos, Media Player), buy the HEVC Video Extensions from the Microsoft Store. This solves Problem 1. It does not solve Problem 2 — if your chip can’t hardware-decode 10-bit, you will still stutter.
3. Transcode to H.264
For maximum compatibility, convert the clip to H.264 (8-bit), which every machine made in the last fifteen years can play. Two reliable tools:
HandBrake (free, graphical): load the file, pick the “Fast 1080p30” preset, set the video codec to H.264 (x264), and encode.
ffmpeg (free, command line):
ffmpeg -i input.mp4 -c:v libx264 -crf 20 -pix_fmt yuv420p -c:a aac output.mp4
The -pix_fmt yuv420p flag forces 8-bit output, which is the part that guarantees universal playback. The trade-off is a larger file and a one-off processing wait, plus you have now made a second copy to manage.
Want to stop fighting codecs and just deliver footage clients can watch? See how Swyvl works for drone operators.
The real fix is delivery, not playback
Everything above solves your problem. None of it solves the problem that actually costs you time: your client cannot play the file either, and you cannot install VLC on their machine.
This is the distinction that matters. There is a difference between moving the file and delivering the data.
When you send a DJI clip over WeTransfer, Dropbox, Google Drive, or email, you are doing one thing: moving bytes from your drive to theirs. Those tools are storage and transfer. They do not decode anything. The client ends up with the exact same 10-bit HEVC file you started with, sitting in their Downloads folder, black-screening on the exact same Windows machine — except now you are the one fielding the “it doesn’t work” email.
| Generic file transfer | Browser delivery | |
|---|---|---|
| Gets the file to the client | Yes | Yes |
| Client needs the right codec | Yes | No |
| Client needs compatible hardware | Yes | No |
| Client installs software | Often (VLC, codec) | Never |
| Plays on any device | No | Yes |
| You handle the conversion | Manually, every time | Automatically |
A delivery platform closes this gap by handling the conversion for you and serving the video where it just plays: inside the client’s browser. The platform transcodes the 10-bit HEVC source into a web-standard stream the moment you upload, and the client opens a link and watches it — on Windows, on a Chromebook, on their phone — with nothing to install and no codec to buy.
You keep the original high-quality file for editing and archival. The client gets a version that plays. Neither of you thinks about HEVC again.
How this works in practice
When you upload DJI footage to a delivery platform built for spatial and drone media, the workflow looks like this:
- You upload the original clip — 10-bit HEVC, MOV or MP4, exactly as the drone produced it.
- The platform transcodes it to a browser-friendly stream automatically.
- You share a single branded link.
- The client clicks the link and the video plays inline in their browser.
- If they genuinely need the raw file for their own editing, the original is there to download.
No codec purchase. No HandBrake. No “can you re-send it as an MP4 that actually works.” The playback problem disappears because the file is being decoded on infrastructure you control and played back through the browser, which every device already has.
This is the same principle behind streaming a Cloud Optimized GeoTIFF on a map instead of making the client download a 3 GB orthomosaic — meet the client where they are, in the browser, with zero setup on their end.
Quick reference: diagnosing a DJI playback problem
| Symptom | Likely cause | Fastest fix |
|---|---|---|
| Black screen, audio plays | Missing HEVC decoder | Open in VLC |
| ”Codec not supported” error | No HEVC codec on Windows | Install HEVC Video Extensions |
| Plays but stutters badly | No 10-bit hardware decode | Transcode to H.264 |
| Plays on Mac, not on PC | Mac has built-in HEVC | Deliver via browser viewer |
| Client can’t open the file at all | Same HEVC issue on their machine | Deliver via browser viewer |
The bottom line
Your DJI drone video isn’t broken. It is 10-bit HEVC (H.265), and your computer — or your client’s computer — simply lacks the codec or the hardware to decode it. For your own viewing, VLC, the HEVC extension, or a quick H.264 transcode will get you a picture.
But for delivery, none of that scales. You cannot talk every client through installing a decoder, and you should not have to. The professional answer is to deliver the footage somewhere it just plays — a browser viewer that handles the conversion so the client installs nothing and sees the work you actually captured.
For a deeper look at the codecs and containers behind all of this, read Drone Video Formats Explained. And when you are ready to stop emailing clips that black-screen on the other end, see the best ways to share drone video.
Your footage is too good to arrive as a black screen.