RTSP Protocol (Real Time Streaming Protocol)

RTSP is the control protocol behind most IP cameras, NVRs and low-latency live streams. This guide explains what it is, how it works with RTP and SDP, its main methods and ports, and how it compares with RTMP, SRT, WebRTC and HLS.

What is RTSP?

RTSP (Real Time Streaming Protocol) is an application-layer, client-server control protocol for delivering audio and video over IP networks. It works like a remote control for a live stream: the client asks the server to describe a stream, set up the transport, and then play, pause or tear down the session.

RTSP does not carry the media itself. It negotiates and controls the session, while the actual audio and video are packaged and sent with RTP (Real-time Transport Protocol) and monitored with RTCP. The stream is described in SDP (Session Description Protocol).

RTSP is standardized in RFC 2326 (RTSP 1.0) and RFC 7826 (RTSP 2.0). It is the de facto control protocol for IP surveillance and is widely supported by players and tools such as VLC, ffmpeg and GStreamer.

How RTSP works

An RTSP session typically follows four steps:

  1. DESCRIBE — the client asks the server for the stream description. The server replies with an SDP document listing the media tracks, codecs and transport options.
  2. SETUP — the client and server agree on the transport for each track (RTP over UDP, RTP over TCP, or interleaved over the RTSP connection).
  3. PLAY — the server starts sending RTP media to the negotiated ports. The client can later send PAUSE to stop temporarily.
  4. TEARDOWN — the session ends and the server releases its resources.
Key idea: RTSP is stateful. The server tracks each session by a Session ID, which is why RTSP can start, seek, pause and stop a live stream — something file-based HTTP streaming cannot do natively.

RTSP methods

The RTSP protocol defines a small set of request methods, similar in style to HTTP:

  • OPTIONS — query the methods the server supports.
  • DESCRIBE — retrieve the SDP description of a media resource.
  • SETUP — create a transport for a media stream.
  • PLAY — start or resume delivery of the stream.
  • PAUSE — halt delivery without tearing down the session.
  • TEARDOWN — end the session.
  • ANNOUNCE / RECORD — publish or record media (used by RTSP publishing tools).
  • GET_PARAMETER / SET_PARAMETER — read or set session parameters and keep-alives.

RTSP ports and URL format

RTSP uses TCP port 554 by default, and RTSPS (RTSP over TLS) commonly uses port 322. The actual RTP media is carried on dynamically negotiated UDP or TCP ports unless it is interleaved over the RTSP connection.

A typical RTSP URL looks like this:

RTSP URL
rtsp://username:password@192.168.1.64:554/Streaming/Channels/101

Many cameras also expose an RTSPS endpoint on port 322 for encrypted control, and some support RTSP over HTTP tunneling on port 80 or 443 when the network blocks port 554.

RTSP vs RTMP, SRT, WebRTC and HLS

RTSP is one of several streaming protocols. The table below is an approximate comparison for typical configurations; real latency and compatibility depend on the encoder, network and player.

ProtocolTypical latencyTransportBest for
RTSPSub-second to ~2 sRTP over UDP/TCPIP cameras, NVRs, VMS, LAN live viewing
RTMP~1–3 sTCPIngest to CDNs and live platforms
SRT~0.1–1 sUDP (ARQ)Lossy or long-distance contribution links
WebRTC< 0.5 sUDP/SRTPBrowser playback and conferencing
HLS~6–30 sHTTP(S)Scalable delivery to many viewers

For deeper latency numbers, see latency in mainstream streaming protocols.

Common RTSP use cases

  • IP cameras and NVRs — live view and recording control over RTSP.
  • Video management systems (VMS) — pull camera streams from multiple vendors.
  • Streaming servers — accept RTSP publishes and serve RTSP clients on a LAN.
  • Protocol conversion — convert RTSP to RTMP, SRT, WebRTC or HLS for distribution.
  • Testing and simulation — emulate cameras or publish synthetic streams with RTSP tools.

How to open and test an RTSP stream

The quickest way to verify an RTSP URL is with a desktop player or ffmpeg:

  • VLC: Media → Open Network Stream → paste the rtsp:// URL.
  • ffmpeg: ffplay rtsp://user:pass@host:554/stream

If the camera sits behind a firewall that blocks port 554, use RTSP over HTTP/TCP or an RTSP tunnel instead.

Happytime RTSP tools

Happytimesoft provides RTSP software and SDKs for both ends of the session:

  • RTSP Client — low-latency player and C SDK for RTSP/RTP.
  • RTSP Server — self-hosted RTSP server for LAN and camera simulation.
  • RTSP Pusher — publish screen, camera, file, RTMP or SRT sources to an RTSP server.

FAQ

Is RTSP still used?

Yes. RTSP remains the standard control protocol for IP cameras, NVRs and surveillance streaming, and is supported by VLC, ffmpeg and most VMS platforms.

Is RTSP secure?

Plain RTSP is unencrypted. Use RTSPS (RTSP over TLS) or SRTP to encrypt control and media, and prefer digest authentication over basic auth.

Does RTSP use TCP or UDP?

RTSP control normally runs over TCP. Media can use RTP over UDP (lower latency) or RTP over TCP (more firewall-friendly), depending on what the client and server negotiate.

Standards & references

Key standards: RTSP 1.0 is RFC 2326 and RTSP 2.0 is RFC 7826; the default RTSP port is 554; RTP/RTCP is RFC 3550; SDP is RFC 8866.

Standards checked 2026-11-17. Primary sources are linked for verification.