RTSP to WebRTC is the step that turns a camera's RTSP stream into live video any modern browser can play. It is one chapter of video streaming protocols.
Why browsers cannot play RTSP
Browsers cannot play RTSP, the protocol most IP cameras use to send video. To watch a camera live in a browser, the video has to be repackaged as WebRTC, which every modern browser plays. Done well, this adds almost no delay. Visylix does it inside its own streaming engine, so live view arrives in under a second.
RTSP (Real Time Streaming Protocol) is the language almost every IP camera speaks. It has carried camera video for more than two decades. But no modern web browser can play it. Viewing RTSP has always meant special software, plugins or VPN tunnels.
Operators now expect something simpler: open a dashboard in Chrome or Edge and see every camera live, straight away, with nothing to install. WebRTC is the browser technology that makes that possible. Turning RTSP into WebRTC, quickly and at scale, has become one of the most important jobs a modern video management system does.
RTSP carries the control commands and RTP carries the video itself; what is RTSP explains both.
What happens between the camera and the screen
The video management system connects to the camera over RTSP and receives its compressed video, usually H.264 or H.265. It then repackages that video for WebRTC. The server and browser agree how to talk, find a network path to each other and set up encryption, and the first frame appears.
Each step adds a little delay. The best designs avoid the slowest step of all, converting the video into a new format, by passing the camera's own video straight through. They also keep camera connections open in advance and set up the browser connection in parallel, so a feed opens almost instantly.
WHEP is the standard way for a browser to ask for a WebRTC stream; the handshake is covered in WebRTC signaling server.
WHEP has a sister standard for the other direction. WHIP, published as RFC 9725 in March 2025, is a simple HTTP way to send WebRTC video into a streaming service (RFC 9725). Visylix supports both.
Doing it yourself: the common shortcuts and where they break
There are three common shortcuts, and each breaks at scale. A small conversion tool per camera falls over as cameras grow. Sending HLS adds several seconds of delay. Decoding and encoding every stream burns CPU. Visylix pulls each camera once and shares that feed with live view, recording and AI, so nothing is decoded twice.
The usual shortcut is to place a general purpose conversion tool, such as FFmpeg, between camera and browser. It unpacks every stream and packs it again in a browser friendly format. That works for a handful of cameras. Across a real estate the processing cost becomes huge, and many systems end up needing extra servers just for conversion.
Another route is an open source media server, such as Janus or MediaMTX, in the middle. These can pass video through without conversion. But you then run, secure and update a second system beside your video platform, and you still need recording, search and alerts elsewhere.
Falling back to HLS trades the problem for delay; see HLS vs WebRTC.
Codecs: H.264 and H.265 in the browser
Every modern browser plays H.264. H.265 is patchier, and whether a browser can play it over WebRTC depends on the browser and the device. A good platform passes each camera's video through untouched wherever the browser can play it. It converts H.265 to H.264 only for the browsers that need it. HEVC vs H.264 explains the two codecs.
The baseline is fixed by the standards. WebRTC browsers must implement VP8 and H.264 Constrained Baseline (RFC 7742). That profile has no B-frames, which some cameras use to save bandwidth.
So a camera sending H.264 with B-frames also needs converting before a browser will play it over WebRTC. Visylix does that on the CPU, for that one stream only. Recording always keeps the camera's original video.
Getting through firewalls and NAT
Most cameras and viewers sit behind routers that hide their real addresses. WebRTC uses ICE to find a path anyway. Each side gathers possible addresses, tests every pairing and keeps one that works (RFC 8445).
A STUN server tells each side the public address its router gave it. Where no direct path exists, a TURN server relays the video instead. Inside one building, viewers usually connect directly. Remote viewers across the internet are where relays matter.
Is WebRTC secure?
Yes, by design. The WebRTC security architecture says every media channel must be secured with SRTP, with DTLS used to set up the keys (RFC 8827). There is no unencrypted mode to switch on by mistake.
That is a real step up from plain RTSP, which many cameras still send unencrypted across the local network. It is one more reason to keep camera traffic on its own network and let the video platform carry it to viewers.
Scaling from one camera to a full video wall
Code that works for one camera often fails at fifty. Three things change as a wall grows.
- One pull per camera. Many cameras accept only a few connections. Pulling each camera once and sharing that feed means ten viewers never mean ten connections to the camera.
- Lighter streams for small tiles. Visylix shows video walls of up to 6x6, or 36 tiles. Small tiles use the camera's lighter second stream, and opening a camera full screen switches to full quality.
- Conversion only where needed. Converting every stream would need racks of servers. Passing video through untouched keeps a large wall on modest hardware.
How Visylix does it natively
Visylix handles the whole RTSP to WebRTC journey inside its native streaming engine, built in house. There is no separate conversion tool or media server to run.
Each camera is pulled once, and that one feed serves live view, recording and AI. The camera's H.264 or H.265 video goes to the browser without conversion wherever it can be played. Where a browser cannot play H.265, Visylix converts that one stream to H.264 on the CPU, for WebRTC only. When an operator clicks a camera, the live picture appears almost at once.
Visylix shows live camera video in any modern browser over WebRTC in under a second, and down to under 200 ms in ideal conditions. It converts H.265 to H.264 only where a browser needs it, on the CPU, for that one stream. Video wall tiles use the camera's lighter second stream, so a full wall stays smooth.
The same engine speaks 13+ protocols; see live view and streaming.
How fast is it?
Visylix delivers sub second live view over WebRTC, down to under 200 ms in ideal conditions. That is the full journey from the camera to the operator's screen.
The remaining delay in a real control room usually comes from the camera's own encoder settings and the network, not the platform. We measure it with you on your own cameras and network, and you keep the figures. Live view runs in any modern browser, alongside 13+ other protocols in the same engine, including RTSP, RTMP, HLS, LL-HLS, SRT and RIST.
Where the rest of the delay comes from is set out in low latency streaming.
FAQ
Why convert RTSP to WebRTC instead of just using HLS?
HLS sends video in chunks, so the picture always arrives several seconds late, which is too slow for live security work. WebRTC delivers sub second live view and plays natively in Chrome, Edge, Safari and Firefox with no plugins. For live incident response in a browser, WebRTC is the right choice.
What is wrong with using FFmpeg as the RTSP to WebRTC bridge?
A general purpose tool like FFmpeg unpacks and repacks every stream, which uses a lot of processing power per camera. Large estates end up needing dedicated servers just for conversion. Visylix passes the camera's own H.264 or H.265 video straight into WebRTC wherever the browser can play it. That keeps servers light and live view fast.
What end to end latency should I expect from Visylix in production?
Sub second live view over WebRTC, down to under 200 ms in ideal conditions. In practice the camera encoder settings and your network have the most influence. We measure it on your own cameras and network and give you the results.
Do I need a separate media server like Janus or MediaMTX with Visylix?
No. Visylix handles camera ingest, the browser connection and encryption inside its own native streaming engine. There is no separate media server to install or maintain, which keeps the system simpler and the attack surface smaller.
Can WebRTC video get through a firewall?
Usually, yes. WebRTC uses ICE to find a working path, with STUN to learn public addresses. A TURN relay is the fallback when no direct path exists. Inside one building, viewers normally connect directly.
Is WebRTC video encrypted?
Always. The WebRTC standards require every media channel to be secured with SRTP, with keys set up over DTLS, so there is no unencrypted mode.
Sources
This guide supports live view and streaming on the Visylix platform.










