
RTSP streaming is a way to control and receive live video from IP cameras, media servers, and other network video sources. It is commonly used to bring a camera feed into OBS Studio, VLC, an NVR, or a monitoring system with low delay.
RTSP is usually used to move video inside a production or monitoring workflow. For example, OBS can receive an RTSP camera feed and then send the finished production to a streaming platform.
This guide explains what RTSP streaming is, how it works, what you need, and how to connect an RTSP camera to OBS. RTSP can support workflows such as event streaming, sports production, church services, recording, monitoring, and multi-camera video production.
RTSP stands for Real-Time Streaming Protocol. It establishes and controls a media session between a server and a client.
For example, imagine adding a live IP camera feed to OBS. RTSP works like a remote control: it tells the camera when OBS wants to start, pause, or stop the feed. RTP works more like a delivery vehicle, carrying the actual video and audio from the camera to OBS across the network.
Unlike HLS, which is designed for browser-friendly delivery to large audiences, RTSP is commonly used for IP cameras, security systems, local production networks, and professional video workflows. Its main strengths are low latency, direct camera access, and compatibility with applications such as OBS and VLC.
Common RTSP Usage Scenarios:
| What You Need to Do | Suitable Protocol |
|---|---|
| Pull a live feed from an IP camera | RTSP |
| Add a network camera to OBS or VLC | RTSP |
| Stream from OBS to YouTube or Facebook | RTMP or another platform-supported protocol |
| Send video over an unstable internet connection | SRT |
| Deliver live video to a web browser | HLS or WebRTC |
| Discover and control compatible IP cameras | ONVIF, often used with RTSP |
RTSP is a strong choice when you need to receive a live video source with low delay. RTMP, SRT, HLS, and WebRTC solve different parts of the streaming workflow, see our guide on the difference between RTSP, RTMP.
RTSP uses a client-server model:
A typical RTSP session follows this process:
Before setting up an RTSP stream, prepare the following:
A wired Ethernet connection is usually more stable for long sessions or multiple high-resolution feeds. Wi-Fi can work well when the signal is strong and the network is not congested.
An RTSP URL may look like this:
rtsp://192.168.1.100:8554/live
The address contains several parts:
Some devices include a username, password, channel number, or stream quality setting in the URL.
RTSP works in a similar way across different devices. A computer may open the feed in OBS or VLC, an NVR may record it, and a mobile application may display it through the camera system. A web page normally needs the RTSP stream converted to HLS, WebRTC, or another browser-supported format.

The OBSBOT Tail 2 can work as an RTSP video source in a local production network. Once RTSP is enabled, OBS or another compatible client can receive the camera feed through Wi-Fi or Ethernet.
This setup is useful for events, sports, houses of worship, studios, and other productions that need a network camera without placing a capture card beside it. Tail 2 also supports other professional connection and streaming options, making it easier to match the camera to different production systems.
Key RTSP-Related Features:
The following setup uses OBSBOT Tail 2 as the RTSP camera and OBS Studio as the receiving application. Other cameras use a similar workflow, but the location and format of their RTSP settings may differ.
The address may look similar to:
rtsp://192.168.1.xxx:8554/live
Your camera and computer should be connected to the same local network. When RTSP mode is enabled on Tail 2, other video output modes, such as UVC or NDI, may be unavailable until you change the operating mode.

OBS Studio can receive the RTSP feed through Media Source or VLC Video Source.
Media Source is the simpler starting point for a single RTSP feed. VLC Video Source is useful when you want VLC-based decoding, playlist controls, or adjustable network caching. VLC Video Source requires VLC Media Player to be installed on the computer.

5. Clear the Local File checkbox.
6. Paste the RTSP URL into the Input field.
7. Enable hardware decoding if it is available and works reliably on your computer.
8. Select OK.
The Tail 2 feed should now appear in the OBS preview.

9. Adjust Network Caching if you need to balance lower delay against smoother playback.
10. Select OK to add the feed to the OBS scene.


If VLC Video Source does not appear in OBS, check that VLC and OBS use compatible 32-bit or 64-bit versions.
| Problem | What to Check |
|---|---|
| OBS shows a black screen | Confirm that the RTSP URL is complete and RTSP mode is enabled. |
| The connection times out | Make sure the camera and computer can access the same network. |
| OBS repeatedly disconnects | Use Ethernet or improve the Wi-Fi connection. |
| The feed works in the camera app but not in OBS | Check the RTSP port, stream path, username, and password. |
| Playback has a long delay | Reduce unnecessary network caching and check network congestion. |
| Video appears but there is no sound | Confirm that the selected RTSP stream includes an audio track. |
If the feed still does not appear, open your own RTSP URL in VLC using Open Network Stream. If VLC also cannot play it, the problem is more likely related to the camera settings, URL, credentials, or network rather than OBS.
Once the feed appears in OBS, you can:
RTSP brings the camera feed into OBS. OBS then encodes and publishes the final program through the protocol supported by the destination platform.
Most modern browsers cannot play RTSP in a standard HTML video player. To show an RTSP camera feed on a web page, a server or gateway normally needs to convert it to WebRTC, HLS, DASH, or another browser-supported format.
Yes. RTSP is still widely used for IP cameras, local network monitoring, NVR systems, video production, and software such as OBS and VLC. It remains useful when low delay and direct access to a camera feed are more important than browser compatibility.
No. Some consumer cameras use proprietary applications and do not provide an accessible RTSP feed. Before purchasing or configuring a camera, check its specifications, user manual, network settings, and supported protocols.
Look in the camera's network, streaming, or device information settings. The manufacturer's user manual or support page may also provide the required URL format. You may need the camera's IP address, RTSP port, username, password, channel, and stream path.
Yes. OBS can receive an RTSP URL through Media Source or VLC Video Source. Media Source is a straightforward option for a single feed, while VLC Video Source provides VLC-based decoding, playlist support, and network caching controls.
YouTube does not normally accept a camera's RTSP URL as the public live input. A common workflow is to receive the RTSP camera feed in OBS and then send the completed program from OBS through a protocol supported by YouTube.
ONVIF is a standard that helps compatible IP devices handle discovery, configuration, and camera control. RTSP establishes and controls the media streaming session. An IP camera may use ONVIF for device management and RTSP for delivering its live video feed.
RTSP streaming is best suited to receiving live video from cameras and media servers with low delay. A complete setup requires a compatible video source, the correct RTSP URL, a stable network, and receiving software such as OBS or VLC.
For an OBS workflow, first enable RTSP on the camera, copy its stream address, and add it through Media Source or VLC Video Source. Once the feed is available in OBS, it can be recorded, combined with other sources, or included in a finished live production.




