> For the complete documentation index, see [llms.txt](https://docs.christianworldmedia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.christianworldmedia.com/documentation-and-guides/live-streaming/adaptive-live-streaming.md).

# Adaptive live streaming

{% hint style="info" %}
This feature is included in our higher-end plan(s).
{% endhint %}

With server-side adaptive streaming, we can split your incoming high-quality live feed into multiple resolutions, providing a better streaming experience for those with less-than-perfect internet conditions and high quality for those with excellent internet conditions.

For example, when your encoder sends in a high-quality 720p feed, your viewers can also have 480p, 360p, 240p, and 144p available. And the best part is their players will automatically adapt to the best resolution based on their internet speed.


---

# 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.christianworldmedia.com/documentation-and-guides/live-streaming/adaptive-live-streaming.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.