What Is RTSP? The Real-Time Streaming Protocol Explained (Update)

The Real-Time Streaming Protocol (RTSP) is an application-layer control protocol that sets up and manages live audio and video sessions between a client and a media server. It sends commands like SETUP, PLAY, PAUSE, and TEARDOWN, while the Real-time Transport Protocol (RTP) carries the media itself. Like other streaming protocols used for ingest and first-mile contribution, it moves video from a source to a server, where it is packaged for low-latency delivery.

The Real-Time Messaging Protocol (RTMP), along with RTSP, once dominated the streaming landscape. That’s no longer the case today. Nevertheless, RTSP remains a cornerstone in many security and surveillance architectures, particularly in closed-circuit television (CCTV) systems. The reason is simple: it’s still the preferred protocol for IP cameras.

What Is RTSP?

RTSP servers often leverage the Real-Time Transport Protocol (RTP) in conjunction with the RTP Control Protocol (RTCP) to move the actual streaming data. The official 1998 RTSP standard states:

“The Real-Time Streaming Protocol (RTSP) establishes and controls either a single or several time-synchronized streams of continuous media such as audio and video. It does not typically deliver the continuous streams itself, although interleaving of the continuous media stream with the control stream is possible. In other words, RTSP acts as a ‘network remote control’ for multimedia servers.”

When a media server pulls a video stream from an IP camera using RTSP, the server sends RTSP requests (DESCRIBE, SETUP, PLAY) to the camera, and RTP then carries the audio and video.

RTSP At A Glance

• Audio Codecs: Codec-agnostic, so the stream’s SDP sets the codec. Wowza Streaming Engine ingests AAC, AAC-LC, HE-AAC+ v1 & v2, MP3, Speex, Opus, and Vorbis.
• Video Codecs: Codec-agnostic, so the stream’s SDP sets the codec. Wowza Streaming Engine ingests H.265, H.264, VP9, and VP8.
• Playback Compatibility: Web browsers do not play RTSP natively. Desktop players, such as VLC media player, can play RTSP.
• Benefits: Low-latency and ubiquitous in IP cameras.
• Drawbacks: Not optimized for quality of experience and scalability, with no native browser playback or adaptive bitrate streaming.
• Latency: Sub-second to about 2 seconds on a local network.
• Transport: RTSP control messages over TCP port 554, with RTP media over UDP or interleaved in the TCP connection.
• Security: RTSPS over TLS on TCP port 322, with SRTP for media encryption.
• Standards: RFC 2326 (RTSP 1.0) and RFC 7826 (RTSP 2.0).
• Variant Formats: RTSP as an umbrella term describes the entire stack of RTP, RTCP (RTP Control Protocol), RTSPS (RTSP over TLS / Secure RTSP), and RTSP.

What are RTSP commands?

RTSP employs various commands to control media streams. These include:

• Options: This request determines what other types of requests the media server will accept.
• Describe: A describe request retrieves the media description, usually via Session Description Protocol (SDP).
• Announce: The announce method describes the presentation when sent from the client to the server and updates the description when sent from the server to the client. It is worth noting that RTSP 2.0 removed this method.
• Setup: Setup requests specify how a media stream must be transported before a play request is sent.
• Play: A play request starts the media transmission by telling the server to start sending the data.
• Pause: Pause requests temporarily halt the stream delivery.
• Record: A record request initiates a media recording. RTSP 2.0 also removed this method.
• Teardown: This request terminates the session entirely and stops all media streams.
• Redirect: Redirect requests inform the client that it must connect to another server by providing a new URL for the client to issue requests to.
• Get Parameter and Set Parameter: Read or change parameter values for a presentation or stream.
• Play Notify: Added in RTSP 2.0, this lets a server notify a client about events in an active session, such as a stream ending.

More information on RTSP 1.0 and RTSP 2.0 can be found in RFC 2326 and RFC 7826, respectively.

How RTSP, RTP, and RTCP Work Together

RTSP controls the session, RTP carries the audio and video packets, and RTCP reports reception quality such as packet loss and jitter so endpoints can adjust. The difference between RTP and RTSP comes down to control versus transport.

Does RTSP Use TCP or UDP?

RTSP control messages travel over TCP, but RTSP 2.0 removed RTSP message transport over UDP. RTP media usually travels over UDP for the lowest latency. When a firewall or NAT blocks UDP, interleaved binary data carries RTP inside the RTSP TCP connection. Wowza Streaming Engine supports UDP, interleaved TCP, and RTSP tunneled over HTTP through the rtpTransportMode stream file setting.

