> 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/advanced-settings/mobile-parameters/and-flagship.md).

# \&flagship

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Details

`&flagship` is a manual hint that tells VDO.Ninja to treat a mobile publisher as more capable than the default mobile assumptions.

It does not detect the phone model or chipset. It is useful when you know the guest is using a high-end mobile device and you want less aggressive mobile protection.

For room-only conferencing, VDO.Ninja can also use automatic room-only bitrate tiers. Those tiers are usually safer than forcing all mobile devices into a high-performance mode. See [Room-only mobile bitrate tiers](/guides/room-only-mobile-bitrate-tiers.md).

In director or scene controlled rooms, `&flagship` can be useful if you intentionally want a capable mobile guest to send higher quality video to other room guests. Test carefully, as mobile browsers can overheat or become CPU-limited when sending several peer-to-peer video streams.

If you need a numeric mobile cap instead of a broad hint, use [`&maxmobilebitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/and-maxmobilebitrate.md).

## Related

{% content-ref url="/pages/2sMgzgRpMONN0QYeQ2X9" %}
[Room-only mobile bitrate tiers](/guides/room-only-mobile-bitrate-tiers.md)
{% endcontent-ref %}

{% content-ref url="/pages/wI6cHBYKKmus5LyFjDDJ" %}
[\&maxmobilebitrate](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/and-maxmobilebitrate.md)
{% endcontent-ref %}

{% content-ref url="/pages/4q8OvUgNsobKPzdRHI82" %}
[\&notmobile](/advanced-settings/mobile-parameters/and-notmobile.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXc77Nu07lj\_22d16f" %}
[\&forceios](/advanced-settings/mobile-parameters/and-forceios.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/mobile-parameters/and-flagship.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.