Video is the heaviest cargo your radio spectrum carries, and the first thing customers judge your product by. The engineering question is never "which video system is best" — it's how much latency your mission tolerates, because latency tolerance determines cost, range and architecture.
Start from latency, not resolution
| Use case | Latency budget (glass-to-glass) | Sane architecture |
|---|---|---|
| Manual FPV / acro piloting | < 40 ms | Analog or low-latency digital FPV |
| Teleoperated inspection / precision work | < 150 ms | Digital FPV or good IP link |
| Observer / payload operator feed | < 300 ms | IP link, LTE acceptable |
| Remote monitoring, streaming to cloud | < 1 s | LTE/5G + WebRTC/SRT |
The three families
Analog FPV: the cockroach of video links
NTSC/PAL over 5.8 GHz FM. Terrible picture, ~25 ms latency, and a failure mode that degrades gracefully — static creeps in, but the image never freezes. Cheap, tiny, unkillable; still respectable as a pilot's backup eye on aircraft where the primary link is digital. Not a product-grade customer feed.
Digital FPV systems
Purpose-built digital video (DJI O3/O4-class, HDZero, Walksnail): HD quality at 21–40 ms, integrated ecosystems, consumer pricing. Caveats for commercial builds: closed ecosystems with limited integration hooks, consumer-band power limits (see spectrum rules), and freeze-style failure at the edge of coverage. Excellent for piloted operations; awkward as a systems component.
IP / COFDM links: the professional default
Video as network traffic over a broadband modem (COFDM microwave, mesh radios, or LTE/5G). H.264/H.265 encoded — natively or on the companion computer — with AES encryption, multiplexed C2 and data, non-line-of-sight resilience, and clean integration into GCS software, recording and cloud. Latency 80–300 ms depending on stack; prices from hundreds (LTE) to many thousands (broadcast COFDM). For most commercial UAV products, this is the answer, with the interesting choices inside it:
- Encoder placement: camera-native encoding saves companion CPU; companion encoding gives overlay/AI-annotation freedom.
- Codec: H.265 halves bitrate for the same quality vs H.264, at more encode cost and licensing footnotes; AV1 is arriving via newer silicon.
- Transport: RTSP for local GCS, WebRTC for browser-latency remote ops, SRT for lossy backhaul to infrastructure. Adaptive bitrate is non-negotiable over cellular.
Bandwidth arithmetic you'll use weekly
1080p30 H.264, inspection quality: 4–8 Mbps
1080p30 H.265, same quality: 2–4 Mbps
4K30 H.265: 8–16 Mbps
Thermal 640×512 + metadata: 0.5–2 MbpsCompare against honest link throughput at range (not the brochure's ideal), then leave half the channel free — a video link saturating its radio starves everything sharing it and collapses ugly instead of degrading pretty.
Integration gotchas that cost weeks
- RF fratricide: a video transmitter is the loudest emitter aboard — placed near a GNSS antenna it degrades fixes; near the C2 receiver it deafens it. Separate bands, separate ends of the airframe, test with everything transmitting at once.
- Thermal: multi-watt transmitters and encoders throttle in sealed bays; throttling mid-mission looks like "random pixelation" tickets.
- Recording is not streaming: record full quality onboard, stream what the link affords. Customers forgive a choppy live feed; they don't forgive missing evidence of the defect they flew to find.
- Time sync: stamp frames against aircraft time (PPS/UTC) or your inspection data can't be georeferenced later — a payload integration detail that's cheap on day one and expensive on day 400.
Primary: IP video over your broadband link, encoded on the companion, encrypted, adaptive. Optional: low-latency FPV eye for the pilot where manual flight is part of operations. Always: onboard recording, honest bandwidth budget, RF coexistence tested. This pattern survives payload changes, link upgrades and BVLOS ambitions without redesign.
Frequently asked questions
What video latency does a drone application actually need?
Manual FPV piloting wants under ~40 ms glass-to-glass. Teleoperated inspection is comfortable below ~150 ms. Situational awareness and observer feeds tolerate 200–500 ms. Every requirement you relax below 'FPV pilot' opens cheaper, longer-range options.
Why do professional drones use IP video links?
IP links (often COFDM-based) integrate with networks, encrypt cleanly (AES), multiplex video with C2 and payload data, and handle non-line-of-sight conditions better. The cost is higher latency than dedicated FPV systems and a higher price.
How can I stream drone video over 4G/5G?
Encode H.264/H.265 on a companion computer and stream via RTSP/WebRTC/SRT over an LTE modem. Latency of 200–600 ms is typical; use adaptive bitrate, and treat coverage and data cost as mission-planning constraints. This is standard for BVLOS and remote-operations architectures.