Short answer: use RTMP where an encoder is asked to publish to an ingest endpoint, WebRTC where the viewer interaction and real-time path justify it, and HLS where HTTP-based audience delivery is the selected path. A live service often uses more than one; the protocol names describe different boundaries.
Choose from the viewer back to the source
| Question | WebRTC | HLS | RTMP |
|---|---|---|---|
| Primary receiver | Interactive browser/application peer or media service | HTTP-capable player and delivery path | Ingest server or platform endpoint |
| Transport/delivery model | Real-time media session negotiated for the peers | Playlist plus media segments fetched over HTTP | Persistent TCP publishing session |
| Browser role | Designed for browser real-time media APIs | Delivered through a player path; platform support varies | Not native modern-browser playback |
| Codec check | Confirm browser, service and negotiation support | Confirm player, packaging and rendition compatibility | Confirm encoder and ingest endpoint compatibility |
| Network check | Signalling, ICE/STUN/TURN and firewall conditions | Origin, cache/CDN and player request behaviour | Reachability of the assigned ingest host and port |
| Fits when | Interaction is part of the product requirement | Audience delivery is the job | An encoder must hand a feed to an ingest receiver |
What to test first
| Workflow choice | Endpoint to test | First acceptance check |
|---|---|---|
| Interactive contribution or audience: WebRTC | A configured WebRTC viewer/session endpoint | Signalling plus ICE/TURN connectivity, then programme audio/video |
| Broad browser playback: HLS | https://example.invalid/live/master.m3u8 | Manifest fetch and the intended player rendition |
| Encoder/platform ingest: RTMP | rtmp://example.invalid/app plus assigned key | Publisher state, then the explicitly selected HLS or WebRTC output |
These are endpoint forms, not Callaba-provisioned addresses. For the underlying delivery models, see W3C WebRTC, IETF HLS, and the RTMP specification.
Quick decision: choose the protocol by job
For interactive contribution or audience participation, test WebRTC signalling and ICE/TURN before choosing it. For broad browser playback, test the HLS manifest and player. For encoder-to-platform ingest, test RTMP to the assigned endpoint, then select and test the downstream HLS or WebRTC output.
If the decision is “how do viewers receive the programme in a browser?”, start with WebRTC or HLS and their player, access and delivery requirements. If it is “how does this encoder publish to the platform?”, start with the platform's RTMP ingest contract. RTMP can feed a later HLS or WebRTC stage, but it does not itself create that stage.
Common false comparisons
WebRTC vs HLS
This is a delivery decision. WebRTC needs a real-time session path; HLS needs playlist/segment delivery and a compatible player. Test the exact audience endpoint and its access model rather than only the source feed.
RTMP vs WebRTC
These commonly occupy different ends of the workflow: RTMP as encoder ingest, WebRTC as interactive delivery. A bridge is a configured media-server or service function with its own codecs, signalling and operations—not a property of either URL.
HLS vs RTMP
HLS packages media for HTTP delivery; RTMP publishes media to an ingest receiver. A viewer who cannot open an RTMP URL needs the selected HLS or WebRTC output path, not a different browser.
A mixed workflow
A programme encoder can publish RTMP to a controlled ingest resource. The operator confirms source activity, then configures a separate output for audience delivery—HLS for an HTTP player workflow or WebRTC for the interaction path. Validate each boundary in sequence: encoder-to-ingest, processing/output creation, then the actual viewer URL.
Pre-production protocol checklist
- Write down source codec, frame rate, audio and target receiver constraints.
- Assign an owner to publish credentials, signalling/access and player testing.
- Use a private rehearsal audience and test a recovery after stopping the source.
- Keep direct browser-playback claims tied to the configured output, never the RTMP source URL.
Choose the next step
For encoder ingest and publisher/receiver access, see RTMP Server. An RTMP publish URL may use the same application and stream name as a receiver URL, but the publisher and receiver still have different roles. For browser output, start with Web Player guidance; for packaging intent, see RTMP to HLS. If the workflow is SRT contribution rather than RTMP publishing, the SRT Server is the appropriate owner.