Typical RTSP Workflow

RTSP is a stateful protocol used more often for video contribution (ingest) than for last-mile delivery and playback (egress). Web browsers don’t play RTSP streams natively. So, people rarely use RTSP for end-to-end streaming. Instead, most broadcasters leverage a media server like Wowza to repackage the RTSP stream into a more user-friendly format like HLS.

The same RTSP ingest in Wowza Streaming Engine can also feed the Wowza Video Intelligence Framework (VIF), which enables object detection, scene understanding, and vision-language model analysis on live frames. Verify, an extension of VIF’s integration with the NVIDIA Synthetic Video Detector, flags synthetic or AI-generated video in real-time, with a verdict, confidence score, and the plain-language reasoning behind it.

What Is An RTSP Stream?

An RTSP stream is a live audio and video session controlled by the Real-Time Streaming Protocol. It does not transport the media, rather, it works alongside the Real-Time Transport Protocol (RTP), which carries the audio and video packets between endpoints. Each RTSP stream has its own rtsp:// URL, and most IP cameras expose more than one, such as a main stream for recording and a sub-stream for live viewing. RTSP streams remain the dominant ingest format in IP camera and surveillance workflows.

RTSP Ports, URL Format, and Security

What Port Does RTSP Use?

RTSP uses TCP port 554 by default, and RTSPS uses TCP port 322. RFC 7826 also registers port 8554 as an alternative. RTP and RTCP use separate ports that the client and server negotiate during SETUP. Wowza Streaming Engine accepts incoming RTP on UDP ports 6970 to 9999 by default. Wowza Streaming Engine 4.12 also uses that range for WebRTC by default, so deployments that run both should assign separate ranges.

What Is the RTSP URL Format?

An RTSP URL follows the pattern rtsp://[username:password@]host[:port]/path. The rtsps:// scheme signals RTSP over TLS. Clients assume port 554 for RTSP and port 322 for RTSPS when the URL does not specify a port. Each camera manufacturer defines its own path, listed in the device’s interface or documentation.

Is RTSP Secure?

Plain RTSP sends control messages and media without encryption. RTSPS wraps the control channel in TLS, and SRTP encrypts the RTP media. Wowza Streaming Engine supports SRTP for publishing and playback and supports Basic and Digest authentication for RTSP sources.

RTSP 1.0 vs. RTSP 2.0

RTSP emerged in the late 1990s from Netscape Communications, Progressive Networks (RealNetworks), and Columbia University. The Internet Engineering Task Force (IETF) officially published it in 1998, with Version 2.0 introduced in December 2016 as RFC 7826. That made Version 1.0 (RFC 2326) obsolete. Most IP cameras still implement Version 1.0, though, so media servers and clients often support both versions.

Before adaptive bitrate streaming (ABR) via HLS (HTTP live streaming) and MPEG-DASH (dynamic adaptive streaming over HTTP), RTSP and RTMP dominated the live streaming space. However, they were not suited for large-scale streaming due to their reliance on dedicated servers. 

Primarily, organizations use RTSP for ingest. In other words, it is used in the first part of the streaming workflow, before the streams are transmuxed for delivery. Most workflows leverage a media server to ingest streams transmitted via RTSP/RTP and then repackage the file for delivery to viewing devices, ranging from iPhones to smart TVs.

Next-generation alternatives like Secure Reliable Transport (SRT) are common for contribution over public networks. Even so, RTSP remains popular in surveillance workflows as the de facto standard for IP cameras.

RTSP for IP Cameras

IP cameras use RTSP to deliver live video to recorders, video management systems, and media servers. The Mississippi Department of Transportation runs about 1,300 traffic cameras on Wowza Streaming Engine and automates provisioning and failover through the Wowza Streaming Engine REST API. Because VIF runs inside Wowza Streaming Engine, existing cameras can feed real-time detection without new camera hardware. Organizations that stream an IP camera to a website typically route each camera through a media server first.

Do All IP Cameras Support RTSP?

No, not all IP cameras support RTSP. While it is common in professional surveillance, many consumer-grade, battery-powered, or cloud-based cameras lack support and lock users into proprietary apps with cloud subscriptions.

RTSP and ONVIF

