How to route an RTMP camera feed into a streaming setup

The short answer

A camera that outputs RTMP (Real-Time Messaging Protocol) does not appear on your computer as a webcam. It pushes its video, and usually its audio, to a server address that you give it. To use that feed in a streaming setup, you need something on your computer or network that receives the stream. You then add that received stream as a source in your streaming or production software. If you want the feed in a video-call app, the usual final step is to send the software's output to a virtual camera, which the call app can select like a normal webcam.

Two points can change this answer. First, RTMP is a push protocol: the camera sends, and something must be listening. Many IP and security cameras use RTSP instead, which is a pull protocol. With RTSP, your software connects to the camera directly and no separate receiving server is needed. Check which one your camera actually offers. Second, if your goal is only to send the camera straight to a streaming platform, you can enter the platform's server address and stream key in the camera itself. Nothing on your computer is involved. This guide covers the other case, where the camera feed has to pass through your own setup first.

For DSLR and mirrorless cameras, RTMP output is only one possible route, and many models do not offer it. Other common routes are a manufacturer's USB webcam utility or an HDMI capture device. Use the RTMP route only if your camera or its companion app has an RTMP, custom RTMP or custom live-stream option. Your camera's manual or app settings will show whether it does.

What you need before you start

• A camera, or a camera companion app, that can stream to a custom RTMP server address.
• A computer on the same local network as the camera, preferably with a wired connection.
• RTMP server software running on that computer, or on another machine on the network, to receive the stream.
• Streaming or production software that can open a network stream as a media source.
• The computer's local IP address, so the camera knows where to send the stream.
• Firewall permission for the RTMP server to accept incoming connections. RTMP conventionally uses TCP port 1935 unless you configure a different one.

Step 1: Start a receiving RTMP server

Install and run an RTMP server on your computer. This can be a dedicated lightweight RTMP server application or a web server with an RTMP module. The server's documentation will tell you two things: the application name it expects, such as a path segment often called something like live, and whether it needs any configuration before it accepts streams. Your operating system may ask whether to allow the program through the firewall. Allow it on private networks if you trust the network you are on.

Success check: the server is running without errors, and its log or status display shows it is listening for connections. This confirms only that the receiver is ready. It does not confirm the camera can reach it.

Step 2: Point the camera at the server

In the camera or its app, choose the custom RTMP or custom live-stream option. Enter a server address made up of four parts: the rtmp scheme, your computer's local IP address, the port if you changed it from the default, and the application name your server expects. Then enter a stream key or stream name. On a local server this is often any name you choose, and you will reuse it in the next step. Some cameras ask for the server address and stream key in separate fields. Others want them combined into one address. Follow the format the camera's own screen describes. Start the stream from the camera.

Success check: the server's log or status page shows an incoming connection or an active stream under the name you chose. Many cameras also display a live or streaming indicator. A camera indicator alone does not prove the server received anything, so rely on the server's own confirmation.

Step 3: Add the feed to your streaming software

In your streaming or production software, add a source that can play a network stream. Enter the same address the camera is publishing to, including the stream name. In OBS Studio, for example, you add a Media Source, turn off the option for a local file, and enter the stream address as the input. Other programs may call this a network source, a stream input or a URL input. Where buffering or latency settings are available, lower buffering reduces delay but can make the picture less stable on a weak network. Adjust in small steps and recheck after each change.

Success check: moving video from the camera appears in the software's preview, and it keeps updating rather than freezing on one frame. This confirms the full chain from camera to server to software. It does not confirm audio, sync or quality, which are covered below.

Step 4: Use the feed in a video call

Video-call apps generally list only camera devices, not network streams. To use the RTMP feed in a call, start your streaming software's virtual camera output, if it has one. OBS Studio includes a Start Virtual Camera control, for example. Then, in the call app's video settings, select that virtual camera. If the call app does not list it, fully quit and reopen the call app. Also check that the app has camera permission in your operating system's privacy settings, and in the browser if the call runs in a browser.

Success check: the call app's preview shows the same image as your streaming software's output. This proves the call app can access the virtual camera and capture video from it. It does not prove call quality. Resolution, compression and network conditions during a real call are decided by the call service and your connection. Only a test call with another participant, or the service's own test call feature if it has one, shows what others actually see.

Checking audio from the camera

An RTMP stream can carry audio from the camera's microphone or from a microphone connected to the camera. If you want that audio, confirm the media source's audio appears in your software's mixer. Speak near the microphone and watch the meter move. A moving meter shows only input activity. It does not show that speech is clear, free of echo, or in sync with the picture. To check those, record a short clip in your software and play it back, listening for clarity and watching whether lip movement matches the sound.

Because a network stream usually arrives later than a microphone plugged directly into the computer, mixing the camera's video with a separate computer microphone can put sound ahead of the picture. Many streaming programs offer an audio delay or sync offset setting for this. Adjust it while watching a playback of a clap or a spoken hard consonant until they line up. Virtual camera outputs typically carry video only, so the call app will need its own microphone selection. Choose either your real microphone or a virtual audio device, depending on how you route sound.

The supplied material does not include verified input-level targets or other technical thresholds for this setup. This guide therefore does not recommend specific meter readings, bitrates, resolutions or latency figures. Use your software's and camera's documentation for those values, and confirm by listening and viewing test recordings.

If something does not work

• Camera says it cannot connect: confirm the computer's IP address has not changed, that both devices are on the same network, that the server is running, and that the firewall allows the RTMP port.
• Server shows the stream, but the software shows nothing: check that the address and stream name in the software match what the camera publishes, character for character.
• Video appears but freezes or stutters: try a wired connection, move the camera closer to the router, or lower the camera's streaming quality setting if it offers one.
• Video is noticeably delayed: reduce buffering in the media source if that option exists. Some delay is inherent to RTMP and cannot be removed entirely.
• Call app does not list the virtual camera: confirm the virtual camera is started, restart the call app, and check camera permissions in the operating system and browser.
• No camera audio: check that the camera is set to include audio in its stream and that the media source is not muted in your software's mixer.

Limitations to keep in mind

Routing a camera through RTMP adds delay compared with a USB webcam or an HDMI capture device. This matters most in live conversation, where a delayed picture can feel out of step with your voice. The setup also depends on the camera staying connected to the network and the server staying running. Wi-Fi drops or a changed IP address will interrupt it. If your camera offers a direct USB webcam mode or clean HDMI output, those routes are often simpler for calls. RTMP is most useful when the camera has no other output you can use, or when it needs to sit away from the computer on the network.