Most drone video is recorded in 10-bit HEVC (H.265), and that single fact is why so much beautiful footage ends up unwatchable when you send it to a client. The codec that makes your footage look great in the field is the same codec that produces a black screen in their browser. I have spent years watching drone operators capture stunning aerial video and then lose half the impact because the client could not open the file.
This post explains what the format actually is — the codec, the bit depth, the colour profile, and the resolution — and what each one means when your goal is to hand the footage to someone else.
What your drone is actually recording
When you pull a clip off a DJI (or Autel, or Skydio) drone, you are usually looking at three things bundled into one .mp4 or .mov file:
- Codec: how the video is compressed. Modern drones default to HEVC (H.265), the successor to H.264, because it stores the same quality in roughly half the file size.
- Bit depth: how many shades of colour per channel. Drones increasingly record 10-bit (over a billion colours) rather than 8-bit, to preserve detail in skies and shadows.
- Colour profile: often a flat “log” profile like D-Log or HLG, which looks washed-out straight off the drone but holds maximum dynamic range for grading.
Each of these is a sensible choice for capture and editing. Each of them is a problem for playback and sharing.
H.264 vs HEVC (H.265): the core trade-off
| H.264 (AVC) | HEVC (H.265) | |
|---|---|---|
| Compression efficiency | Good | ~50% smaller at equal quality |
| Browser playback | Universal | Spotty — limited and licence-dependent |
| Hardware decode support | Everywhere | Common at 8-bit, patchy at 10-bit |
| Editor compatibility | Universal | Often needs paid extensions / proxies |
| Best use | Delivery | Capture / archive |
HEVC is genuinely better compression — that is why drones use it. But “smaller file” is the wrong thing to optimise for when the file’s whole job is to be opened by someone else. H.264 is the lingua franca of video playback. It plays in every browser, on every phone, in every editor, with no extra software. For a deliverable, that universality beats compression every time.
The 10-bit problem (this is the one that bites)
Bit depth is the part people miss. Even where HEVC plays, 10-bit HEVC decoding is far less widely supported than 8-bit. Hardware decoders on many Intel, NVIDIA, and AMD chips handle 8-bit HEVC but fall back to slow software decoding — or fail outright — on 10-bit. The big exception is Apple Silicon, which decodes 10-bit HEVC efficiently. That is why a clip plays perfectly on your M-series MacBook and then stutters, shows a black screen, or refuses to import on your client’s Windows machine.
It is also why 10-bit HEVC is expensive to process. In our own pipeline, the difference is dramatic: an 8-bit H.264 clip transcodes in seconds, while a 10-bit HEVC clip of the same length can take far longer to decode on a standard cloud CPU. The footage is fine — it is the handling of 10-bit HEVC that is heavy.
Resolution: 4K, 1080p, and why 360 video is different
Resolution is the easy part, with one twist.
- 1080p is plenty for in-browser review of standard (flat) drone video. It plays smoothly anywhere and keeps file sizes sane.
- 4K is worth delivering when the client needs to scrub for fine detail (inspection, progress capture), but 4K H.264 is heavy to stream and not every device decodes it well.
- 360° video is the exception. An equirectangular 360 frame is wrapped around a sphere, so the viewer only ever sees a slice of it at once. A 360 clip delivered at 1080p looks like roughly 540p in the headset or viewport. 360 footage genuinely needs 4K (or higher) to look acceptable — it is the one case where you should not downscale aggressively.
So what should you actually do?
The practical workflow that avoids every problem above:
- Capture in whatever your drone does best — 10-bit HEVC, D-Log, 4K. Keep the original; it is your archive and your editing master.
- Deliver an 8-bit H.264 web rendition (1080p for flat footage, 4K for 360 or detail-critical work). This is the file your client actually watches.
- Don’t make the client transcode. Asking a surveyor’s client to install an HEVC codec pack is a great way to make your deliverable feel broken.
This is exactly what Swyvl does automatically. You upload the original drone file — HEVC, 10-bit, log profile, any resolution — and Swyvl transcodes a browser-friendly H.264 web version (and a 4K version for 360 video) so your client just opens a link and presses play. The original stays preserved and downloadable for anyone who wants the master.
Want to share drone footage that just plays? See how Swyvl delivers drone video to clients — branded links, in-browser playback, no codec installs.
The short version
Your drone records 10-bit HEVC because it is efficient and preserves dynamic range. That is the right choice for capture and the wrong choice for delivery: 10-bit HEVC is poorly supported in browsers, patchy in editors, and heavy to process. Capture in HEVC, deliver in H.264, keep 360 at 4K, and never make the client do the conversion. Get those four things right and your footage lands the way it looked when you shot it.