Direct answer
Treat the camera RTSP feed as an ingest protocol and place an authorized gateway between the camera network and browser clients. Choose WebRTC for interactive latency or HLS for scalable buffered delivery.
Why this happens
Modern browser media stacks do not generally expose a raw RTSP player. A gateway must handle camera authentication, codec compatibility, session fan-out and a web-native transport.
Browsers normally need a gateway that converts the camera feed into a web-native delivery path.
A controlled test
Draw the ingest, gateway, browser and authentication boundaries before selecting software.
Change one variable at a time. Keep the camera model, firmware, endpoint and account recorded; then test network reachability, protocol response, media transport and decoding as separate layers.
Use a dedicated view-only account and a trusted local diagnostic tool. Redact credentials, private addresses and identifying data before sharing output.
Diagnostic sequence
| Check | Action | Evidence of progress |
|---|---|---|
| Latency | Define the maximum glass-to-glass delay. | The target points to WebRTC, HLS or another delivery mode. |
| Scale | Estimate concurrent viewers and camera fan-out. | One camera is not opened once per browser without a plan. |
| Codec | Match camera output to browser decode support. | Passthrough or transcoding is chosen deliberately. |
| Trust | Keep camera credentials at the gateway. | Browsers receive scoped access, not camera passwords. |
Evidence to keep
The architecture record should name who terminates RTSP, who authenticates viewers, whether video is transcoded and where buffers add latency.
Boundary and safety note
Never put a credential-bearing private RTSP URL into client-side JavaScript or a public online player.
For remote viewing, use a managed VPN instead of exposing RTSP or camera administration ports directly to the public internet.
SmartRTSP
SmartRTSP is a camera-focused RTSP and ONVIF viewer for Apple devices, Windows and Android. It fits direct viewing, discovery and multi-camera checks; keep a dedicated NVR or VMS when continuous recording, evidence export or centralized enterprise controls are required.
Frequently asked questions
Can Chrome or Safari open rtsp:// directly?
Do not design around direct raw RTSP playback; use a controlled gateway and a web-native delivery path.
When should I choose WebRTC?
When interactive or operational viewing needs low latency and the added session infrastructure is acceptable.
When is HLS a better fit?
When broad HTTP delivery, caching and tolerance for segment-based latency matter more than interactivity.
Primary references
- IETF RFC 7826 — Real-Time Streaming Protocol 2.0
- W3C — WebRTC 1.0 specification
- IETF RFC 8216 — HTTP Live Streaming
- MDN — Media container and codec formats on the web
Related SmartRTSP guide
Open related guideChoose WebRTC, HLS or another web-native output instead of expecting a browser to open a camera RTSP URL directly.