ONVIF is an interoperability standard that defines how IP cameras announce themselves and expose their capabilities. ONVIF Profile S relies on RTSP for streaming, so ONVIF-conformant cameras expose RTSP URLs that discovery tools can find automatically. Wowza’s open-source ONVIF module uses Profile S discovery to locate cameras on a network and create stream files for them in Wowza Streaming Engine.

IP Cameras Behind NAT

Cameras behind NAT often advertise a private IP address in their SDP, so the DESCRIBE request can succeed without media arriving. Wowza Streaming Engine 4.12 added the rtspIgnoreAdvertisedHost setting, a stream file property that sends SETUP and PLAY requests to the host and port in the configured stream URI instead.

How to View, Set Up, and Test an RTSP Stream

How do I view an RTSP stream?

Web browsers and most consumer devices do not natively support RTSP playback, so viewing an RTSP stream usually requires a compatible player like VLC or a 3GPP-compliant mobile player. Apple’s QuickTime player used to support it, but Apple has since quietly phased out support. For browser-based or large-scale playback, the standard approach routes the feed through a media server such as Wowza Streaming Engine, which transmuxes the stream into HLS, MPEG-DASH, or WebRTC for delivery to viewing devices.

How do I set up an RTSP stream?

Setting up an RTSP stream requires a source that publishes it (typically an IP camera, encoder, or software like FFmpeg), a media server to ingest and manage the session, and the network configuration to connect them. The general workflow is:

1. Configure the source. On an IP camera, locate the RTSP settings in the device’s web interface and enable the server. Most IP cameras serve a primary and secondary stream, where one would be considered high quality and the second low quality. Make sure you are connecting to the appropriate stream URL: rtsp://[username:password@]camera-ip:554/path. For software encoders, point the RTSP output at the destination server’s IP and port.
2. Provision the media server. There are two distinct provisioning workflows, depending on whether you’re working with a camera or an encoder. Camera streams will generally be provisioned on Wowza Streaming Engine using the .stream file, where the server initializes the connection. Encoder streams are where the encoder initializes the connection.
   1. For camera streams, first create a live application configured to accept RTSP/RTP ingest in Wowza Streaming Engine. Generate a .stream file, use the Stream Files interface to define the source URL, or configure the camera to push to the server’s RTSP endpoint. To make an IP camera connection persistent, add the .stream file to the StartupStreams list with the rtp MediaCaster type so it reconnects when the server restarts.
   2. For encoder streams, configure the encoder to connect to an RTSP endpoint on Wowza Streaming Engine, using a URL in the format rtsp://[wowza-ip]:[port]/[application-name].
3. Open the required ports. RTSP uses TCP port 554 by default for session control, with RTP media flowing over dynamically negotiated UDP ports (or interleaved over the same TCP connection for firewall-restricted environments). Wowza Streaming Engine accepts incoming RTP on UDP ports 6970 to 9999 by default.
4. Start the stream and verify ingest. Launch the source, then confirm the media server is receiving the feed. Then the server can transmux the stream into HLS, MPEG-DASH, or WebRTC for delivery.

Learn more about restreaming from an IP camera using Wowza Streaming Engine.

How do I test an RTSP stream?

Testing an RTSP stream confirms that the source publishes successfully and that the stream remains reachable, decodable, and playable downstream. The fastest method is to open the RTSP URL in VLC (Media > Open Network Stream) to verify the video renders without errors. For a more complete test, ingest the stream into Wowza Streaming Engine and validate playback through the Wowza test players. Wowza provides a free RTSP test stream as a known-good source for checking a player or integration.

How do I check my stream URL?

RTSP URLs follow a standard format: rtsp://[username:password@]host[:port]/path, with TCP port 554 as the default. Most IP cameras publish the exact stream URL in the device’s web interface or product documentation, with manufacturers like Axis, Hanwha, Hikvision, and Dahua listing it under streaming or network settings. To verify the URL works, paste it into VLC or send it to a media server endpoint and confirm a successful SETUP and PLAY exchange.

RTSP vs. Other Streaming Protocols

RTSP usually works alongside other protocols, rather than replacing them. It brings camera feeds into a media server, and other protocols handle contribution over public networks or delivery to viewers.

RTMP

RTMP is a better choice for streaming directly to a social media platform. More encoders and live streaming services accept RTMP. Wowza Streaming Engine can repackage RTSP camera feeds as RTMP and simulcast them to several destinations at once, which is a common way to live stream from an IP camera to social media. Our detailed protocol comparison covers the trade-offs in more depth.

