Want the measured numbers first? Read the Matrice 4E bench test: real codec, real bitrate, real setup.
The built-in sharing in DJI Fly and DJI Pilot 2 streams to social platforms, or into DJI's own ecosystem. That works for a public audience on those platforms, but it doesn't give you the thing a client or a team usually wants: a plain web page they can open, private to them, with the live picture on it. The feed otherwise stays on your controller.
Both apps can push the live feed to any RTMP address you give them. That single field is the bridge to the web: enter the RTMP URL of a relay service, and the relay takes the stream in and serves it back out as a web page. The path is the same for the consumer line (Mini, Air, Mavic, Neo, Flip via DJI Fly) and the enterprise line (Matrice and Mavic Enterprise via DJI Pilot 2).
With Hover the flow looks like this:
No OBS, no streaming PC, no port forwarding, and nothing for the viewer to install. The connection is outbound from the app, so it works from the field over a hotspot, LTE, or Starlink.
You can build this yourself: rent a server, run an RTMP ingest (nginx-rtmp or MediaMTX), transcode to something browsers play, put a player page in front of it, and keep all of it patched and running. It genuinely works, and if you enjoy running infrastructure it's a fine weekend project. The tradeoffs are the ongoing ones: the server bill, the maintenance, no access control unless you build it, and no recording unless you build that too. A managed relay exists so the stream is just a link.
One thing we learned on the bench: the app's quality labels understate what actually leaves your controller. On a Matrice 4E, the "1.5M" setting sustained 9.5 to 14 Mbps of real upstream traffic. The stream is H.264, 720p in our tests, video only. Provision your data plan and check your signal for the higher figure; the full bench test has the measurements.
A browser page with the live picture and telemetry, gated by a PIN you control. It holds up over field networks, and the flight records to the cloud so the client can rewatch it, without per-gigabyte storage fees. If you fly for clients, that page is a deliverable: Hover for certified drone operators covers that angle.
Not by itself. DJI's apps stream to social platforms or to DJI's own ecosystem, and the drone's feed otherwise stays on the controller. The bridge is the custom RTMP option in DJI Fly and DJI Pilot 2: point it at a relay service and the relay turns the stream into a web page anyone with the link can open.
No. The RTMP stream goes straight from the DJI app over the controller's internet connection to the relay. There is no capture software, no streaming PC, and nothing to install on the viewer's side; they open a link in a browser.
Any drone flown with an app that has custom RTMP. DJI Fly covers the consumer line (Mini, Air, Mavic, Neo, Flip) and DJI Pilot 2 covers the enterprise line (Matrice and Mavic Enterprise). We bench-verified the flow on a Matrice 4E.
Budget for more than the app's label suggests. On our Matrice 4E bench test, the "1.5M" quality setting sustained 9.5 to 14 Mbps of real upstream traffic. A solid LTE connection handles it; plan your data and signal for the higher figure.
That's up to the relay you use. Hover gives each stream a private viewer page gated by a PIN, so you share the link and PIN with your client or team and nobody else can watch. Recording to the cloud is included.
Yes; that's the normal case. The stream leaves the controller over whatever internet it has: a phone hotspot, LTE, or Starlink. No port forwarding or fixed IP is needed because the connection is outbound from the app to the relay.