> 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-setup.md).

# Set up Meshcast for a phone camera

Set up Meshcast for a phone camera, find SRT or RTMP publishing details, and copy the correct VDO.Ninja viewing link into OBS.

Meshcast receives one upload and distributes it to viewers. Use it when several production viewers need a camera feed, or as a bridge from a phone's SRT/RTMP output into VDO.Ninja. For a single phone-to-OBS feed, start with [normal VDO.Ninja](https://docs.vdo.ninja/guides/streaming-sports-and-events.md).

Meshcast does not increase the phone's upload capacity. SRT adds packet-recovery buffering; RTMP is an alternative for services that expect a server address and stream key.

## Use the built-in Meshcast option

For simple server distribution, open **Additional outputs > Meshcast** in the [native app](https://docs.vdo.ninja/steves-helper-apps/native-mobile-app.md), enable **Use this destination**, and tap **Save**. Start the camera stream and use the app's viewing link, which now uses Meshcast. This uses WHIP and can work with an anonymous session, without manually setting up SRT or RTMP.

Browser publishers can use [`&meshcast`](https://docs.vdo.ninja/advanced-settings/meshcast-parameters/and-meshcast.md). Check [Meshcast's current limits](https://app.meshcast.io/pricing) when planning viewer counts and event length.

## Set up an account for SRT or RTMP

1. Open [app.meshcast.io](https://app.meshcast.io/) and select **Sign In** or **Get Started**.
2. Choose **Continue with Google** or **Continue with Discord**. Use the same account on later visits. Review the site's terms and complete the provider's sign-in prompts.
3. Open **Studio** from the dashboard. Under **Stream**, select an existing stream, or choose **+ Create New Stream**, enter a label such as `Event camera`, and click **Create Stream**.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-cc0192c0a4104dd07d87e593d857e8c998ea7b8a%2Fmeshcast-sign-in.jpg?alt=media" alt="Meshcast sign-in page with Continue with Google and Continue with Discord" width="420"><figcaption><p>The same page handles sign-in and account creation.</p></figcaption></figure>

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-10d3e0e21720b4da86f8d98da5f4da5b78a084de%2Fmeshcast-create-stream.jpg?alt=media" alt="Meshcast Studio Create New Stream dialog with Event camera entered as its label"><figcaption><p>Give the stream a recognizable label, then select it for publishing and viewing.</p></figcaption></figure>

A registered free account supports SRT and RTMP. If Studio shows **Anonymous Mode** and asks you to sign in for those tabs, complete sign-in first.

## Copy publishing details to the phone

Select the stream in Studio before copying its settings. Keep publishing URLs and keys private.

| Studio tab | Copy to the app                                                    | Phone instructions                                                                              |
| ---------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| **SRT**    | The complete **SRT URL (Caller Mode)**, including its query string | [SRT setup with screenshots](https://docs.vdo.ninja/guides/mobile-app/srt-to-meshcast.md)       |
| **RTMP**   | **RTMP Server** and the secret **Publish Key**                     | [RTMP setup with screenshots](https://docs.vdo.ninja/guides/mobile-app/rtmp-to-meshcast.md)     |
| **WHIP**   | The publishing URL for **Custom WHIP**                             | [WHIP settings](https://docs.vdo.ninja/steves-helper-apps/native-mobile-app.md#whip-publishing) |

Start publishing from the phone. Studio's **Go Live** button is for its own browser camera/screen source; you do not need to start a second browser publisher for the phone's SRT or RTMP feed.

## Bring the stream into OBS

1. In Studio, open **Watch Links** for the same stream.
2. Copy the complete **VDO.Ninja View Link**. Keep its `whep` parameter and any server options; a bare `?view=...` link does not identify the Meshcast playback endpoint.
3. In OBS, add **Sources > + > Browser** and paste the link into **URL**. Set your layout dimensions and enable **Control audio via OBS**.
4. Check moving video and audio, then record and play back a sample.

Give production viewers this Meshcast-backed link too. Opening the phone's original direct viewer link creates another upload from the phone. Keep only the outputs and previews you need.

## Other Meshcast workflows

* [Bring RTMP or SRT into OBS](https://docs.vdo.ninja/guides/meshcast-rtmp-srt-to-obs.md), including hardware encoders and a sending copy of OBS.
* [Stream to multiple platforms](https://docs.vdo.ninja/guides/multistream-with-meshcast.md) from one upload.
* [Compare the phone's output modes](https://docs.vdo.ninja/guides/mobile-app/choose-an-output.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-setup.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.
