> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/guides/meshcast-rtmp-srt-to-obs.md).

# Bring RTMP or SRT into OBS with Meshcast

Bring a phone, OBS, or hardware encoder into OBS through Meshcast using RTMP or SRT.

Send a camera feed to Meshcast, then receive it in OBS. The sender and OBS can be on different networks.

![A phone or encoder sends RTMP or SRT to Meshcast. Meshcast sends the feed to an OBS Browser Source.](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-5e3d15f044a16c55b1717270c4222ef6cf2cc7a0%2Fencoder-to-obs.svg?alt=media)

For a phone camera, start with the **VDO.Ninja native app**: follow the illustrated [SRT setup](https://docs.vdo.ninja/guides/mobile-app/srt-to-meshcast.md) or [RTMP setup](https://docs.vdo.ninja/guides/mobile-app/rtmp-to-meshcast.md). The steps below also work with compatible hardware encoders and a sending copy of OBS.

## 1. Create a Meshcast stream

1. Sign in at [app.meshcast.io](https://app.meshcast.io/). RTMP and SRT need a registered account, including a free account.
2. Open **Studio**. Under **Stream**, select a stream or choose **+ Create New Stream**.
3. Give it a recognizable name, such as `Remote camera`.

See [Meshcast account setup](https://docs.vdo.ninja/guides/meshcast-setup.md#set-up-an-account-for-srt-or-rtmp) for screenshots. Check [current plans](https://app.meshcast.io/pricing) for bandwidth and viewer limits.

## 2. Start the sender

Copy publishing details from Studio into the phone or encoder:

| Sending with | Copy from Meshcast                  | Set on the sender                                   |
| ------------ | ----------------------------------- | --------------------------------------------------- |
| RTMP         | **RTMP Server** and **Publish Key** | Server and stream key in separate fields            |
| SRT          | Complete **SRT URL (Caller Mode)**  | SRT caller mode; keep the full URL and query string |

Use **H.264 video**, **AAC audio**, and **0 B-frames** for the Browser Source path below. If the encoder calls the option **Use B-Frames**, turn it off. Restart the output after changing encoder settings.

In a sending copy of OBS, these settings belong under **Settings > Stream** and **Settings > Output**. For SRT, paste the full publishing URL into **Server** and leave **Stream Key** empty.

Start the phone or encoder and confirm Meshcast receives the stream. Studio's **Go Live** button starts its browser camera or screen; you do not need it for an external encoder. Keep publishing keys private.

## 3. Add the feed to the receiving OBS

1. In Meshcast Studio, open **Watch Links** for the same stream.
2. Copy **VDO.Ninja View Link**, including its `whep` parameter and any server options.
3. In the receiving OBS, choose **Sources > + > Browser** and paste that link into **URL**.
4. Enable **Control audio via OBS**, then check the picture and audio meter.
5. Make a short recording and play it back to check both sound and motion.

You do not need to press **Start Streaming** in the receiving OBS. That button sends OBS's finished program to another service.

## Prefer an SRT Media Source?

Meshcast can also send the feed to an OBS **Media Source** over SRT. This is useful when you want to receive without a browser player.

Follow [Meshcast's SRT receive guide](https://app.meshcast.io/docs/srt-to-obs). It uses the stream's media server and public Stream ID in a `read:` URL. The SRT publishing URL contains credentials and belongs on the sender, not in the receiving source.

## Quick fixes

| Problem                            | Check                                                                                              |
| ---------------------------------- | -------------------------------------------------------------------------------------------------- |
| Nothing in OBS                     | Start the sender first. Copy the view link for the same Meshcast stream; do not use a publish URL. |
| Browser playback fails             | Use H.264 with B-frames disabled. Restart the sender after changing this.                          |
| No sound                           | Enable sender audio and **Control audio via OBS**; unmute the source in OBS.                       |
| Breakup or growing delay           | Lower the sending bitrate. For SRT, allow more recovery time in its latency setting.               |
| Several viewers overload the phone | Give them the Meshcast viewing link and close unused direct phone previews.                        |

To send the finished show to several platforms, use [multistreaming with Meshcast](https://docs.vdo.ninja/guides/multistream-with-meshcast.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdo.ninja/guides/meshcast-rtmp-srt-to-obs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
