Direct answer
Set a latency target, measure each stage, and remove avoidable queues while preserving enough jitter protection for the real network. Start with camera GOP and encoder buffering before blaming WebRTC.
Why this happens
A low-latency protocol cannot erase delay already created by the camera encoder, transcoder or an oversized player buffer. Each queue can also trade resilience for speed.
Browsers normally need a gateway that converts the camera feed into a web-native delivery path.
A controlled test
Use a visible time source or synchronized timestamp method to compare capture and display under normal and impaired network conditions.
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 |
|---|---|---|
| Camera | Measure encoder and keyframe behavior. | The source delay is known. |
| Gateway | Identify decode, transcode and queue time. | Passthrough and conversion costs are separated. |
| Network | Measure RTT, loss and jitter on the target path. | The jitter buffer is sized from evidence. |
| Browser | Measure render delay and recovery after loss. | The experience meets the stated target. |
Evidence to keep
Publish a latency budget table, not a single best-case number. Include device, codec, network condition and measurement method.
Boundary and safety note
Reducing every buffer to zero can create freezes and artifacts; the target is bounded latency with acceptable resilience.
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
Does WebRTC guarantee sub-second latency?
No. The camera encoder, gateway and network can consume the budget before the browser receives media.
What should I tune first?
Measure the camera GOP and gateway queues before reducing the browser jitter buffer.
Can passthrough reduce delay?
Yes, when the browser supports the source codec and packetization, because transcoding can be avoided.
Primary references
- IETF RFC 7826 — Real-Time Streaming Protocol 2.0
- W3C — WebRTC 1.0 specification
- FFmpeg — RTSP protocol options and examples
- IETF RFC 5905 — Network Time Protocol version 4
Related SmartRTSP guide
Open related guideBreak end-to-end delay into camera encoding, ingest, gateway, network, jitter and browser decode instead of tuning one buffer blindly.