SRT

SRT is an open-source protocol that runs over UDP, adding packet retransmission and AES encryption, which makes it a common choice for contribution over unpredictable public networks. Media servers and encoders widely support SRT, including Wowza Streaming Engine.

WebRTC

The speediest technology available right now is WebRTC. It delivers near-instantaneous voice and video to and from any major browser. It’s also the only answer if simplicity is key. Unlike the other protocols mentioned, WebRTC can be streamed from end to end, without additional processing.

RTSP and WebRTC usually work together. An IP camera publishes RTSP, a media server ingests it, and viewers watch over WebRTC. This typically can achieve a latency of one second or less for passthrough streams, and two seconds or less if transcoding is involved. For real-time surveillance, passthrough workflows are popular due to sub-second latency. For steps on how to set up these workflows, read the Wowza Streaming Engine guide to ingesting RTSP streams for WebRTC playback.

WebRTC used to be restricted to small-scale streaming and browser-based publishing. But, that’s all changing. A technology called the WebRTC HTTP Ingest Protocol (WHIP) provides encoding software and hardware with a standard signaling protocol when talking to media servers, thus removing WebRTC connectivity barriers between encoders and media servers. Wowza Streaming Engine supports WHIP and WHEP signaling, WHIP stream targets, simulcast, NACK/RTX retransmission, and ICE restart. To minimize latency and improve performance, using WebRTC and/or the WHIP protocol, from the source, will significantly out-perform in ultra-low latency when compared to contribution protocols.

HLS

HLS and its low-latency counterpart, LL-HLS, deliver video over HTTP to large audiences with adaptive bitrate streaming. RTSP and HLS fill different roles, where the former brings camera feeds into a media server, and the latter carries them to viewers at scale.

MoQ

Media over QUIC (MoQ) is an emerging IETF publish/subscribe delivery protocol, while RTSP remains a first-mile camera protocol. Wowza joined the OpenMOQ consortium and demonstrated Wowza Streaming Engine publishing over MoQ at NAB Show 2026.

Ingesting RTSP with Wowza Streaming Engine

Despite its age, RTSP has staying power as an ingest format. Delivering a feed to end-user devices still requires an RTSP streaming server that records, transcodes, and repackages camera feeds, managing each session that clients open with commands such as DESCRIBE, SETUP, and PLAY.

Wowza Streaming Engine pulls RTSP from IP cameras or accepts it from encoders, then transcodes, records, and repackages each feed for HLS, LL-HLS, MPEG-DASH, WebRTC, or RTMP delivery. Architecture guidance for large deployments appears in our guide for streaming at scale.

Choosing Wowza

Wowza provides a comprehensive, scalable streaming solution. Whether you need a media server for ingest, transcoding, or delivery, Wowza has you covered. Start with a free trial today.

Frequently Asked Questions

What does RTSP stand for?

RTSP stands for Real-Time Streaming Protocol. Netscape, Progressive Networks, and Columbia University developed it, and the IETF standardized it as RFC 2326 in 1998.

Is RTSP outdated?

RTSP is not outdated. IP cameras, network video recorders, and video management systems still use it to deliver live video to a media server. Viewers rarely watch it directly, so media servers such as Wowza Streaming Engine convert feeds to WebRTC, HLS, or MPEG-DASH for browsers and mobile devices.

What are the disadvantages of RTSP?

RTSP lacks native browser playback and adaptive bitrate streaming. It also sends media unencrypted, unless RTSPS and SRTP are configured. RTP over UDP can struggle with firewalls and NAT, and the server keeps a session open for every client, which limits scale for large audiences. That is why most workflows use it for camera ingest and WebRTC or HTTP-based protocols for delivery.

Can a web browser play an RTSP stream?

Modern browsers, including Chrome, Safari, Firefox, and Edge, do not play rtsp:// URLs natively. A media server such as Wowza Streaming Engine ingests the feed and repackages it as WebRTC for sub-second browser playback or as HLS and MPEG-DASH for larger audiences.

What is the difference between RTSP 1.0 and RTSP 2.0?

RTSP 2.0, published as RFC 7826 in December 2016, makes RTSP 1.0 (RFC 2326) obsolete. Version 2.0 removed the RECORD and ANNOUNCE methods and message transport over UDP, added the PLAY_NOTIFY method, and defined RTSP over TLS with the RTSPS scheme on port 322.